Super Brain Metaphor

Instead of a project manager collecting input from team members to do the plan, the whole team plans together in Sprint Planning. Using all experiences, and personalities in a highly interactive and energetic way, facilitated by the Scrum Master. This unleashes the super brain capability which enables high-quality plan and a true commitment by the team. As a positive side effect, team members will feel a stronger commitment towards a plan they have been part of creating.

Implementation recommendation

  • Super Brain metaphor to be used in kick-off sessions of new teams or when starting a Sprint planning with inexperienced or new team members...
  • Learn more...

    Impediments Management

    Impediments are whatever hinders the team from reaching the Sprint Goal. Often when introducing Scrum ugly stuff that is swept under the carpet becomes visible again. This is impediments to be handled.

    Implementation recommendations

  • Visualize impediments raised by the team by creating a list on white-board with impediments. Often impediments are in the obvious domain where sense – categorize – respond is applied...
  • Learn more...

    Continuous Improvements @whiteboard – Kaizen

    Kaizen – continuous improvement, inspect, adapt and transparency is the common denominator throughout the Scrum framework. By applying the Scrum framework, a journey of continuous improvement has begun. The framework itself is a continuous improvement loop each sprint in several dimensions

    Implementation recommendation

  • Understand the reason why the team is unable to meet deliveries, “5 whys” method [1] can be used to build an understanding of why a team is unable to meet the Sprint goal. Ask the team why they cannot meet the Sprint goal? Ask the question five times for each reasonable explanation.
  • Read more...

    Kanban

    Scheduling system – Good practice to schedule shared resources between Scrum teams, examples – specialists, test pilot, lab or other external dependencies tied to Scrum teams. Basically, Kanban is a prioritized list that optimizes on flow, decoupled from the tools and methods you already use. It’s a simple scheduling system yet transparent and powerful. Scrum Master aid’s team to kick off a Kanban board and explains the method.

    Implementation recommendation

  • Kanban methodology is applied on groups outside a Scrum team, typically specialists supporting with qualified work. When those resources are shared by other Scrum teams or entities in organization the supporting functions need a way to schedule incoming work to be able to handshake deliveries to Scrum team...
  • Click Here...

    Commitment Point – Yes, team believes in Sprint forecast

    Commitment Point manages dependencies outside team when doing detailed planning. It enables a commitment from team to the detailed Sprint planning. Dependencies outside of team (länk till “Organize supporting functions”) are common when a wide spectrum of competencies are involved.

    Implementation recommendations

  • A list with External Dependency is established during Sprint Planning. The list contains information on dependencies, actions and who is responsible for the action to be resolved until the Commitment – point....
  • Learn more...

    Sprint Planning – How do we reach the Sprint goal?

  • The Product Owner is accountable for the Product backlog, he or she should have the Product backlog in shape when entering Sprint Planning so that the development team can pull PBI’s [länk till Agile word book] into Sprint backlog...
  • Implementation recommendation

    Daily Scrum is an event in Scrum framework. It’s the event with shortest duration of inspect and adapt loop - 24 hours. Each team member shares what he or she is up to and if anything hinders from moving towards Sprint goals. It's about making the most out of today's working day (carpe-diem), to generate most value with the knowledge team has right now.
    Click Here...

    External Dependencies

    list of arguments used to keep track of external dependencies that needs to be sorted out before Sprint Planning commitment.

    Availability and competence mapping

    Each member in development team completes their availability before Sprint planning. Template summarizes availability for each competences area