" />

Disciplined Agile Delivery Adherence Check


Working in partnership with Giles Lindsay, a Certified Disciplined Agilist, Certified Scrum Master and Enterprise Agile Coach we have developed the Disciplined Agile Delivery Adherence Check. This check concentrates on the fundamental principles of the Disciplined Agile Delivery framework, it enables the team to understand if they have the basic operational concepts are in place. Getting this established will allow you to work on the real meaning of being agile, if you are not adopting some of the framework principles the team should ask why and discuss how they should adopt them as part of their continuous improvement process.

To see a sample project select Demo

Getting a high score does not mean you are fully agile, there is more to agile than passing a test, but it does mean you are on the path to success! Each question encourages you to think, some questions are very factual and can be answered easily, others are more subjective and need further thought and evidence to answer correctly.

Giles Lindsay



Disciplined Agile Delivery
Project Name:
information Select a project to asses, this will enable you to display your score on the company awards page (if you have selected to display awards in your profile).

To add a new project select ‘New Project’ and add the project name, this new project will appear in the drop down.

Maturity Model Rating
Score 1
Score 2
Score 3
Score 4
Score 5
information You can display your rating on the awards page by changing the setting in your profile.
To access your profile click on your login name, top right of this page.
You can also embed this rating on your own web page by using the code provided on your profile page.
Level 1 - Initial
Framework is not being adopted
Level 2 - Managed
Very Low adoption of framework
Level 3 - Defined
Low adoption of framework
Level 4 - Quality
Good adoption of framework
Level 5 - Optimised
Full adoption of framework
Analysis


