sepc FS20

• Management Buy-In
• Small experienced team
  • Management position to get things going
  • Work with management
  • Start with 2-3 teams
• Continous Learning

Scaling Agile Framework

We are uncovering better ways of developing
software by doing it and helping others do it.
Through this work we have come to value:

• Individuals and interactions over processes and tools
• Working software over comprehensive documentation
• Customer collaboration over contract negotiation
• Responding to change over following a plan

• Satisfy customer through early delivery
• Welcome changing requirements
• Deliver frequently
• Business people and developers work together
• Motivated individuals...
• Face-to-face conversation
• Working software
• Sustainable development
• Attention to technical excellence
• Simplicity
• Self-organizing teams
• Regular self-reflection

• To plan
• To schedule (f.e. releases)
• Plan ressources (or hire them if needed)
• Price and guide investment

It's a method for estimating story points. The SM sits together with the development team:

1. SM picks a task and reads it to the development team
2. Each teammember picks one of his planning poker cards which states "how big" the tasks is in his/her opinion.
3. The cards are shown (turned public) all at once.
4. If the whole team agrees good. If the estimate vary heavily, the "player" with the highest amount and one with the lowest one justify their picks (on why this tasks takes that long)
5. The estimates are continued until theres consens.

A list of all User Stories and Tasks that the team wants to complete in the current sprint.

The team is responsible for it.

A relative work estimate to other User Stories.

Fibonacci Numbers are used because large numbers reflect the uncertainty, for which the team estimated certain User Stories.