agile > chapter 1 the agile approach > 10 agile work process for projects

Agile Work Process for Projects

Agile can be used to manage projects, products, services and teams. This article discusses the average work process for an agile project. It is NOT a blueprint to be used for every type of agile project.

Work process

The general steps involved are:

  1. Feasibility study - the creation of a business case to validate the undertaking of a project
  2. Project letter - to authorize use of company resources and to indicate the official commencement of the project. It consists of:
  1. Project charter - we begin by asking who is the product for
  2. Personas - these are the archetypes of the users of our product
  3. Requirements - are usually written as user stories and form a list we refer to as the project backlog/requirement stack; prioritization is done based on the business value each requirement brings; some methods are MoSCoW and Kano
  4. Project roadmap - divides the project into iterations
  5. Planning poker (this is very problematic in reality because team members can find it stressful to assign points to tasks for which we may not know the amount of work involved)
  6. Designing delivery packages (deciding which tasks to do first after factoring in technical dependencies)
  7. Plan the 1st iteration
  8. Execute the first iteration
  9. Demo/review of the results of the 1st iteration
  10. Retrospective on the 1st iteration
  11. Rinse and repeat

Parties defined in the agile approach