- Case Study (45 minutes).
- Agile Transformation.
- Experienced (Ri) Practitioners.
Technical writers tackling increasing complexity for 11 years learned to adapt Agile principles to different and harder problems.
The session will explore how technical writing tasks differ from typical software development tasks, and the corresponding impact in Agile practices.
The session will also recall the story of the team between 2004 and 2014, starting with a small team to senior writers, up to a larger team with formalized meetings, then down to streamlined practices to incorporate new team members.
The session will explain in detail the unique practices that the team developed to cope with specific workloads, and the principles behind the practices.
- Yearly meetings based on four questions can challenge the status quo and turn good teams into better teams.
- Retrospectives make teams Agile, forcing the team to adapt their practices to evolving team members and to the work at hand.
- Scrum actually assumes that most learning has taken place when each sprint starts.
- Phillip Armour is an unsung guru that unified development with testing and technical writing.
- Tackle harder tasks by managing effort instead of tasks, while sharing knowledge and nurturing the team culture.
- A team can be Agile even when the surrounding organization is not Agile.