This is the governing body for certification in Disciplined Agile.
LIVE CHAT 24 HOURS PER DAY
@Aldo - Great question! I would hope that people are following agile documentation strategies for developing the vision artifact. Having just checked that section, I see that we didn't explicitly point that out. So I've updated it do so.
Level of Detail: Just a question... Would it not also good to consider a progressive elaboration of the detail over time? Place it in between the Lightweight and the Detailed views...
This allows organisations/ teams to find what their "good enough" will be for their context.
We just posted an update to this excerpt. Several changes based on feedback. The big difference is the addition of a Communicate the Vision decision point.
Hi folks, Develop Common Vision-> Capture the vision
1. Expected Outcomes: I suggest mentioning OKR as a possible method to achieve this goal when you choose this option. It seems to fit very well in this scenario.
2. Vision Statement: Some authors also refer this approach as an Agile Project Charter, Agile Business Case or a Lightweight Business Case.
@Valentin - Good catches. I like the idea of expanding the Formality options as you suggest.
@Abhishek - Good catches too. As for your point about the medium, you're right. In another conversation that I had elsewhere we identified the need for exactly that. When I post an update to the excerpt later today you'll see the addition of "Capture the Vision".
@Jerry - Agreed. I'll add something to the description of the goal to point out that someone very likely started on the vision, now the team is fleshing it out. On the lifecycle diagrams this sort of thing is indicated, initial vision and funding is a flow into Inception, but wasn't mentioned here.
Lot of good input. Thank you very much. It'll take us a few hours to update the doc and get it posted here. Stay tuned!
This goal needs to consider a paragraph of two on the overlaps with Product Management and Product Managers from the perspective of understanding the Product Vision. The initiation may differ depending upon how organisations are set-up. But if an organisation has a Product Management they may well be doing Product Discovery to establish the vision and conduct experiments to establish a common vision.
Under Develop Common Vision -> Formality. Under the tradeoffs column for the Statement of Intent option
It reads A simple conversation may all that is required ...
It perhaps should be
A simple conversation may be all that is required ...
Under Develop Common Vision: Level of Detail
it seems to me that we are stressing on the medium of communicating the vision as well as the level of detail. Could we not cover the medium of communicating the vision as a separate goal?
the last option reads Detailed ......In some cases may be a form cost-benefit analysis study.
Pardon my ignorance, but I wasn't sure what is a form cost-benefit analysis study, or did we mean formal?
Sometimes it is useful to persist (take a picture and save it) the wall diagrams for later use or just as a backup. In the case of Vision, this approach should be highly recommended because of the high importance of the Vision content.
Level of agreement – Informal agreement /Formal agreement
In the picture it is written “Informal Agreement”, but the text describes a “Formal Agreement”.
Level of agreement – Informal agreement
The type of informal agreement that I have used in many cases it is not a verbal statement of intent, but a lightweight document (~ email, eventually after a call or discussions) with an explicit agreement, but only with high-level information (not detailed). That match with “lightweight” option for Level of Detail factor.
© 2013-2019 Project Management Institute, Inc.
14 Campus BoulevardNewtown Square, PA 19073-3299 USA