Align project activities to achieve goals
Source (project/general)
Best practice
See page body for best practices
Challenge
Projects perceived internal delivery standards vs. speed of delivery
Added by
What is the quality standard that we think we need to have achieved before going public with a work product at the end of a Season?
What is the business metric that we want to achieve by going public?
Can we do more damage by delivering a beta into the public?
Are we proud of the work we delivered so far?
Discussion results:
- It is vital to define KPIs for the success of a project in a sufficient level so everyone knows the common goal and can work towards that goal.
- However, even clearly defined KPIs will leave some room for interpretation. Depending on the individual quality ambitions of each team member the assessment, whether a KPI has been reached can differ. How should a project champion deal with a situation, where the teams perception is that the KPIs has not been reached with sufficient quality but the project champion thinks that the quality is sufficient?
- It is okay if the project champion decides on this basis that the KPI is reached and in the specific case that we discussed this would go in line with a decision to release to public.
- Ideally, releases are not to be up for decision in general but should follow a cadence. Only in circumstances where the product manager feels that the quality of the release is insufficient, the release would be delayed. So flipping the angle of viewing around and release as a standard with an exception process for the product manager
- Generally we want to foster a positive and optimistic view on our work products as a DAO. This means that If there is a way to take a positive, optimistic angle of view on something, we should make it a point to take this angle. Is there a way to be proud of our work, if yes, the team should be proud? Is there a way to tell a great narrative about our work results, the team should tell it?