Sprints

by Ora

For teams that refuse to be average

Agile Sprints in Ora
Agile Sprints in Ora

Agile Sprints in 5 Steps

Backlog3New task26
As a power user, I can specify files or folders tobackup based on file size, date created anddate modified.230m#2358
Mobile app mockup45m#23813
#23As a user, I need to be able to upload files easily.Furthermore, I want to be able to manage anddelete files as well.
138
Backlog3New taskAs a user, I need to be able to upload files easily.Furthermore, I want to be able to manage anddelete files as well.#2326As a power user, I can specify files or folders tobackup based on file size, date created anddate modified.230m#2358Mobile app mockup45m#23813

1. Collect

Add all stories, ideas and requests to your product backlog, discuss, prioritize, and plan ahead.

2. Estimate

Make relative estimates of the effort and business value for each story.

#23As a user, I need to be able to upload files easily.Furthermore, I want to be able to manage anddelete files as well.138

3. Start a sprint

Choose the right amount of work according to your team’s velocity and start a Sprint.

4. Burn

Follow your progress each day as your team burns down stories until you get to the bottom.

Sprint ReviewSTORIESPOINTSPOINTS DONE50p40p30p20p10pTueJul 23WedJul 24ThuJul 25FriJul 26SatJul 27SunJul 28MonJul 29TueJul 30WedAug 1ThuAug 2FriAug 3SatAug 4SunAug 5MonAug 6TueAug 7481146Sprint 4Tue, July 23 -Tue,August 7GuidelineRemaining pointsMonday,Feb 2429 pointsremaining4 points done

5. Finish on time

Finish on time, every time! Right after your first Sprint, your team will generate velocity. By looking at your team's Velocity, it will be easier to don't over-commit and finish on time! Review your Sprint. Plan the next one accordingly. See long-term progress, burndown, and forecasts on epics and releases.

See a velocity chart of how much you committed vs how much you completed.

Sprint 1Sprint 2Sprint 3Sprint 4Sprint 5CommitmentCompleted50p40p30p20p10pSprint 6Sprint 7Sprint 8Sprint 9 (active)VELOCITY CHART3232402842485252404850508484444444444Sprint 540 points comitment44 points completedTue, July 23 -Tue,August 7

Is your release going to be on time? A release burndown will show you how work for this release is moving for each sprint. Based on completed points Ora will forecast how many more sprints are needed.

Remaining workCompleted workAdded workForecast50p40p30p20p10pSprint 7Sprint 8Sprint 9Sprint 10Sprint 11NextNext +1Next +2Next +3Next +4RELEASE BURNDOWNVersion 2.0DueTue,August 7-2-3-4-3-3-3-3+4+23031272420143032-33STORY POINTSREMAINING27OF ISSUES AREESTIMATED100%MORE SPRINTSFORECASTED5Sprint 1122 pointsremaining4 points doneTue, July 23 -Tue,August 7

Epic tasks usually need to be worked on in more than one sprint. Track progress and see a forecast of when the selected epic is going to be ready.

Remaining workCompleted workAdded workForecast50p40p30p20p10pSprint 9Sprint 10Sprint 11NextNext +1EPIC BURNDOWNReports 2.0DueTue,August 8-3-6-6+43031126-6STORY POINTSREMAINING12OF ISSUES AREESTIMATED80%MORE SPRINTSFORECASTED2

Powered by Ora

The cleanest, most versatile and customizable workspace you will ever find.

Time Tracking
Close with commit
Markdown
Code Highlight
Multiple Select
Context Menu
Task Relationships
List Actions
Mentions
Comments
Milestones
Due Dates