Send the link below via email or IMCopy
Present to your audienceStart remote presentation
- Invited audience members will follow you as you navigate and present
- People invited to a presentation do not need a Prezi account
- This link expires 10 minutes after you close the presentation
- A maximum of 30 users can follow your presentation
- Learn more about this feature in our knowledge base article
Do you really want to delete this prezi?
Neither you, nor the coeditors you shared it with will be able to recover it again.
Make your likes visible on Facebook?
You can change this under Settings & Account at any time.
Let's adopt Scrum
Transcript of Let's adopt Scrum
developers management Team Story Definition
Initial estimation story point product owner How do we use Scrum ? With Greenhopper ? sprint backlog deadline Goal:
"Why do we do this sprint? Why don't we go in vacation instead?" Priority Velocity definition of "done" story Tasks 3 5 2 collaboration 2 demos pizzas ? Sprint planning scrum moderator stand up meetings task estimation branches Sprints Tests man-day vs story points functional specification sprint name retro TDD Continuous integration Next: QA tests ? Each sprint should at least include one QA round. The QA version will appear in the git repository as a branch with the following convention:
QA-ROUNDNUMBER-NAMEOFTHESPRINT Have a master for each project, the master has to be stable (compilation should “never” fail)
While working in the development, the developers will create branches:
For each release:
BUILD-NAMEOFTHEBUILD Final word Boards Links links between tasks Issues epics tasks sub-tasks stories Rapid board -> Plan Task board story points or time estimation? ranks estimation