Transparency
- Across the board...this includes the Scrum Team (Product Owner, Scrum Master and Development Team members), Customer, Stakeholders, Management, etc..
- It's a KEY factor for Collaboration in true sense...everybody works as a One Team.
- It creates Honest and less stressful environment. Less Negotiation, More Collaboration.
- Less time wasted behind preparing various Reports for tracking the progress.
- Information runs from top-to-bottom and vice versa.These provides great visibility, which helps with quick decision making.
- 360 degree feedback and sharing details horizontally with other teams and departments. Improves collaboration and opportunities improve increases and overall Risk decreases.
- Scrum Master assures Transparency and teaches Scrum Team to improve. Scrum Master also works with other Scrum Masters and management to improve Transparency at Organization level.
Inspection
- Regular Check points for Tracking / Measuring Progress...Daily Stand-ups, Sprint Review and Sprint Retrospective provides us opportunities.
- It's KEY factor and first step towards improvements for generating more value.
- Development Team uses Ceremonies for Inspection like Daily Stand-up for checking and adapting game-plan to meet Sprint Goal, getting feedback from Customer and Stakeholder during Sprint Review and using Spring Retrospective for improving Team's processes.
- Various boards and charts are used for visual Inspection opportunities.
- If we fail to Inspect then won't catch emerging issues / deviations, which leads to project delays and additional costs.
- We can appoint Inspectors for different aspects of the project, thus sharing responsibilities within the Scrum Team.
Adaptation
- Adjusting / Rectifying / Improving processes when identified and as soon as possible to gain maximum value.
- It's KEY differentiator between traditional waterfall methodology and Agile methodology. In Agile world, we always embrace and Adapt changes, so that we can constantly improve.
- Many times, Inspection and Adaptation goes hand in hand. While Inspection, if we find deviation then we formulate and Adapt new game plan.
- Now a days, in fast paced businesses, product cycles are shorter. So, Customer will keep changing requirements as per the feedback received from market. Scrum Team have to accommodate all those changes to keep customer happy.
- Development Team, Inspect and Adapt on daily basis during Daily Stand-up ceremony.
- Sprint Review is another ceremony where Scrum Team will ask for feedback from all stockholders and Adapt accordingly.
- During Sprint Retrospective, Scrum Team discusses internally about issues and opportunities for improvements. The will prepare and Adapt new plan as a team to generate more value.
Commitment
- Commitment => Dedication => Hard work => Passionate => Happy and Successful.
- Scrum team is made up of self-organizing Development Team members, Scrum Master and Product Owner. All collaborates but no one controls. In this scenario, self COMMITMENT plays crucial role.
- Commitment is the key element of success for high performing teams.
- Committed teams emit positive energy which reflects on their attitude and productivity.
Focus
- Being Focused means you are working towards the GOAL. Constantly generate value to keep Customer happy and satisfied.
- Your mind (Conscious as well as Subconscious) is thinking about HOW to achieve the GOAL.
- It brings out Creativity. Many of "out-of-box" and disruptive idea comes from being Focused.
- Delivering working product each iteration is not easy. Fully Focused Scrum Teams can plan well ahead. They will be able to Inspect and Adapt to the changing situations effortlessly. They will be more AGILE.
Openness
- Openness, Fully Transparent, NO Secretes, NO office politics, NO back stabbing.
- Be Open about your capabilities, constructive 360 degree feedback, keep an Open mind about new ideas, new way of thinking.
- Actual status of the development is visible to all stakeholders. Team members willingly collaborates to generate maximum value.
- Impediments are also made visible, so fast actions can be taken.
- Bottom-up and cross-functional information flow will improve organizational productivity.
- It brings out TRUST between each other and strengthen bonds to work as single unit.
Respect
- Respect can't be WON, it MUST be EARNED. It's a core principle at Servant Leadership management style of Scrum Framework.
- Scrum teams are formed with cross-functional members having multiple competences.
- They all SHOULD Respect each others expertise and point-of-view to work as a cohesive unit.
- Management and Stakeholders SHOULD Respect Product Owner (PO) for his decisions for maximizing Product profitability and Development Teams productivity.
- Scrum Master SHOULD be trusted and respected for implementing Scrum rules and guidelines at every level of the organization for maximum benefits.
- Development teams SHOULD be respected for their ability to produce working Product at end of each iteration.
Courage
- “Success is not final, failure is not fatal: it is the courage to continue that counts.” - Winston S. Churchill
- Give your best, Inspect the results, Adapt to improve....and do it again!
- Have the Courage to share your knowledge, to ask for help without hesitance, to try new ideas without fear of being criticized and to oppose when you don't agree.
- Constructive criticism is healthy for the progress. It brings out best and brightest ideas.
- Have the Courage to say NO to Product Owner, when s/he tries to give more User Stories for the Sprint.
- Have the Courage to say NO to people, who asks you to do additional work out of Sprint.
- Have the Courage to delay the Release, if Quality of the Product is not meeting the Acceptance Criteria or Definition of Done.
- Have the Courage to respect Time-box boundaries, which will improve team morale.
