Agile

2 minute read

General Guides

Guides Source
Agile Manifesto (2001)  
Agile Playbook Agile Alliance
Scrum Guides, 2020 Scrum Guide Ken Schwaber and Jeff Sutherland
The Agile Coach - Atlassian’s no-nonsense guide to agile development Atlassian

Methodologies

Methodologies References
Scrum


Advised for less mature teams, because it defines some rules and boundaries around a Sprint that has a defined timeframe and Goal.
  • Agile Playbook: Start with Scrum (page 15) (by Agile Alliance)
  • Scrum (by Agile Alliance)
  • Scrum Glossary (by Scrum Inc)
  • Scrumban


  • Agile Playbook: Seeing success but need a more flexibility? Move to Scrumban (page 17) (by Agile Alliance)
  • Scrumban (by Agile Alliance)
  • Kanban

    Advised for very experienced teams that have a great expertise on the process and don’t need boundaries set when Replenishment or Refinement is needed.
  • Agile Playbook: If you are ready to kick off the training wheels, try Kanban (page 18) (by Agile Alliance)
  • Kanban (by Agile Alliance)
  • Ways of Working

    Ways of Working (WoW) References
    General Ways of Working (WoW) for a SCRUM TEAM (by Paulo Caroli)
    Definition of Ready (DoR)

    Team defines the pre-requisites for a Story to be considered ready for the Engineering team. That might include Detailed Use Cases / Scenarios, Acceptance Criterias, User Flow, UI Design.
    Definition of Ready (by Jeff Sutherland)
    What is definition of ready
    Definition of Done (DoD)
    Team defines the pre-requisites for a feature/improvement to be considered done (finished) and ready for production. That might include Automated Testing, Test Coverage, Documentation, UX Validation.
    Definition of Done (by Jeff Sutherland)
    Backlog List of prioritized items that might be available soon to the Engineering team, but might not be ready yet according to DoR.

    Ceremonies

    Ceremonies References
    Daily A rapid standup (usually 15-minute) status update on work being done. Also a moment to identify roadblocks and if anyone needs help.
    Planning On a Sprint basis the team defines how much they can commit.
    Grooming / Refinement Detailing the backlog items and estimating.
    Review Present and evaluate the result of work done.
    Retrospective Understand what was done right that needs to be maintained and what needs to be improved. Usually teams use the DAKI tool (Drop, Add, Keep, Improve).

    Retrospective Tools

    Retrospective Tools References
    DAKI

    Drop, Add, Keep, Improve
  • Template by EasyRetro
  • Template by TeamRetro
  • KAML


    Keep, Add, More, Less
  • Template by FunRetrospectives
  • Template by TeamRetro
  • Template by EasyRetro
  • References

    Scrum - by Jeff Sutherland
    The Art of Doing Twice the Work in Half the Time
    Essential Scrum - by Kenneth Rubin
    A Pratical Guide to Most Popular Agile Process
    Coaching Agile Teams - by Lyssa Adkins
    A Companion for ScrumMasters, Agile Coaches, and Project Managers in Transition
    Agile Retrospectives - by Esther Derby
    Making Good Teams Great

    People to Follow

    Jeff Sutherland Jeff Sutherland
    Linkedin, Twitter
    One of the people behind the Agile Manifesto
    Paulo Caroli Paulo Caroli
    Linkedin, Twitter
    Writer of many books and creator of Team Retrospectives