Mind shift for End-user documentation in Agile MethodologyVijay Kulkarni
schedule 1 year agoSold Out!
After a successful release, the product manager feels extremely happy that the team met the commitments and delivered the software on time. However, when he probes the actual users for the feedback, the first reaction is “documentation sucks”. Why does this happen? Most of the developers and testers still follow the traditional approach of involving documentation folks towards the end of the release! This is paradoxical because when you have development and testing happening in agile approach how can you have documentation in traditional approach?
This session deals with the mindshift change that the entire value chain needs to make end-user documentation a critical part of the scrum team deliverables and bring it on equal pedestal as any other deliverable.
It emphasizes that technical writers should not feel marginalized with the fast paced development, testing, and delivery cycles. Instead, they must work very closely with the developers and testers because they no longer require to sit outside the room and walk in only after the bell rings! And the developers, testers, product owners should not consider documentation folks as the last leg of the product delivery cycle. They must all work as an integrated team, start-to-finish.
Challenges and Best Practices: Creating Customer Focused Documentation in an Agile FrameworkTony Xavier
schedule 1 year agoSold Out!
Agile is an increasingly popular development method primarily used by software companies. In Agile software development, work is confined to a regular, repeatable work cycle, known as Sprint. A sprint typically lasts for two to three weeks. In Agile, development teams strive to deliver a fully functioning, high quality, and potentially shippable product increment at the end of each sprint. Hence, product documentation becomes an essential part of the sprint deliverable to meet stakeholder requirement. Since, the primary focus of Agile development is to deliver products with high quality, technical communicators are expected to create customer focused documentation with high quality.
Creating Customer focused documents involves paying great attention to needs and opinions of customers, and creating documents with a purpose. As writers we must ensure that the documents we create focus on the needs of the actual customers of the document and provides value. As writers we must identify who the potential customer(s) for our documentation are, what they require, and create minimal documentation that they actually need. By understanding the needs of our customers we will be able to deliver customer focused documentation with high quality. However, the combination of Agile’s high speed of development, short delivery cycles, and limited requirements documentation presents a unique set of challenges in creating customer-focused documentation.
This paper highlights some of the challenges writers face and provides best practices that can be used in creating customer-focused documentation in an Agile framework.