Edward Herrera Aguirre Open Knowledge Technologies

 Software development is not a defined process  The main inputs to the software process activities are people  Complex processes require an empirical control model

 Traditional methodologies try to be predictive - to create a schedule at the beginning of a project and to conform to this schedule for the life of the project  In the physical world people accept that requirements need to be fixed  Software is much less tangible. Not only is it hard to be precise about what's needed, it's also hard to see why it should be difficult to change later

Version One - 3rd Annual Survey: 2008 “The State of Agile Development"

 SCRUM Is a sub set of the Agile methodology for software development project management  Differentiates from others methodologies because its introduces the concept of “empirical process control” that is, use the real-world progress of a project

 Product Owner (Industry or Business expert)  Scrum Master  Team Member

 Living backlog  Short iterations or sprints  Daily meeting –scrum-  Brief meetings to define the backlog items for each sprint  Retrospective to reflect about past sprints

 Crystal Clear  Extreme Programming  Feature Driven Development  Dynamic System Development Method  Adaptive Software Development  Lean Development

Scott W. Ambler

Version One - 3rd Annual Survey: 2008 “The State of Agile Development"

Indeed.com

Eclipse Foundation 2010 survey

 Team Foundation Server template for project management  Contains the elements of the SCRUM process for a project team into a Team Foundation Server

 Sprint  Product Backlog Item  Bug  Task  Impediment  Test Case

 Release Burndown  Sprint Burndown  Velocity  Build Success Over Time  Build Summary  Test Case Readiness  Test Plan Progress

 ScrumWorks  Greenhopper  Banana Scrum  Bright Green  Agilo for Scrum  Digaboard  FireScrum  IceScrum  PrjPlanner  Scrum Dashboard  Scrum Time  The Scrum Factory  Winds of Scrum

 Plan the project.  Build the product backlog  Establish the release plan  Plan the sprint  Chose user stories  Identify tasks  Run the sprint  Complete the user stories  Track the sprint  Track the project