Scrum Methodology
Learn Scrum
The Scrum approach to agile software development marks a dramatic departure from waterfall management. Scrum and other agile methods were inspired by its shortcomings. Scrum emphasizes collaboration, functioning software, team self management, and the flexibility to adapt to emerging business realities.
4th
SEP
Scrum and the Enterprise
Posted by admin under Uncategorized
As Scrum continues to grow in popularity, one of the hottest topics on the minds of the community is how to translate the benefits of a paradigm created for small, collocated teams for enterprise-level installations of hundreds, if not thousands of users. Given that communication channels increase (and therefore communication decreases) as the size of a team grows, this issue is only compounded when teams begin to scale to Scrum-of-Scrum configurations. Clearly, the solution is a tool designed specifically for Scrum projects that can allow teams to remain small, but nonetheless connected to the bigger picture.
Of course, the tool also needs to be flexible enough to meet the unique demands of large and complex development environments. For example, large organizations often develop products with shared components, which require the ability to plan releases against multiple backlogs. And while Scrum and other agile management methods have steadily crept into the software development landscape, the project management tools available have not kept pace.
But all that may be changing now. I just watched a screencast of ScrumWorks Pro 4 and this release’s new functionality makes it the first truly enterprise-ready Scrum tool. Namely, it addresses the issue outlined above by allowing customers to manage high-level features and releases that span multiple product backlogs. This is a really important breakthrough. Before that functionality existed, organizations had to creatively develop workarounds for their agile tools to achieve the same effect, but, still, with less-than-ideal results. Now, products can be associated with multiple programs, which, in turn, allows shared components to be modeled accurately while providing organizations with a more realistic view of overall progress. This is going to eliminate some very big headaches for some very big companies… You can read more about it here.
Tags: program management, project management, Scrum Basics, Scrum tool, ScrumWorks ProScrum Training Series
Recent Posts
- Scrum based funding model – 20 percent May 9, 2013
- The Next Big Idea March 5, 2013
- On Being Available February 17, 2013
- Should Scrum Always Require the Product Owner to Attend the Sprint Retrospective Meeting? February 5, 2013
- Happiness Metrics January 23, 2013
Archives
- May 2013 (1)
- March 2013 (1)
- February 2013 (2)
- January 2013 (2)
- December 2012 (3)
- November 2012 (1)
- January 2012 (1)
- December 2011 (2)
- November 2011 (3)
- October 2011 (2)
- November 2010 (1)
- September 2010 (1)
- June 2010 (1)
- April 2010 (1)
- March 2010 (1)
- February 2010 (1)
- December 2009 (3)
- November 2009 (2)
- October 2009 (4)
- September 2009 (4)
- August 2009 (2)
- July 2009 (2)
- June 2009 (2)
- May 2009 (2)
- April 2009 (2)
- March 2009 (5)
- February 2009 (2)
- January 2009 (2)
- December 2008 (4)
- November 2008 (3)
- October 2008 (4)
- September 2008 (4)
- August 2008 (1)
Categories
- Agile and Scrum (32)
- Agile Assessment (2)
- Agile Manifesto (6)
- Agile Principles (10)
- Scrum Basics (45)
- Scrum Discussion (28)
- Scrum Transitions (19)
- transformation (5)
- Uncategorized (10)