Disciplined Agile

Strategies that Enable Team Governance

Figure 1 calls out several agile strategies that support the governance of Disciplined Agile (DA) teams.  

Team Governance

Figure 1. Governing Disciplined Agile Teams.

The strategies that support effective governance within DA teams include: 

  • Enterprise awareness. Enterprise awareness refers to the concept that DA teams realize that they work within your organization’s enterprise ecosystem, as do your other teams. There are often existing solutions (products and services) that should not be negatively impacted by the release of the solution they are working on. Better yet their solution will leverage existing functionality and data available in your operational infrastructure instead of reinventing the wheel. DA teams will work with other teams that are working in parallel to them, striving to leverage each other’s work. They will work towards your organization’s strategic vision. Enterprise awareness is the underpinning of effective governance. 
  • Release planning. Early in a project, or when a product team is first initiated, a DA team will invest some time in high-level release planning. They do this to identify and think through any dependencies on other teams and often to identify a reasonable cost and time estimate for the current release that they are working on. They will keep this high-level plan up-to-date as development progresses, sharing it with their stakeholders. Release planning enables the team to answer critical governance questions regarding forecasted schedule and cost. 
  • Team dashboard. The basic idea is that the tools used by your team should be instrumented to record important events when they occur. For example, your work management tool could record when a work item ticket is defined, when work begins on it, when the work is validated (if appropriate), and when it is marked done. Within a software team, whenever a build is run your build tool could record basic information such the date and time it was initiated, the time it took, the number of tests run, the number of successful tests, and so on. This sort of information, or more accurately intelligence, can be recorded in a data warehouse and later reported on using business intelligence (BI) tooling via dashboard technology at the team, program, or portfolio, or enterprise level. The real-time, accurate information radiated by a team dashboard enables the team to make better decisions and provides better transparency to stakeholders (including governance people). 
  • Information radiators. An information radiator is a visible display that shows something of interest to a team or their stakeholders. Examples include a whiteboard with an architecture sketch on it, a corkboard with index cards tacked to it, and a wall-mounted monitor showing the team’s dashboard. Information radiators enable better governance by increasing transparency. 
  • Active stakeholder participation. Active stakeholder participation is the practice of having on-site access to stakeholders, or at least their proxies (i.e. Product Owners). Active stakeholders have the authority and ability to provide information and make timely decisions regarding the prioritization and scope of requirements. This enables more effective governance through improving the team’s access to decision makers. 
  • Demos. On a regular basis, typically at the end of each iteration for teams following an agile life cycle or on an as-needed basis for lean teams, the team demonstrates the solution to key stakeholders. The team shows completed work and invites feedback. This enables effective governance by increasing transparency and providing better opportunities for stakeholders to steer the team.
  • Coordination meetings. The team meets for a few minutes, typically at the beginning of each day, to coordinate their activities. The team lead facilitates the meeting and is responsible for keeping it short and focused. This practice is often called a scrum meeting or daily stand-up meeting, although neither of those terms accurately conveys the concept that the aim is to coordinate. This enables tactical governance within the team itself through increasing internal transparency and reducing the feedback cycle within the team. 
  • Light-weight, risk-based milestones. Effective milestone reviews are as simple and short as possible. For a small co-located team a milestone review could be as simple as a few people from the governing body, or their agents, to visit the team room and have the team spend an hour walking them through whatever is to be reviewed. For larger efforts this could be upwards to half a day and be held in meeting room. Teams in regulatory environments may need to invest a bit more effort, particularly around creation and baselining of artifacts to be reviewed and recording of action items from the review. With adoption of common agile practices such as demos and team dashboards, described earlier, there will be less need for status discussions in milestone reviews. The milestones suggested by the DA tool kit are risk-based, not document based. For example, the Proven Architecture milestone is best fulfilled through development of beginning-to-end functionality that implements high-risk requirements, not the creation and review of an architecture model. 
  • Retrospectives. A retrospective is a facilitated reflection meeting performed by the team, the goal of which is to identify potential areas of improvement. Retrospectives often last thirty to sixty minutes. Retrospectives help teams to be more self-aware and improvement focused, supporting your overall governance goal of continuous improvement

These strategies support a light-weight approach to governance while improving the overall effectiveness of the team. Where traditional governance was something to be dreaded, agile governance should be something to be welcomed. 

Related Reading