This page outlines the scrum process and is being used as a reference for information about how the ClueMapper could be used. ifPeople has adapted the scrum process and seeks to find a project management tool to help with enabling this functionality in ClueMapper.

General Process

• Create project space, create team, and set up your infrastructure

• Gather user stories/requirements: Add general user stories to the backlog. Prioritize user stories with client.

• Create iterations: scheduled by calendar time (start/end dates of iterations), add description and capacity info (earlier ones need it, later ones may not have it). If many iterations, ones further out in future may be grouped together and later organized into specific ones (ie i1, i2, i3, i4-6)

• Plan iterations: add user stories into iterations. Need to be able to see capacity information (vs scheduled) as you plan. Add tasks to user stories, flesh out details on user stories.

• Track iterations: daily standups, update actual and to-do hours as work happens, transition tasks and user stories in workflow. Reports show the burndown chart.

• Reflection: review work and team functioning, adopt experiments/learning for next iteration

Terms

• Burndown chart: a progress report that charts the remaining hours of work for a given iteration (typically, but can also be for release).

• Story points: A relative size measure for user stories. Determined by the whole team, they become a metric that can help planning and reporting.

• User story: brief description of the "who does what and what happens" of your site's functionality. Written in general language. More specific and technical details are added on in terms of Test Cases and Tasks.

• Backlog: Where all the requirements start out...the container for unscheduled work.

• Iteration: time-boxed unit of work. Has determined capacity and time, scope flexes. Planning moves stories from backlog to iterations.