There's more to writing than typing words into an editor. You need a plan and a process. Here are our guidelines for managing your team's documentation work in an agile environment. You've probably heard the word "agile" around. Lots of people and companies are talking about "being more agile" but it's hard to know what that actually means. Honestly, "being more agile" depends on the framework your team uses.
If you like this video, subscribe to our newsletter for more updates. →
Learn the basics of creating documentation in any agile framework.Requirements Phase
This is when your team documents what users want and how you plan to deliver it within the product. Use this phase as an opportunity to begin your draft documentation.Development Phase
With your draft in hand, you'll begin working with the team to write full documentation. This phase is interesting, because the team is simultaneously building and documenting the product.Testing Phase
Test the quality of your documentation by having one or more people unfamiliar with the contents read it and provide feedback.Delivery Phase
As part of a great agile process, your documentation is ready for delivery along with your product. Publishing can be handled using one or more approaches, depending on the type of product you make.Feedback Phase
With the product and documentation in the hands of customers, you will continue to review and iterate to improve your content.
Documentation in Agile