-
Notifications
You must be signed in to change notification settings - Fork 1
Scrum
Alex Aubé edited this page Apr 20, 2015
·
2 revisions
A method for agile project management

- Agile Structure where we use agile technics
- Use to solve problems with great complexity and changes
- Planning
- Cycles of Sprint
- Closure
- Everyone can take decisions
- No project manager
- Product owner => To maximise the value of product and the work of the team. Manage product backlog(requirements).
- Scrum master => Comprehend and apply SCRUM. To facilitate Communication between parties.
- developers => Manage it's own work. Touch every assets. Takes decisions.
- Planning => Backlog production, analyse risks, obtain ressources, produce calendar of project
- High level Architecture/Conception => Minimal architecture for system with backlog
- Sprints => Short, 2 to 4 weeks.
- Starts with task planning => Prioritized and risks degree awarded
- Sprint backlog => List of feature to do
- Scrum meetings => Short(15 minutes), before every work sessions. Everybody is involved. Adjusting the planning daily
- Sprint Review => At the end of a sprint. 1 hour per week of sprint. Everybody is involved.
- Sprint retrospection => To learn from experience. Not do the same mistake twice.
- Final integration of all sprints if necessary
- Last System tests
- Writing Doc
- Formation for users
- Acceptation Tests
- Deployment