agile development

In the Scrum process, the Sprint Retrospective Meeting follows the Sprint review meeting. At this time-boxed 3 hour meeting, the ScrumMaster encourages the Team to revise, within the Scrum process framework and practices, its development processes to make it more effective and enjoyable for the next Sprint.

Further Reading

In the Scrum process, the Sprint Backlog defines the work, or tasks, that a Team defines for turning the Product Backlog into an increment of potentially shippable product functionality.

Tasks should be divided so that each takes roughly 4 to 16 hours to finish. Tasks longer then 4 to 16 hours are merely placeholders for tasks that haven't yet been appropriately defined. Only the Team can change the Sprint Backlog.

Further Reading

In the Scrum process, the Sprint is the name for the process where work is accomplished. A Sprint is a 30-day iteration in which the Team works to complete new functionality from the Product Backlog. Each Sprint is initiated with a Sprint Planning Meeting and ends with a Sprint Review Meeting.

Further Reading

In the Scrum process, the Daily Scrum Meeting is a 15-minute status meeting during a Sprint cycle. Meetings are led by the ScrumMaster.

Purpose:

To synchronize the work of all Team Members daily and to schedule any meetings that the Team needs to forward its progress.

Time & Location:

The Daily Scrum meeting is time-boxed to 15 minutes regardless of the number of Team Members.

Daily Scrum meeting will be held in the same place at the same time every work day - ideally first thing in the morning.

Attendance:

In the Scrum process, the Sprint Planning Meeting initiates each Sprint cycle. Sprint planning meetings cannot last more then 8 hours, and are broken up into two 4 hour sessions. The first 4 hours are spent with the Product Owner who presents the highest priority product backlog to the Team. During the second 4 hours, the Team plans out the next Sprint. When the second 4 hour meeting commences, time begins to advance for the current Sprint session.

Further Reading

In the Scrum process, the Product Backlog is usually a constantly changing list of prioritized requirements for a project. The Product Owner is responsible for the contents, prioritization, and availability of the Product Backlog.

Further Reading

I was doing some research on the adoption rate of agile development methodologies in corporations and came across this great quote in a CIO magazine article:

The CHAOS Report is a study based on The Standish Group’s CHAOS Research Project on IT project success rates and project management best practices. The study is often cited as the de facto authority on success rates of IT projects. It was started in 1994 and reported that only a startling low 16.2% of IT projects are successful. Successful projects are defined as meeting all the requirements of the project management iron triangle; on time, on budget and on scope. The CHAOS reports classifies projects into: