Execution Principles For Autonomy
- Darcy Patten
- Jul 23, 2018
- 2 min read
Recently, I have become obsessive about creating an environment of complete empowerment and autonomy for my program. Fortunately all my team members are elite, self starting and multidisciplined so the hard part is already done. All that is left to do is to build the outline of the field and create a rule book defining how the game is played. Once finished, I should be able to sit back, relax and watch their genius at work.
To do this, we are focused on team principles that fall under 3 pillars: 1) Customer Service 2) Project Delivery and 3) Team Culture. Every pillar has multiple ground rules, each built with the following details: a) Overview b) Your Focus Should Be c) You Are Failing If d) What I Will Ask You. And finally, the entire team has full input into the creation and maintenance of their principles. Below is a single example from our Project Delivery pillar:
Make the Absolute Best
Overview
It is more important to get a rock solid core system as opposed to have a lot of features, some of which don’t work very well. This means collaborating and guiding the clients to clearly define and prioritize Minimum Viable Product (MVP) user stories. It there are alternate use cases that were not completed, that is okay, if they are important enough a second phase will be initiated.
Your Focus Should Be:
Clearly defining which users stories are Minimum Viable Product.
Ensuring MVP is fully functional before starting with the next set of MVP user stories.
Using the MVP Status Timeline to help guide the client in labeling which user stories are truly MVP.
Using the Icebox to store user stories that the budget does not allow you to complete.
You Are Failing If:
You have not clearly defined MVP User Stories that are identified in collaboration with the client.
You do not have the client testing the MVP User Stories as soon as they are complete.
You are not using a method to regularly communicate if MVP will be finished within the budget scope.
You do not clearly know and/or you are not tracking your budget.
You do not adjust your planned sprint velocity after each sprint.
What I will Ask You:
What is your sprint velocity?
Does you sprint velocity and number of sprints allow for completion of all MVP user stories?
Did you review your user stories after every sprint to constantly adjust which ones are MVP?
Did you estimate your user stories?
Now, this is just one example, but if we do this correctly, each delivery team will be able to use any estimation technique, any agile methodology, any method to communicate velocity or any method to design the solution. In fact, just like a sporting league, each team will be able to execute with any strategy that they are best at. The only problem......if it works well, the teams will no longer need a coach!
Disagree, let me know your thoughts, communication is the best way to learn!
Comments