The Sprint Methodology in Agile Project Management

From apppm
Revision as of 17:29, 11 February 2018 by Sarah (Talk | contribs)

Jump to: navigation, search

Contents

Abstract

Breaking down projects into smaller parts is paramount to being adaptive and agile as well as for maintaining the interest and momentum towards stakeholders [1]. Working in sprints facilitates a quick and continuous review of results allowing regular feedback and thereby keeping on the right path towards a successful project for all parties involved. This iterativeness thus challenges the traditional way of conducting projects, which is characterised by much robustness and formalities.

This article investigates relevant aspects of the sprint methodology in agile project management. First, the concept and purpose behind sprints is described, leading to the further description of the actual application of the method. Second, even though sprints are challenging the traditional way of running project where the latter is insufficient, there are also some limitations and risks involved with running projects in sprints. These limitations and risks are discussed taking offset in relevant and recent research results and material, which are questioning the risk management processes in agile project management. Finally, relevant references for further reading are outlined allowing the reader to investigate the different matters further.


Sprints

What

What characterises sprints and agile project management?

Why

Purpose of running projects in sprints.

How

Application of tool.

(make figure?)

Limitations

Risk Management

Annotated Bibliography

References

  1. Winch, G.M. (2010) Managing Construction Projects: An Information Processing Approach, Second Edition. Oxford: Wiley-Blackwell Publishing
Personal tools
Namespaces

Variants
Actions
Navigation
Toolbox