This is the governing body for certification in Disciplined Agile.
LIVE CHAT 24 HOURS PER DAY
Drennan, interesting point about near-located offices/cubicles. We've reworded the trade-offs associated with those options.
We're just about to publish Chapter 1 of the book which goes more into how to apply it in practice. We talk about retrospectives there, similar to what you're saying.
Based on our conversation on Tuesday during the webinar I found it quite remarkable when you suggested tailoring of process goals during the retrospective. Perhaps to include under trade-offs in the Process Tailoring Workshop decision point:
Sessions can be several hours long, so it’s better to organize the workshop into twothree: one early in Inception for Inception work and one later during Inception for Construction and Transition and one during the Retrospective.
Under Near-located offices (Trade-offs):
We just posted an update to this excerpt. Several improvements based on feedback (thanks!). The most noticeable change is the addition of the Select Lifecycle decision point.
Good points about open space areas, collaboration styles, and organize tool environment. Will update.
Your points about tailoring the process sounds like a good blog topic for you.
@Jerry: Good point. Operational monitoring tools was a missing category.
Physical Environment --> open space problems
I just want to notify a possible huge disadvantage of an open-space-based work environment that does not have cost-free rooms for periodical or ad-hoc team meetings. In some cases, teams and organizations that want or claim to be Agile need to rent a meeting room for a day for thousands of dollars. The main cost is not the cost of the meetings, but the cost of skipping needed meetings. Cave and commons where there is no cave to host a full team are a non-sense.
Choose collaboration styles -> strategy & tactics
We need a collaboration strategy at the very beginning of the development because most important activities that need collaboration are early in the life-cycle. In the same time, a team needs to be able to adapt this style according to the needs. So collaboration style needs all types of “modeling”: envisioning, look ahead, iteration and ad-hoc.
Choose collaboration styles -> Remote Pairing, Code reviews
That kind of activity requires composite support with different tools: audio calls (eventually video), screen share, remote work tools.
Tailor Initial Process -> The essence
The most important part of process tailoring is related to any concrete process decision pear each process goal during the life-cycle. Formal or informal, with more or less DA support, the team should be aware that any practices related decisions (beyond roles and others) it is a core-tailoring of the process.
In the initial process, significant inputs are
IMPORTANT – the whole inception level work is, in fact, the main workshop for initial process tailoring
It is also expected that:
More: it is also expected that a team working on a product will capitalize its experience and will adopt a continuous improvements approach.
More: it is also expected that organization will capitalize teams’ experiences and will work to share this experience across teams
Organize Tool Environment -> Agile Tools vs. Agile Process confusions
Too many times teams and organization are confusing Agile supporting tools with the Agile itself. Some of the most common examples are Continuous Integration, Continuous Deployments, DevOps. The organizations will buy more or less expensive tools and will expect agility with too few attenbtion for People and Process.
I propose to change the options titles for “Continuous Integration” and “Continuous Deployments”: “Support for Continuous Integration” and “Support for Continuous Deployments” and also to specify that CI and CD cannot be achieved only from tools (or “procedures”), but are the final results of an overall improvement. Simple example: how many teams that have JUnit tools installed are really using TDD?
One of the category of tools that we need to set-up for Digital Products such as Mobile is crash analytics tools or monitoring tools. We also set up tools (analytics) to track user interactions to get feedback on usage etc. That way the developers get fast feedback on defects and what caused the issue and the UX designers get fast feedback on how products are being used. Tools such as Microsoft Application Centre provide crash analytics and product usage analytics. Microsoft Application Insights more in depth analysis. On the Digital Products that we are doing these tools need to be set-up as part of the work environment goal that we undertake.
I just posted the excerpt for the Form Work Environment process goal. Please post your feedback as responses to this topic.
Thanks in advance!
© 2013-2019 Project Management Institute, Inc.
14 Campus BoulevardNewtown Square, PA 19073-3299 USA