Agile management promotes a project management process that encourages frequent inspection and adaptation, a leadership philosophy that encourages teamwork, self-organization and accountability, a set of best practices that allow for rapid delivery of high-quality products, and a business approach that aligns development with customer needs and company goals. It is related to extreme documentation and scrum methods.
In my experience, Agile worked great for the developers and QA/testing folks but not as well for the UX and documentation folks. The primary reason was the constant flux in what emerged when an iteration ended.
Agile and waterfall methods are utterly different—from the way projects start to the expected deliverables and release schedules. In a waterfall world, what's an IT enterprise to do? Can agile and waterfall methodologies successfully coexist? The answer is yes, for both the short-term and the long-term. In this presentation, Michele Sliger outlines how to: factor your company's business needs into existing agile processes, streamline requirements and activities and identify specific points where agile and waterfall teams must plan, coordinate, and review progress. Learn how you can make agile processes work in the real-world.
The basic idea is that very little of the documentation which gets created during software development actually gets read by the actual target audience. This article explains the problem and presents advice for addressing it.
Whether you’re integrated into an agile project team and away from other writers, or together with multiple writers on the same project, increasing collaboration is key.
When it comes to getting work done, replace written documentation with more efficient forms of communication. To guide future work, create documents at the end of the project, when everything is complete, well understood, and easy to document.
This is a description of a simple software-internals documentation format and process. It is derived from the Unified Software Development Process, simplified towards eXtreme Programming compatibility, and arranged for realisation in a plain text file.
Test-driven development or TDD is a widely accepted practice used by agile software development teams of many flavors – not only Extreme Programming teams. For each small bit of functionality they code, programmers first write unit tests, then they write the code that makes those unit tests pass. TDD is seen as a design tool, since it forces the programmer to think about many aspects of each feature before coding.
Recently, Agile Software Processes have been discussed as flexible and light-weight alternatives to established Software Engineering approaches, in order to overcome the obstacles created by the cost of producing and maintaining documents on higher abstraction levels. Depending on requirements and needs on the documents itself, Agile Documentation becomes a key issue and brings up questions on how to create, maintain and distribute documents among the team members without creating unnecessary or unjustifiable cost. This paper describes a technique allowing to produce documentation automatically, by conducting analysis on the series of development steps taken during project planning and enactment.
As Agile gains momentum as a development approach of choice, documenting design becomes a challenge. Peter Gremett shows how using a wiki to capture your design is a great way to be adaptive as you build and deliver product to customers.
A wiki represents a relatively new approach for the product teams to easily create and manage project data. Wikis are web pages that are easily editable and their ease of use ensures that that no one is excluded from making contributions to it. Any team member can edit or create wiki pages without requiring HTML knowledge by providing his/her login information.
A broader awareness of how changes can impact other things, including schedule commitments and work outside of the immediate area of change, is beneficial in terms of assessing trade-offs and benefits.
Technical and professional communicators spend a good deal of time man- aging teams and documentation projects, and their organizations are increasingly introducing new project management practices. This article introduces Agile project management strategies that were created in soft- ware development environments, exploring how these iterative strategies can complement the traditional linear project management approaches that are taught in technical and professional communication (TPC) programs. To do so, the author presents a brief history of Agile, a case study of how the author applied specific Agile strategies in a grant writing course, and a comprehensive set of tips for implementing Agile in other TPC courses.