What would be the main difference in documentation for predictive and agile approach?
I assume the main documentation such as Charter, stakeholder register, risk register etc can be used for both approaches. Does someone have more detailson this? Saving Changes...
Sort By:
Sergio Luis ConteHelping to create solutions for everyone| Worldwide based OrganizationsBuenos Aires, Argentina
First thing is to understand that predictive and adaptive are not right ways to call a project. Worst when those are related to agile approach. In fact, agile frameworks like Scrum are predictive. Unfortunately lot of people and organizations contribute to that. Second, the documentation will depends on the method/framework you select but mainly for your defined project governance process. Saving Changes...
Use the documentation you need for your given situation, not as prescribed by a framework/methodology/approach/whatever. Using Scrum as an example, Scrum is focused on a single team delivering potential value via product. Scrum doesn't care about compliance or other business needs that don't affect development tasks, as long as they're not interfering with the team's ability to produce. Task related risk is addressed as part of the task, but there is no ceremony for reviewing the risk register, or risk items that are not related to tasks.
Scrum doesn't effectively address stakeholders, in the traditional sense. You get the vague impression that the PO is supposed to do something with them to define stories, in the CSPO class, and that the SM gives them status and might go to them to help remove obstacles from the team. These are things that need to happen, and if you have experience with traditional project management you might have a good idea of what is involved. Scrum doesn't care, in a sense, because it was created for developers - it is a framework for product, not project, management.
Like I said at the beginning, use the documentation and tools you need (emphasis on the word 'need'). Some approaches emphasize protecting the development team from anything beyond development, but they weren't created with your project or organizational context in mind. Saving Changes...
There are some generalizations which can be made but context counts. In a non-regulated domain with the team being empowered to make the majority of delivery decisions, delivery information might be captured in a minimally sufficient manner using wikis, sticky notes or other such tools. However, where organization standards or regulations dictate, more formal templates might still need to be used.
The purpose behind the documents don't change but how the information is captured might.
Kiron Saving Changes...
Thomas WalentaGlobal Project Economy ExpertHackenheim, Germany
Project Managers understand that they have to predict a lot and have to be agile at the same time. The artificial dichotomy predictive/agile creates mostly confusion.
As Aaron said, use the documentation required for your project situation and your product's lifecycle. Scrum (as most used approach labeled agile) does not give you guidance, PMBoK Guide some guidance on useful documentation to support communication and gather data (plans, reports, lists, charts etc). Saving Changes...
Mehdi AlibakhshiPM Specialist and Instructor| PHSABritish Columbia, Canada
Liya both predictive and Agile approaches require certain documentation, but the content, format, and level of detail may differ. In a predictive approach, the documentation is typically more extensive and detailed because the project scope, requirements, and plan are all defined upfront. This documentation includes a detailed project plan, requirements documentation, design documents, change management plan, risk management plan, etc. The project manager is responsible for ensuring that the documentation is complete and up-to-date, and that it is used as a baseline for managing the project. In contrast, Agile documentation is more flexible and lighter in nature because the approach focuses on delivering working software and adapting to change rather than following a predefined plan. For example, in Scrum practice documentation includes user stories, product backlog, sprint backlog, sprint planning notes, sprint review notes, and retrospective notes. The Agile team is responsible for creating and maintaining the documentation, which should be just enough to support the development process. However, it's important to note that the level of documentation can vary depending on the specific project and organization. Some Agile projects may require more documentation due to regulatory or compliance requirements, while some predictive projects may use a lighter documentation approach to increase agility and responsiveness to change. Overall, the main difference in the documentation for predictive and Agile approaches is the level of detail and the amount of upfront planning required.
...
1 reply by Liya Gabdrakhmanova
Mar 17, 2023 2:45 AM
Liya Gabdrakhmanova
...
Mehdi, thank you so much! This is the answer I was looking for.
Saving Changes...
Stéphane ParentSelf Employed / Semi-retired| Leader MakerPrince Edward Island, Canada
Your documentation should be like any other backlog item: it should add value. Don't document just for the sake of documenting; document because the effort of capturing information is eclipsed by its value. Saving Changes...
Liya both predictive and Agile approaches require certain documentation, but the content, format, and level of detail may differ. In a predictive approach, the documentation is typically more extensive and detailed because the project scope, requirements, and plan are all defined upfront. This documentation includes a detailed project plan, requirements documentation, design documents, change management plan, risk management plan, etc. The project manager is responsible for ensuring that the documentation is complete and up-to-date, and that it is used as a baseline for managing the project. In contrast, Agile documentation is more flexible and lighter in nature because the approach focuses on delivering working software and adapting to change rather than following a predefined plan. For example, in Scrum practice documentation includes user stories, product backlog, sprint backlog, sprint planning notes, sprint review notes, and retrospective notes. The Agile team is responsible for creating and maintaining the documentation, which should be just enough to support the development process. However, it's important to note that the level of documentation can vary depending on the specific project and organization. Some Agile projects may require more documentation due to regulatory or compliance requirements, while some predictive projects may use a lighter documentation approach to increase agility and responsiveness to change. Overall, the main difference in the documentation for predictive and Agile approaches is the level of detail and the amount of upfront planning required.
Mehdi, thank you so much! This is the answer I was looking for. Saving Changes...
Latha Thamma reddiSr Product and Portfolio Management (Automation Innovation)| DXC TechnologyMckinney, Tx, United States
I hope if dogs ever take over the world, and they choose a king, they don't just go by size, because I bet there are some Chihuahuas with some good ideas.
Community Champion
