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 Review Meeting is held at the end of each Sprint cycle. It is a 4-hour time boxed meeting at which the Team presents what was developed during the Sprint to the Product Owner and any other stakeholders who want to attend. This informal meeting at which the functionality is presented is intended to bring people together and help them collaboratively determine what the Team should do next.

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 Team is responsible for developing functionality. Teams are self-managing, self-organizing, cross-functional, and they are responsible for figuring out how to turn the Product Backlog into an increment of functionality within an iteration and managing their own work to do so.

Further Reading

Product Owner
ScrumMaster

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

In the Scrum process, the Product Owner is responsible for representing the interests of everyone with a stake in the project and its resulting system. He/she creates the initial overall requirements, ROI objective, release plans, and prioritizes requirements.

Further Reading

A Visitor is a statistical term to describe a single user that has accessed your site. Web servers log visitors on the first hit they make on the server then track them so that any additional requests are only logged as hits, not a new visitor. Web servers not only log the number of visitors but also which page they accessed first.

Further Reading

Value describes the overall worth that is derived from your site for the organization.

Means of Value:

• Promote name recognition
• Elevate company's perceived value
• Establish credibility
• Generate sales leads
• Enhance sales process
• Expand markets
• Reduce operating costs
• Improve communications

Further Reading