Adherence Questions Compliance Quality
Team Lead
informationYes - There is evidence that the team work in this way.
No - The team have major impediments preventing them working in this way.
N/A - There is a justifiable reason why the team do not work this way.
informationRed - The team have major or moderate impediments which prevents them achieving this to a standard they are happy with.
Amber - The team sometimes achieve this, but not often.
Green - The team always achieve this.
N/A - There is a justifiable reason why the team do not work this way.
Is there a Team Lead?
Can the Team Lead describe their role and responsibility?
Does the Team Lead regularly coach and promote self-organisation within the Development Team?
Does the Team Lead regularly coach and promote cross-functionality within the Development Team?
Does the Team Lead remove impediments to the Development Team’s progress?
Does the Team Lead ensure the Team have the goal of addressing stakeholder needs?
Does the Team Lead facilitate the DAD events/ceremonies?
Does the Team Lead support the Product Owner find techniques for effective Product Backlog management?
Does the Team Lead facilitate the Team to create clear and concise Product Backlog items?
Does the Team Lead support the Product Owner in understanding the product planning in an empirical environment?
Does the Team Lead ensure the Product Owner knows how to arrange the Product Backlog to meet their needs?
Does the Team Lead support the Product Owner understanding and practising DAD?
Does the Team Lead coach the organisation in its adoption of DAD?
Does the Team Lead facilitate/implement changes that increases the productivity of the Team?
Does the Team Lead work with other Team Leads to increase the effectiveness of the application of DAD in the organisation?
Product Owner
Is there a Product Owner?
Is the Product Owner the only person who tells the Development Team what to work on?
Does the Product Owner clearly express the Product Backlog items?
Does the Product Owner groom and order the items in the Product Backlog?
Does the product Owner optimise the work the Team perform to meet their needs?
Does the Product Owner ensure that the Product Backlog is visible, transparent, and clear to all, and shows what the Team will work on next?
Does the Product Owner ensure the Team understands items in the Product Backlog?
Does the Product Owner ensure each Backlog item has a Definition of Done?
Does the Organisation respect the Product Owners decisions?
The Team
Is the Team self-organised and choose how best to accomplish their work?
Is the Team cross-functional and have all of the skills as a team necessary to create a product Increment?
Does the team have an Architecture owner?
Does the team know the seven disciplined agile principles and abide by them?
Does the team know the Disciplined Agile Manifesto?
Is there a clear stakeholder for the solution being developed?
Are there the appropriate specialists within the team to support the delivery of the solution?
Are there independent tester(s) to ensure the quality and confirm the definition of done?
Are there domain experts to support the delivery of the solution?
Are there technical experts in the team to support the delivery of the solution?
Is there integrator within the team to ensure the solution can work within the chosen environment?
Is the Development Team between 3 and 9 members?
Inception Phase
Has a goal diagrams been created?
Has the required view types been established?
Has the level of detail required to capture the stakeholders needs been agreed?
Has the modelling strategy been established and agreed?
Has the work item management strategy been established and agreed?
Have the non functional requirements been captured?
During the Inception phase have all the team roles (primary and secondary) been established and assigned?
Has the team developed a Common Vision for meeting the Product Owners needs?
Has the solution been aligned with the companies enterprise direction?
Has the initial scope been explored, established and agreed?
Has the Initial Technical Strategy been explored, established and agreed?
Has a Initial Release Plan been developed?
Has funding been secured?
Has the required working environment been created (physical environment, virtual environment, tools etc.)
Have the risks been identified, captured and documented?
Has the Initial Test Strategy been developed?
Iteration Planning
Does the entire team participate in the Iteration Planning?
Are the Iteration Planning sessions held at the beginning/before an Iteration?
Does the Team Lead ensure that the Iteration Planning takes place?
Does the Team Lead ensure that attendants to Iteration Planning understand its purpose?
Does the Team Lead encourage the Team to keep the Iteration Planning within the time-box?
Is the Iteration Planning time box maintained (Eight hours for a one-month Iteration or for shorter Iterations less than eight hours)?
Does the Team forecast the Product Backlog items which it will be delivering in the Iteration?
Does the Team establish a Iteration goal during the Iteration Planning?
Does the Team self-organise to undertake the work in the Iteration Backlog?
Do the attendants to Iteration Planning understand its purpose?
Does the Product Owner help to clarify the selected Product Backlog items to be developed during the Iteration?
Can the Team renegotiate the selected Product Backlog items with the Product Owner?
Is the Team able to explain to the Product Owner and Team Lead how it intends to work as a self-organising team to accomplish the Iteration Goal and create the anticipated Increment?
Iteration
Does each new Iteration start immediately after the conclusion of previous Iteration?
Are the maximum length of the iteration one month?
Do all the iterations have the same length?
If needed during the Iteration is the scope clarified and re-negotiated between the Product Owner and Team?
Are the quality goals maintained during the Iteration?
Are changes requested during the Iteration that would endanger the Iteration Goal managed so there is no impact?
Is the Product Owner the only person with authority to cancel the Iteration?
Are incomplete Product Backlog items re-estimated and put back on the Product Backlog?
Daily Coordination Meeting
Does the Team Lead ensure that the Team has the Daily Coordination Meeting?
Is the Team responsible for conducting the Daily Coordination Meeting?
Does the Team Lead teach the Development Team to keep the Daily Coordination Meeting within the 15-minute time-box?
Is the daily Coordination Meeting up kept to 15 minutes long and members remain standing?
Does the Daily Coordination Meeting cover what the team have completed since the last meeting?
Does the Daily Coordination Meeting cover what the team are working on now?
Does the Daily Coordination Meeting cover any impediment that prevents the Team from meeting the Iteration Goal?
Is the Daily Coordination Meeting held at the same time and place each day?
Does Team Lead ensure the appropriate Team members participate in the Daily Coordination Meeting?
The Iteration Review
Are the Iteration Reviews performed at the end of every Iteration?
Is the Iteration Review time box maintained (Four-hour for one-month Iteration or for shorter Iteration less than four hours)?
Does the Team Lead ensure that the Iteration Review takes place?
Does the Team Lead ensure that the attendants understand the Iteration Review purpose?
Does the Iteration Review attendees include the Primary and Secondary Teams?
Does the Product Owner explain what Product Backlog items have been “Done” and what has not been “Done”?
Does the Team discuss what went well during the Iteration, what problems it ran into, and how those problems were solved?
Does the Team demonstrate the work that it has “Done” and answers questions about the Increment?
Does the Product Owner discuss the Product Backlog as it stands, and likely completion dates based on progress to date (if needed)?
Does the Iteration Review provide valuable input to subsequent Iteration Planning?
Does the Iteration Review discuss how the marketplace, potential use of the product, or Product Owner needs might have changed and what is the most valuable thing to do next?
Does the Iteration Review discuss the time line, budget, potential capabilities, and marketplace for the next anticipated release of the product?
Is the output of the Iteration demonstrated to the team and relevant stakeholders/sponsor?
Iteration Retrospective
Does the Iteration Retrospective occur after the Iteration Review and prior to the next Iteration Planning?
Is the Iteration Retrospective time box maintained (Three-hour for one-month Iteration, or less for shorter Iterations)?
Does the Team Lead ensure that the Iteration Retrospective takes place?
Does the Team Lead ensure that the Iteration Retrospective attendants understand its purpose?
Does the Team Lead identify improvements that it will implement in the next Iteration?
Does the Iteration Retrospective cover what went well during the Iteration cycle?
Does the Iteration Retrospective cover what went wrong during the Iteration cycle?
Does the Iteration Retrospective cover what could be done differently to improve?
Do the team find creative solutions and develop an action plan at the end of the Iteration Retrospective?
Transition Phase
Does the transition phase contain all the required testing to enable deployment (regression, integration)
Does the transition phase contain all the required training and handover tasks for supporting the deployed solution
Does the transition phase contain all the required documentation supporting the solution