Most all project managers are familiar with this Iron Triangle of project management. When a project comes up, one must weigh the project based on the scrop, cost, and time to market. But what ever happened to the quality? Where does this come into the equation?
- Maintaining a quality focus with their team so that no feature leaves the line as undone or with known defects
- Passionately varying scope with their business partners—while always looking to deliver a high value and minimal marketable feature
The biggest takeaway from this is that the Agile project manager needs to constantly be in communication with the stakeholders, adjusting and changing per the highest priority needs of the business.
There are 4 ways we can ensure that quality is never missed within an Agile project:
- Fixing Bugs/Issues as they crop up – Adding upon technical debt is never good. Hold the line. Fix the issues as they appear.
- Frequent code reviews – Having developers pair up and spot-check each others code can be priceless for the quality of the deliverable. Never have a single source of failure.
- Sprint Reviews to include quality checks – Having frequent sprint reviews after each sprint should include the understanding that quality is a top priority. There needs to be quality attributes that can be measured by your team to ensure that quality is never missed.
- A clear definition of done - If “done” is defined a certain way, features need to be completed to the letter. No partial credit here, folks. Done can include work-done, story-done, feature-done.
Some great take-aways for those in Agile management. See more at the bottom.