We are currently implementing Agile in our organisation and have been going through all of our documentation and templates that we will be using in future. I want to ensure that we're moving away from the typical "heavy" communication documentation and move into a more versatile approach towards communication presentation and delivery.
Do other PMs have a good/best practice that they'd like to share with us?
Best regards,
Emily. Saving Changes...
Sort By:
arlene trimbleAssistant IT Director| Local GovernmentAlamo, Ca, United States
A good start is to keep the project charter, task board, and risk board Saving Changes...
Sergio Luis ConteHelping to create solutions for everyone| Worldwide based OrganizationsBuenos Aires, Argentina
First, you have to understand that agile is not a method or methdology, agile is not software or IT related only, agile is not the manifesto. You can apply agile with any type of life cycle, with any type of method you use today to perform project management in your organizaiton. But if you are thinking to start agile implementation by using a method then documentation will depend on the method. For example, if you take a look to SCRUM or DSDM you will find the documentation you need. Remember: generally speaking agile is a way to behaive and thinking based on client and quality. And key to quality is to deliver value to the client. That could be a driver to decide about documentation. Saving Changes...
