Agile Delivery Kit for Software Organisations

v1.0.16

How to work in an agile way. This starter kit provides the strategies, recipes. workshops, technologies, practices, and guides that will help you and your people create a way of work that enables success.

Overview

First Principals

Index

  

1 minute to read

Last Updated: Fri 2 Jun 2023 07:26

These are the basic propositions or assumptions that the rest of the document is based on.

Principals

No items currently published...

Drafts

  • Value-based Prioritization - Focus on delivering value to the stakeholders
  • Self-Organization - Self Organizing teams have the autonomy to determine how to achieve their goals
  • Market Focus - Update the work based on market and user feedback on timelines shorter than one month
  • Empirical Process Control - Team and stakeholders should be transparent about the work, inspect the progress regularly, and adapt the plan as necessary to achieve the desired outcomes
  • Emergant Work - The work needed will emerge as we do the work and help others do it
  • Emergant Practices - Processes, practices and tools necessary will emerge as we do the work and help others do it
  • Continuous Delivery - Continuous delivery of valuable product to at least some subset of real users every iteration (including the first) and gathering feedback
  • Common Goals - All participants and stakeholders should understand the overall strategic goals and be able to see how the work contributes to it

Recommended Content

  • Manifesto for Agile Software Development (Guide)
    We are uncovering better ways of developing software by doing it and helping others do it. These are our values and principles.
  • The Scrum Guide (Guide)
    The Scrum Guide contains the definition of Scrum.
  • Kanban Guide (Guide)
    Kanban is a strategy for optimizing the flow of value through a process that uses a visual, pull-based system.
  • The Evidence-Based Management Guide (Guide)
    Evidence-Based Management (EBM) is an empirical approach that helps organizations to continuously improve customer outcomes, organizational capabilities, and business results under conditions of uncertainty.
  • Detecting Agile BS (Guide)
    The purpose of this document is to provide guidance to DoD program executives and acquisition professionals on how to detect software projects that are really using agile development versus those that are simply waterfall or spiral development in agile clothing.
Join the Community
The league of extraordinary lean-agile practitioners is a group of peers and seasoned practitioners that continuously learn, share emergent practices, and discuss topics with courage, commitment, focus, respect, & openness!
In this article