Establishing and Maintaining Top to Bottom Transparency Using the Meta-Scrum |
 |
| Friday, 05 October 2007 20:47 |
|
Agile processes and practices have gained enough attention that both IT businesses and product development organizations are engaging in large Agile implementations. These larger-scale products, programs, and projects are more complex, have more dependencies, and present significant challenges. According to the second annual "State of Agile Development" survey, Scrum (and Hybrid XP/Scrum) is being chosen over other Agile methods 60% of the time. For larger multi-team implementations, Scrum has an advantage of providing successful scaling techniques. For example, the Scrum-of-Scrums meeting helps teams synchronize and coordinate with the purpose of executing on the Product Backlog. When the Scrum-of-Scrums is insufficient because multiple organizational units need alignment, and consent must be obtained from high levels, the coordinating Meta-Scrum meeting adds balance because the Meta-Scrum is Product Owner focused while the Scrum of Scrums is team focused. Agile principles, including "Working software is the primary measure of progress," mean we must have a focus on releases - and releases are the primary focal point of a Meta-Scrum throughout the project lifecycle. A properly executed Meta-Scrum helps drive transparency vertically into the organization. Read more >>
Set as favorite
Bookmark
Email this
Hits: 1248 Trackback(0)Comments (0)
|
TrackBack URI for this entry
Subscribe to this comment's feed