Agile Methodologies

Roles

One person shouldn't have all these roles!

Sprint duration

I have tried a month but it's hard to manage and it's not terribly Agile. Particularly when it's hard to not have any interruptions even on a 2-week sprint.

Sprint zero

Trial run.

Product backlog

The product backlog is a living artefact, higher ranked items should be more refined. It is a placeholder for a conversation.

Each refined story in the sprint must have a weight/complexity for planning purposes. These estimates must be done by the people actually doing the work. They should also have a business value and the product owner must share a clear objective/vision for the forthcoming sprint.

Estimating

Humans are bad at estimating how long will take. But they are good at comparing the complexity of tasks: is task two more complex than task one? Use complexity points to move away from thinking about duration.

Use the Fibonacci sequence so you don't overthink it: is it 2.5 or 3 complexity points?

Is this piece of work larger or smaller than this other thing we did last week?

Estimate against work that's already been performed. New backlog? Estimate against a known thing. It might be useful to build up and maintain a list of example tasks and complexities.

1. One line change in a config file.
2. Multiple line change in a config file.
3. One line change in a compiled file.
5. Multiple line change in a compiled file.
8. Create new Visual Studio project.

Daily scrum

Remember that the daily scrum is not a status meeting for the scrum master, it's a planning meeting for the dev team. It's also intended for the dev team so doesn't necessarily include the scrum master of product owner. Don't look at the scrum master, look at the board.

Scrum master

The scrum master's prime responsibility is removing impediments. Learn to navigate the politics of your organisation. A dead scrum master is a useless scrum master. scrum master is responsible for success of current sprint, product owner is responsible for the planning of upcoming sprints. scrum master is also responsible for ensuring that planning occurs.

Meeting the sprint goal

Sprint Review

The sprint review is not the product owner's chance to review work done during the Sprint. It gives stakeholders the opportunity to give feedback on the state and direction of the product. And collaborate on the goals for the next sprint.

Remove rough estimates from backlog prior to sprint planning.

Customer

Agile methodologies

User stories

As a  I want  so that .
Given  when  then .

Encourage simplicity: don't put the implementation details in the requirement.

INVEST

Stories should be:

Testing

Sprint review

How long is an epic?

https://www.scrum.org/forum/scrum-forum/16650/best-practice-size-epics

Example complexities

1

2

3

5

8

13+

References

References