Part 2 Scrum Master Get the most out of Sprints

Incremental = small increments of a project are delivered piece by piece until the entire project is complete.

Iterative = clear feedback is elicited after each increment and incorporated into the next increment.

Incremental + Iterative = Success for Scrum team

  • Breaks a larger project into smaller deliveries
  • Can reduce the overall effort
  • Reduces the impact of costly mistakes
  • Incorporates feedback along the way

Timeboxing

Sprints is a fix time box often define 1-4 weeks, team attempts to complete all work, incorporate feedback.

Features increments: features are not sized consistently, feedback comes unevenly, may not receive feedback on all features.

Sprint increments: feedback occurs more regularly, encourages stakeholders to give more frequent feedback, easier to coordinate.

How long should my sprint be? as short as 1 week, 2 weeks, or 30 days max.

Shorter sprints – easier to plan, better ability to reduce risk but more time planning.

Longer sprints – more difficult but infrequent planning will incur more risk.

Definition of Done

Shared understanding of Done. Need to be specific and everyone understands the same definition. Production or just tested, or still in QA? need to be sure and agree with the team.

  • Attainable – realistically represents the capabilities of your team.
  • Collaborative – created by both stakeholders and the development team working together.
  • Flexible – subject to change as the team finds better ways to work.

Potentially shippable product increment

Scrum are not necessary shipping complete product at the end of sprint. Always leave the product in a releasable state at the end of each sprint so it depends on business to decide which one should be released.

  • better business value – recoup cost sooner or lessen overall investment.
  • reduce risk – create a product that is ready to ship at any moment.
  • more transparency – covey the team’s true status to project stakeholders.

Learning more

  • Creating effective user stories
  • Book – continuous deliver reliable software release through build, test, and deployment automation – Jez Humble and David Farley.

Part 1 Scrum Master Fundamental

Agile is a philosophy but Scrum is a framework to manage software development framework process. Agile is the super set of Scrum, Kanban, XP.

The Agile Manifesto

A group of 17 developers discuss what is the best way to run software development project.

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

Agile is not prescriptive, it’s up to a team on how to do.

The roots of Scrum

  • Empirical process control, prevalent in the manufacturing space.
  • Toyota production system, early scrum was heavily influenced by the TPS.
  • Predates the agile manifesto, the manifesto was written in 2001, but Scrum appears in the 1990s.

Empiricism – knowledge comes only, or primarily, from experiences.

Scrum is driven by Empiricism. Make decisions based only on what has occurred, use lag indicators driven from historical metrics. Scrum use lagging based indicator not leading indicator.

Scrum is a framework, Not a process

  • Definition of key tasks and routine
  • Non-prescriptive

Scrum Framework + Your Environment = Your Process

Your Scrum is not my Scrum. Org structure, team dynamic, cultures are all differences.

3 Legs of Empiricism

  • Inspection
    • inspect both the project and the process
    • look for variances
    • strike the right balance
  • Adaption
    • Reduce what isn’t working, increase what is
    • introduce changes at the right time
    • Adapt the process to serve the project
  • Transparency
    • make your pace and progress visual
    • encourage openness across the team
    • share clear status across team boundaries

Scrum does not solve your problems, but enables you to solve your problems.

What about engineering?

Scrum does not address any engineering practices. The focus is entirely on project management principles. Extreme Programming (XP) is a subset of Scrum offers some engineering practices.

Learning More

  • Agile Manifesto: www.agilemanifesto.org
  • Scrum Guide: www.scrumguides.org
  • Extreme Programming Explained: Kent Beck and Cynthia Andres book