- Being Open For Changes – Scrum framework is simple but not easy to implement unless there is an open minded people across the organization. Simple doesn’t mean easy. What sort of an open mind does it need? Well, First and foremost, be open for changes. Scrum requires radical changes as far as the process is concerned. Team needs to be independent, no one should baby sit the team, team should take control over things to be done. No one has the right to assign the team tasks, maintaining product vision by Product owner etc. Lots of them. This isn’t the case in traditional project management, You don’t have a complete project plan done with Microsoft Project! In Scrum, you take a small step towards the final goal and make necessary changes when your iteration completes at a certain time. Everything in Scrum is time bound.
- Trust Towards Others – Senior management should trust the Scrum team. They can partially influence product owner for any changes needed in the product vision. Even the Product Owner can not assign tasks to the team. He just needs to maintain the vision and priorities for the project. He can be there during the sprint planning, sprint review meeting to see the progress and verify if the team is building the right things. How much to do in a sprint, how to do is all up to the team. That gives the complete ownership of the tasks to the team. No project manager drives the show. Scrum team together manages the show. This can just be done with trust.
- Willingness To Understand Changes Required – Scrum framework is intended to handle frequent changes. Only during Sprint, things committed will not be changed. Before and after sprint, there is always changes proposed by product owner, management, team etc. Scrum encourages changes that refine the product. So, everyone needs to provide feedback and be ready for the changes.
- Inspection and Adaptation – Scrum needs constant inspection, review process to understand the progress made. If anything needs to be changed, it has to be done. Team needs to adapt best practices as and when needed.
- Honesty – Everyone in the Scrum team needs to be honest. Members need to take complete ownership and be responsible for the completeness. Members should be cross functional, non egoistic and honest in taking others work when needed. Since, no one assigns tasks, members should be pro-active in taking up responsibilities etc. Product Owner should do honest review of the progress, talk to customers and be up to date with their requirements. Scrum Master must do an honest attempt to help the team when they are in trouble. He needs to protect the team when additional changes come from upper management during sprint etc.
- No Blame Game – Scrum Team members should not point fingers at each other. It is very important to maintain this during Sprint Review and Retrospective meetings. Members need to respect each other and be polite to each others. If we are rude in pointing mistakes, the team chemistry gets affected adversely. All these qualities in an enterprise is not easy to find. Management needs to do a considerable work to provide such environment in the first place. Company policies need to have changes to accommodate such things.