Agile Project Management

Abstract

Agile methodologies have been increasingly popular since the introduction of the Agile Manifesto in 2001. In general, the methodologies provide a set of different principles and practices for software development projects, which aims at satisfying the customer through iterative development [1]. The agile methodologies for software development are very well described in literature, but not all authors agree on the specific content of the different methodologies. This can cause a lot of confusing for any new project manager wanting to adopt the benefits of an agile approach to a project. The focus in this paper is on Agile Project Management in general, and does not describe a single specific agile methodology. This paper seeks to provide a comprehensive description of Agile Project Management, along with an application example and implementation advice. This will be done through an in-depth literature study of the state-of-the-art within this area. The aim is to provide detailed and easy to understand instructions for using the method. The goal is, that this paper can be used as a guideline for any project manager wanting to adopt an agile approach to the project management.

Introduction

Brief introduction to The Agile Manifest and to agile in general. Description of the basic agile principles, and introduction to the history of Agile Project Management. Introduction to the typical application context and requirements. 


Detailed method description

Detailed description of the Agile Project Management principles, practices and roles. Detailed description of the agile framework and terminology. Short description and brief overview of specific agile methodologies.

Application

Discussion of the general application of the method. Description of a specific application example from the author’s own experience. 


Implementation

Discussion of the pros and cons using the method. Specific implementation advice will be given. 


Conclusion

Concluding remarks 


Work templates

Templates for Sprints, Product Backlog, Sprint Backlog. 


References

[1] M. Fowler and J. Highsmith. The agile manifesto [software development]. Software Development, 9(8):28–32, 2001.