Scrum believes that employees are self-motivated and seek to accept greater responsibility. So, they deliver much greater value when self-organized. The preferred leadership style in Scrum is “servant leadership”, which emphasizes achieving results by focusing on the needs of the Scrum Team. Benefits of Self-Organization Self-organization as an essential principle in Scrum leads to the…
In the process of creating Large Project Components, we need to understand how the multiple Product Owners work together and how the multiple Scrum Teams work together. Also common components and common and specialized resources are to be identified. Following are the inputs required for creating large project components in Scrum. Project Vision Statement A…
It is widely known in the software development industry that Agile values “working software” over “extensive documentation.” This leads to the common misconception that Agile does not believe in documentation. It is true that documentation in Agile does not always mean typing code descriptions or lengthy time consuming information that may come in handy sometime…
Once the Scrum Team has selected User Stories for a given Sprint, they should then consider any dependencies, including those related to the availability of people as well as any technical dependencies. Properly documenting dependencies helps the Scrum Teams determine the relative order in which Tasks should be executed to create the Sprint Deliverables. Dependencies…
As companies progressively adopt Scrum as the preferred project management method over traditional waterfall method, the subject of ‘role-mapping’ becomes more critical. Perhaps, one of the biggest challenges that organizations face when they move to Scrum is where does a Project Manager fit in Scrum? We are so used to the role of a Project…
