Introduction
Overview
3 minutes to read
Last Updated: Wed 25 Oct 2023 11:15
draft
This page is in draft and may include errors or omissions. Please check the discussions for any pending updates and changes to the content or to suggest your own changes.
** Courage | Focus | Commitment | Openness | Respect **
Our best efforts have been made, rather than to dictate, to create a balance between autonomy required for self-management, and alignment required to maintain our business. Always question the content here! Always!
The first decision that needs to be made is Should we use Agile or Traditional Practices. To do that you need to decide what sort of work you are working on. If the work that you have is in Simple or Complicated environments, it is suitable to use traditional practices like PMI or Prince2. If your work is in a Complex or Chaotic environment then you should use an Empirical system like Scrum or Kanban.
Product Delivery
In the Product Delivery world, we operate in a complicated environment where we deliver many easily understood items to the customer; the outcome is known. This may be Support Tickets, a Software Factory, or another pre-built system that we are deploying or configuring. For this type of work, we should follow flow-based techniques to model our current process, and then optimise for output; more stuff.
Risk Management: Risk here is managed by more control; lists of risks and mitigating actions.
Techniques: flow-based techniques complimented at scale with PMI / Prince2 / Plan-Driven
Review: Should we use Agile or Traditional Practices?
Product Development
If we are building something that does not exist yet (all Software Engineering exists here!) then we are in a complex environment and need to use an empirical approach. Implementing an Empirical Process Control System requires transparency. Transparency is required to Inspect and Adapt our work.
We expect that you will use Scrum to manage the work, Nexus to manage many teams work, and Evidence-based Management to monitor your progress.
Risk Management: Delivery of Done increments of value every Sprint including the first.
Techniques: Empirical techniques complemented by Kanban
Review: Should we use Agile or Traditional Practices?
Are Scaling practices right for us?
TBA
Answer: Scaling Scrum
Overview of Content
- Engaging with Customers - Including a pre-sales agile mindset is imperative to enabling business agility.
- One Engineering System - We want our teams to focus on the business problem, and not on getting used to a new set of tools. 1ES provides a single recommended toolset that provides a DevOps orchestration layer that includes Work Items, Code Repositories, Build / Release.
- Learning & Development - What should I focus on learning to increase my agile mindset.
-
Core Practices - These practices are key to our ways of working are part of the alignment across the organisation.
- Accountabilities & Roles - These are the key accountabilities for [Company]
- Definition of Done - While the DOD may vary between Teams and Products, there should be a minimum bar that reflects the protection of the [Company] brand.
- Definition of Ready
- Metrics & Reporting - These are the core agile metrics and don’t reflect additional reporting that might be required by our business or the customers.
- Guides - Includes the Scrum Framework, Nexus Framework, & Evidence-based Management. These are external reference materials that are part of our WOW.
- Complimentary Practices - These Practices are not Core Practices, however, they are suggestions and ideas for things that you can get your team to try.