Creating documentation within an Agile team is both challenging and rewarding. Agile moves fast and emphasizes team collaboration. Many Agile evangelists think that being Agile means no documentation. The same amount of documentation is required in Agile. The difference is when and how that documentation is created. Consider the following tips. 1. Join Daily Stand-Ups A stand-up is a short meeting where the team reports on what they’ve done, what they plan to do, and anything preventing them from doing their work. If you’re not attending, you’ll quickly fall out of sync. When attending stand-ups: Focus on team...Read More
Author: Fred Williams
Fred Williams is a highly regarded speaker, writer, and teacher. Fred recently emceed the Agile Prague conference. He wrote the free Technical Writing Course at Wikiversity, certifies technical writers worldwide, and is a specialist in creating integrated Waterfall/Agile requirements specifications. Able to speak several languages, he now lives in Prague, Czech Republic, where he founded the Open Learning Center and Williams Technical. His latest projects, which include an innovative process for integrating remote technical writers into Agile teams, have been well received by the Agile community, software startups, and government institutions.
Receive exclusive access to members-only content, invitations to in-person and virtual events, and sneak peeks at new tools and emerging technologies. Join today!Join Now!
- The RoundUp: Emojis, Voice Interfaces, Conversational Commerce, and Artificial Intelligence
- The Power of Incrementalism in Content Marketing Strategy
- [May 31] DITA Summit: Best Practices and Lessons Learned From The Trenches
- Seven Habits of Highly Effective Technical Writers
- Digital Transformation: Information Development World