- Individuals and interactions over processes and tools
- Working software over comprehensive documentation
- Customer collaboration over contract negotiation
- Responding to change over following a plan
http://agilemanifesto.org/
Agile project management is an iterative development methodology that values human communication and feedback, adapting to changes, and producing working results.
An iteration is a single development cycle, usually measured as one week or two weeks.
A deployable software package that is a culmination of several iterations of development.
A daily progress meeting (where everyone literally every stands up)
- What I did yesterday
- What I am planning on doing today
- Any blockers
Fixed length iteration provides a cadance that means everyone has a routine they don't need to consciously think about.
Presentation of work completed to team and product owners.
A story that cannot be estimated until a development team runs a time-boxed investigation.
A particular business need to be assigned to the software development team. Stories must be broken down into small enough components that they may be delivered in a single development iteration.
Points are allocated to each story to indicate the size of the task. Usually these are rough sizes like small, medium, and large, not actual time measurements.
A defined period of time during which a task must be accomplished.
The budget of story units available for planning the next iteration of a development project. Velocity is based on measurements taken during previous iteration cycles.
Agile project management is an iterative development methodology that values human communication and feedback, adapting to changes, and producing working results. An important part of this is the Retrospective. Usually held once per iteration. It provides the team a way to communicate wins and losses, to consistently make small course corrections to stay on track.
Steps to run a retro:
The first is the happy column. The second is the wondering column. The third is the sad column.
Now it’s time for everyone to write on a post-it, come up to the board (together), and put their post-its in on the whiteboard in the columns.
Questions to think about when writing up post-its to put in a column:
- What went well this week?
- What questions do you have that we should talk about?
- What’s puzzling you? What was hard?
- What was just downright bad?
Post-its will be reorganised into clusters to try to find common areas for discussion.
Everyone votes on the topics idntified by the clusters.
Top voted topics are discussed in order within the time allocated to the meeting.
Action points will be created for each discussion