The Scrum methodology is a framework which allows your company the flexibility to employ your own processes and techniques. Scrum project management is grounded in an empirical process control theory and utilizes an iterative and incremental development approach.  Inspect and adapt points are incorporated in the Scrum methodology framework for the benefit of the release, each sprint, and the team.  Benefits your company will realize using the Scrum project management framework include:

• Time-boxed sprints and meetings enforce urgency toward immediate defined goals.
• You will receive working software in every iteration – even the first.
• Changing requirements are embraced throughout the project – even late in development.
• Developers, customers and users work together to deliver a product that meets your needs.
• Teams are self-organized, self-managed and highly motivated.

                           The Scrum project management framework begins with Scrum Planning where the project team is formed and the Product Backlog is compiled. Scrum Planning includes whatever activities your organization requires before initiating a project. The key artifact generated from this activity is the Product Backlog which consists of prioritized features with estimates. Scrum Planning is not time constrained but the more time spent here means the less time that is spent building product.                            Once a prioritized Product Backlog has been compiled, iterative sprints begin. Sprints are typically 2 - 4 weeks in duration and begin with a Sprint Planning meeting. Sprint Planning consists of two parts – selection and decomposition.  During the first part of the meeting the Product Owner describes their vision for the product and desired objectives for the upcoming sprint.  In the second part of the Sprint Planning meeting the Scrum Team decomposes the high priority Product Backlog items selected for the sprint into 4 – 16 hour tasks which compose the Sprint Backlog.  This becomes the Scrum Team’s work plan for the next sprint.  The scope of a sprint should rarely change.                            Throughout the duration of the sprint daily Scrum meetings are held. These 15 minute meetings are typically held early in the day at a time when all Scrum Team members can attend. Anyone is invited to attend, but only Scrum Team Members can speak. Each team member is expected to answer three questions.
1. What did I do yesterday?
2. What am I planning to do today?
3. Is there anything in my way that is slowing me down?                            On the last day of each sprint a review is held with interested stakeholders. This is not a formal management level presentation; rather it is a demonstration of what the team has accomplished during the sprint that just ended. Scrum Team members demonstrate the working software that was written in the last sprint. PowerPoint is prohibited!                            Also on the last day of each sprint a team retrospective is held. Scrum Team members attend this meeting where they discuss what went well on the sprint that just ended and what could be improved for the next sprint. It is important to generate a prioritized list of action items for continuous improvement.                            The Product Owner is responsible to make the decision whether to deploy the software or to continue with the next sprint. Their decision is based on progress made on the Product Backlog and demonstrations of the product during Sprint Reviews. The Product Owner also makes the decision whether to terminate the project if they feel there is diminishing value in completing the remaining items on the Product Backlog.