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.
#27609
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.
Shore, James. JamesShore.com (2006). Articles>Documentation>Agile>Extreme Documentation
#27587
USDP-Distilled eXtreme Documentation
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.
Ainsworth, Harrison. HXA7241 (2004). Articles>Documentation>Agile>Extreme Documentation
#27591
Using Design Rationales for Agile Documentation 
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.
Sauer, Thomas. IEEE Digital Library (2004). Articles>Documentation>Agile>Extreme Documentation
#27585
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.
Ferlazzo, Ellen Lawson. XProgramming.com (2002). Articles>Documentation>Agile>Extreme Documentation
#32156
Documentation and Agile Software Development
What’s it like doing documentation as part of an Agile software development team? Why is it a better way of working? I mull this over these and other questions with Graham Campbell.
Christie, Alistair and Graham Campbell. ITauthor (2008). Articles>Documentation>Agile>Podcasts
#32352
How Much Should You Document? Everything? Strategies for an Agile Environment
Some agile environments move so fast, you have to triage what you document because there’s no time to document everything.
Johnson, Tom H. I'd Rather Be Writing (2008). Articles>Documentation>Agile
#32997
Adopting User-Centered Design Within An Agile Process: A Conversation 
eXtreme Programming and other agile processes provide a middle ground between chaos and over-elaborate processes sometimes referred to as 'death by documentation'. A particular attrtactive aspect of the agile approach for many teams is its willingness to accomodate change no matter how advanced development might be. However, this very flexibility can cause user interface design issues and ensuing usability problems. Adopting a user-centered approach to user interface design can address these issues, as the following simulated conversation between a user-centered design consultant and an XP team leader will explain.
Hudson, William. UIaccess (2002). Articles>User Centered Design>Agile>Project Management
#33454
Agile Development Projects and Usability
Agile methods aim to overcome usability barriers in traditional development, but pose new threats to user experience quality. By modifying Agile approaches, however, many companies have realized the benefits without the pain.
Nielsen, Jakob. Alertbox (2008). Articles>Project Management>Usability>Agile
#33588
RITE differs from a “traditional” usability test by emphasizing extremely rapid changes and verification of the effectiveness of these changes. Specifically, practitioners make changes to the UI (prototype or application) as soon as the problem is found and the solution spotted. Changes such renaming buttons, changing the text of menu items often happen before another participant arrives. More complicated, but obvious changes are made as rapidly as possible. This way the change can be tested as quickly as possible.
Levison, Mark. InfoQ (2008). Articles>Usability>Collaboration>Agile
#33640
Getting Real About Agile Design
Agile is here to stay. The economic difficulties of the past months have finally put waterfall out of its misery; now more than ever, long requirements phases and vaporous up-front documentation aren’t acceptable. Software must be visible and valuable from the start. For many designers, Agile is already a fact of life (and for those less accustomed, some recommended reading follows at the foot of this article). We are reaching the point where we must either acclimatize or risk being bypassed. The good news is that Agile does allow us to still do the things we hold dear—research, develop a vision, and test and improve our designs—we just need new techniques. Now is the time to get real, and prove design can adapt, if we want to stay relevant in these increasingly unreal times.
Bowles, Cennydd. List Apart, A (2008). Articles>Web Design>Agile>Project Management
#33988
Three panellists talk about how they've applied agile development techniques to XML, followed by audience discussion and Q&A: Tony Coates will discuss XML and schema quality assurance using unit test frameworks. David Carver will discuss agile XML schema development. Claudia Lucia Jimenez-Guarin will discuss software construction for evolving systems with incomplete data definition.
Carver, David, Anthony Coates and Claudia Lucía Jimenez-Guarin. XML 2006 (2006). Articles>Information Design>XML>Agile
#34496
Using Customer Tests to Drive Development
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.
Agile Journal (2009). Articles>User Centered Design>Agile>Functional Specifications
#34751
Using Wikis to Document UI Specifications
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.
Gremett, Peter. Boxes and Arrows (2009). Articles>User Interface>Agile>Wikis
#35040
Agile Documentation with uScrum
uScrum (uncertainty Scrum) is an agile process developed by a small team at Altitude Software to manage the process of writing user documentation. uScrum manages uncertainty and the unknown, allowing writers to quickly react to changing conditions. uScrum uses orders of ignorance to understand the difficulty of tasks, allowing the team to effectively prioritize regular work together with difficult creative work.
Baptista, Joaquim. ACM SIGDOC (2008). Articles>Documentation>Agile>Scrum
#35192
Corporate Collaborative Authoring
The idea of a Book Sprint is that you can get lots of documentation written in a focused amount of time with the right team and some amount of content already in place. Gathering people in the same room when possible is extremely helpful and motivating as well.
Gentle, Anne. Just Write Click (2009). Articles>Collaboration>Agile>Documentation
#35354
The Impact of Agile on User-Centered Design 
Discusses the impact of an agile software development process on usability testing. Reports opinions about usability testing within a company before and after a change to agile. Presents strategies to incorporate usability testing into agile product development.
Dayton, David and Carol S. Barnum. Technical Communication Online (2009). Articles>User Centered Design>Collaboration>Agile
#35421
Authoring in an Agile Environment
It's a simple fact of life. Developing products in today's world requires shorter cycles, sensitivity to customer needs, and a focus on deliverables that breaks the old waterfall development paradigm. More and more there is a need for teams to focus on the entire development process and deliver precisely what customers need with little or no fluff. As products move towards the user-centric model of product development the push is for more intuitive interfaces with little need for documentation -- or does it really?
Vazquez, Julio J. SDI Global Solutions (2009). Articles>Documentation>Collaboration>Agile
#35538
When I’ve read Agile practitioner reports that tell tales of times when technical writers have left meetings and fled to cry, I am not just surprised but a little dismayed.
Gentle, Anne. Just Write Click (2009). Articles>Collaboration>Agile
#35658
Traditional, heavyweight development methodologies can be very effective at solving well‑defined problems, where the person solving the problem has a clear understanding of the initial and goal states, the available options, and the constraints on the problem. At the opposite end of the spectrum are ill‑defined, so-called wicked problems. When it’s necessary to balance numerous, often‑conflicting factors, traditional development methodologies are much less effective.
Hornsby, Peter. UXmatters (2009). Articles>User Experience>Agile
#35715
Agile User Experience Projects
Agile projects aren't yet fully user-driven, but new research shows that developers are actually more bullish on key user experience issues than UX people themselves.
Nielsen, Jakob. Alertbox (2009). Articles>Project Management>User Experience>Agile
#35803
Five Skills for Managing Documentation Projects in an Agile Environment 
Sometimes, the Agile software development methodology seems like it could be renamed the “Fly by the Seat of Your Pants” methodology. But really, it means that you need a somewhat different set of project management skills for your documentation. I could certainly improve in these skills, but here are a few I rely on in an Agile environment.
Minson, Benjamin. Gryphon Mountain (2009). Articles>Documentation>Technical Writing>Agile
#35811
Agile Works Best in PHP Projects
Agility includes effective, that is, rapid and adaptive, response to change. This requires effective communication among all of the stakeholders. Stakeholders are those who are going to benefit from the project in some form or another. The key stakeholders of the project include the developers and the users. Leaders of the customer organization, as well as the leaders of the software development organizations, are also among the stakeholders.
Abeysinghe, Samisa. Packt (2007). Articles>Web Design>Agile>PHP
