Adopting an Agile Approach to Project Management - Agile Documentation

Full Course: https://www.udemy.com/adopting-an-agile-approach-to-project-management/?couponCode=PROMONOW


Organizational Requirements
If you remember the earlier example that involves developing a database for a group of hospitals, your organization requires that you document your plans and have them approved before work proceeds.
For example, you're required to create a communications management plan before work on the database starts.
Agile Documentation
This doesn't mean you can't adopt an agile approach to the project. The Agile Manifesto values working software over comprehensive documentation – but this doesn't imply that agile teams don't need to create any documents at all.
Agile development requires just enough documentation. Creating unnecessary documentation is considered a waste of valuable development time.
Examples of Agile Documentation
Examples of types of documents that are considered a waste are formal change requests, detailed design plans and scope statements, lists of items that are likely to change, and minutes of team meetings.
Documents that are considered necessary include backlogs, task boards, user stories, and burn-down charts. These track customer requirements and a team's progress in meeting them.
Specific Requirements
You can apply agile principles while still meeting company requirements for specific documentation. This involves keeping the documentation to a minimum, including only the level of detail likely to be needed during a project.
Instead of drafting a 12-page communications management plan, for instance, you might create a one- page table that simply lists stakeholders with their roles, levels of involvement in the project, and contact details.
Exercise - Agile Approach to Documentation
So, to keep it agile, let’s try to practice.
You're updating a retailer's web site to include an online shopping cart. Company policy stipulates that your team should create a design plan of the user interface, or UI, for the customer to sign off on. You're discussing this with your team.
What is it appropriate to say, given the agile approach to documentation?
1. "We should create a simple, high-level plan of the main interface features – including too much detail will just add to the need for later changes and updates."
2. "We'll need to query the policy – as an agile team, we can't waste time creating documents like this. Our only focus has to be on creating a working web site."(...)

Full Course: https://www.udemy.com/adopting-an-agile-approach-to-project-management/?couponCode=PROMONOW