This post originated from an RSS feed registered with .NET Buzz
by Jonathan Crossland.
Original Post: 10 reasons to use or not use Scrum
Feed Title: Jonathan Crossland Weblog
Feed URL: http://www.jonathancrossland.com/syndication.axd
Feed Description: Design, Frameworks, Patterns and Idioms
When you are fire-fighting bugs, issues and points of failure
When you need to quickly get back into good grace with the client after tons of issues
During the very initial investigations of the project, research and understanding user stories
When Use Cases are not being met properly and you need to get things on track functionally
When new members join a team, or an increase in communication is required.
When the product owner needs to balance a backlog
When there is a lack of responsibility and accountability
When NOT to utilize SCRUM (prefer a more Agile Methodology)
Gathering requirements
Designing the system functionally
Designing the system architecturally
Core Development phases
Development phases which require design
Phases dedicated to Refactoring
Phases dedicated to Testing
When roles and responsibilities are defined properly
When requirements are consistent and relatively static
When management and interested parties are not committed to it
SCRUM is not a silver bullet and no team, in my opinion can afford to put all their eggs or life-cycle phases into one basket.
Updated:
Scrum or being agile is not something that can solve your problems. It is rather the the team, leadership and real productive processes that count more than anything. A person unskilled in leadership and who does not have the complete 'vision' will fail in whatever processes are in place. And those that are good at leadership and management, were agile and good at it, before any methodology was created.
I think most importantly, a leader must care, be focused, be open minded and must seem to 'see into the future', as his intuition will show through.
Previous Topic
