Geeks With Blogs
Keep It Simple Simple Solutions for Complex Scenarios

Scrum is an agile framework that deliver an iterative and incremental management approach for software development. In the same way than
Extreme Programming (XP), Feature Driven Development (FDD), and Crystal, Scrum provides an “Agile Approach” to build software using a set of
practices that includes different artifacts such as Product Backlogs and Sprint Backlogs, “time-boxes” such as Sprint, Daily Meeting and predefined roles for the members of the Team (Team == all direct participants into  the project), you already know to ScrumMaster, Product Owner, and Team.

Scrum is often, but not always, a good fit for all organizations or projects software development approach. Software projects vary quite a bit in the stability of the requirements and user needs, the number of factors involved in the development effort, and mainly the level of access to end customers.

Therefore the first key to a successful Scrum adoption is to determine whether or not the methodology is appropriate for a project or for most of the projects in the organization. For me the keys aspects to consider are the following:

  • The accessibility to the feedback from the customers, it is very important for successful adoption of Scrum that the team have access direct to the feedback of the customer throughout the entire project.  
  • The technical skills of the team, in the same way than others methodologies or development framework without the necessary baseline of technical expertise there is a significant risk that the system unable to achieve the business goals that is developed will be brittle. Scrum works best with cross-functional teams allows an effective balance between the need to produce working software in the near term with long-term architectural implications.
  • The impact of the Change, talking about the change is talk about the stability of the requirements for the system. When the requirements for a system are well understood and stable, it is certainly possible to use Scrum, however it is not necessarily the best approach. With stable requirements, an approach such as Staged-Delivery can sometimes be a more effective approach. For me Scrum is a better fit for projects that require more exploration of the users’ needs.
  • The baseline infrastructure, for the iterative development requires that supporting infrastructure is in place or can be built during the project. Baseline infrastructure includes the tools and abilities to perform daily or continuous builds, perform validation of the builds, perform unit testing and regression testing, and promote and release builds. 

These considerations will help us to determine if Scrum is the right fit for an individual project or for use throughout the organization. In cases when a full Scrum adoption is not a good fit, it is generally still possible to adopt specific Agile practices and techniques on the project that will allow it to deliver functionality in a more incremental and iterative approach.

See u

Posted on Tuesday, September 21, 2010 4:55 AM Scrum , Agile Practices | Back to top

Comments on this post: It’s Scrum for me?

No comments posted yet.
Your comment:
 (will show your gravatar)

Copyright © Juan Mestas J. (aka gotchas) | Powered by: