Agile Scrum for Technical Writers
•Download as PPTX, PDF•
0 likes•45 views
This document discusses how Agile Scrum methodology can be applied to technical writing and documentation teams. It defines Agile Scrum, describing the roles of Product Owner, Scrum Master, and Scrum Team Members. The Scrum process involves planning, sprints, retrospectives, and releases. Benefits include quicker delivery, flexibility, and collaboration. Challenges include transitioning from traditional methods and managing changes. The document proposes how a documentation lifecycle could integrate with Scrum through prioritizing documentation, assigning tasks in sprints, and getting stakeholder feedback.
Recommended
More Related Content
Similar to Agile Scrum for Technical Writers
Similar to Agile Scrum for Technical Writers (20)
More from Raghuram Pandurangan
More from Raghuram Pandurangan (18)
Recently uploaded
Recently uploaded (20)
Agile Scrum for Technical Writers
- 1. Agile Scrum for Technical Writing -Raghuram Pandurangan
- 2. Agenda • What is Agile Scrum? • The roles and responsibilities of Scrum team members • The Scrum process • Benefits of using Agile Scrum • Challenges of using Agile Scrum • DDLC & Agile Scrum
- 3. Before Agile
- 4. Before Agile – Waterfall Model
- 5. Before Agile – Iterative Model
- 6. What is Agile Scrum? • Agile Scrum is an iterative and incremental software development framework. • It is based on the following principles: • Individuals and interactions over processes and tools • Working software over comprehensive documentation • Customer collaboration over contract negotiation • Responding to change over following a plan
- 8. Agile Scrum Roles & Responsibilities
- 10. Scrum Team • The Scrum Team consists of three roles: • Product Owner • Scrum Master • Scrum Team Members
- 11. Product Owner • The Product Owner is responsible for: • Defining the product vision • Prioritizing the product backlog • Communicating with stakeholders
- 12. Scrum Master • The Scrum Master is responsible for: • Ensuring that the Scrum process is followed • Removing impediments to the team's progress • Coaching the team on Scrum
- 13. Scrum Team Members • The Scrum Team Members are responsible for: • Developing the product increment • Testing the product increment • Delivering the product increment • Scrum Team Members in S/W Dev. Teams • Software Developers • Tester or QA • Technical Writer • UI/UX Designer
- 15. Scrum Process • The Scrum process is divided into four phases: • Planning • Sprint • Retrospective • Release
- 16. User Story in Agile Scrum
- 18. Benefits of using Agile Scrum • Agile Scrum can help teams to: • Deliver working software more quickly • Respond to changes in requirements more easily • Improve communication and collaboration between team members • Increase customer satisfaction
- 19. Challenges of using Agile Scrum • Agile Scrum can be challenging for teams that are not used to working in an iterative and incremental way. • It can also be difficult to manage change in an Agile Scrum environment.
- 20. DDLC Process Planning •Requirements Gathering •Audience Analysis Designing • Deliverables • Tools, style guides • Templates Creating content • TOC • Iterative content Reviewing •Technical •Editorial review Integrating feedback Publishing & Compiling Maintaining versions
- 21. Agile Scrum for Docs Team • Create a documentation backlog: Track all of the documentation that needs to be created or updated. • Prioritize the documentation backlog: Not all documentation is created equal. Some documentation is more important than others. Prioritize the documentation backlog so that you can focus on the most important documentation first. • Assign documentation tasks to the Scrum team during sprint planning: This will help to ensure that documentation is created and updated on a regular basis. • Create documentation sprints. This will help to focus the Scrum team on creating or updating documentation without being interrupted by other tasks. • Get feedback from stakeholders. This will help you to ensure that the documentation is meeting the needs of the stakeholders. • Keep the documentation up-to-date. This will help to ensure that the documentation is always accurate and up-to-date.
- 22. DDLC in Agile Scrum Methodology
- 23. References • Apart from references specified in the notes: • Intro to Scum in 10 mins: https://www.youtube.com/watch?v=XU0llRltyFM • Scrum vs Kanban: https://www.youtube.com/watch?v=pxxmSLJj8FQ • Agile Methodology Tutorial for Beginners: https://www.youtube.com/watch?v=KNBHQ0pyaG8 • Software Development Lifecycle: https://www.youtube.com/watch?v=i- QyW8D3ei0
Editor's Notes
- Reference: http://www.ascezen.com/2013/11/documentation-development-agile-development-models/
- Reference: https://www.atlassian.com/agile/scrum/scrum-master
- Reference: https://www.scruminc.com/the-3-5-3-of-scrum/
- Reference: https://www.netsolutions.com/insights/user-stories-in-agile/
- Pic Courtesy and further reference: https://www.visual-paradigm.com/scrum/what-is-scrum/
- DDLC Video: https://www.youtube.com/watch?v=FMCI8otTx38 The Documentation Development Life Cycle (DDLC) is a process for creating and maintaining documentation. It is typically divided into four phases: planning, development, review, and maintenance. The planning phase involves identifying the need for documentation, defining the scope of the documentation, and creating a project plan. The development phase involves writing the documentation, creating illustrations and diagrams, and testing the documentation. The review phase involves getting feedback from stakeholders and making revisions to the documentation. The maintenance phase involves keeping the documentation up-to-date and making changes as needed. The DDLC can be integrated with the Agile Scrum methodology in a number of ways. One way is to create a documentation backlog, which is a list of all the documentation that needs to be created or updated. The documentation backlog can be prioritized along with the product backlog, and documentation tasks can be assigned to the Scrum team during sprint planning. Another way to integrate the DDLC with Agile Scrum is to create a documentation sprint, which is a sprint dedicated to creating or updating documentation. During a documentation sprint, the Scrum team can focus on creating or updating documentation without being interrupted by other tasks. By integrating the DDLC with Agile Scrum, teams can ensure that documentation is created and maintained in a timely and efficient manner. This can help teams to deliver high-quality software that meets the needs of stakeholders.