1. Edward Herrera Aguirre Open Knowledge Technologies

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

3.  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

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

6.  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

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

9.  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

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

11. Scott W. Ambler - 2006 www.ambysoft.com/scottAmbler.htmlwww.ambysoft.com/scottAmbler.html

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

13. Indeed.com

14. Eclipse Foundation 2010 survey

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

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

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

18.  ScrumWorks http://danube.com  Greenhopper http://www.atlassian.com/software/greenhopper/  Banana Scrum http://www.bananascrum.com/  Bright Green http://www.brightgreenprojects.com/  Agilo for Scrum http://www.agile42.com/cms/pages/products/  Digaboard http://www.digaboard.net/  FireScrum http://www.firescrum.com/  IceScrum http://www.icescrum.org/  PrjPlanner http://prjplanner.sourceforge.net/  Scrum Dashboard http://scrumdashboard.codeplex.com/  Scrum Time http://scrumtime.org/  The Scrum Factory http://www.scrum-factory.com/  Winds of Scrum http://windsofscrum.sourceforge.net/

19.  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