The Sprint Methodology in Agile Project Management

From apppm
(Difference between revisions)
Jump to: navigation, search
Line 1: Line 1:
The Sprint methodology draft
+
Breaking down projects into smaller parts is paramount to being adaptive and agile as well as for maintaining the interest and momentum towards stakeholders. 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.
 
+
- Abstract of article
+
- Description of the method and its purpose
+
- Application - how do you apply the method
+
- Limitations - critically reflect on the tool/concept/theory and its application context. What can it do,
+
what can it not do? Under what circumstances should it be used, and when not? How does it compare to the “status quo” of the standards – is it part of it, or does it extent them? (Use material from course and use research articles on risks in sprint management)
+
- Annotated bibliography (3-10 references) (for further reading..)
+
 
+
% link to project, portfolio, project management and engineering systems (De Heck MIT ref.)
+

Revision as of 17:04, 11 February 2018

Breaking down projects into smaller parts is paramount to being adaptive and agile as well as for maintaining the interest and momentum towards stakeholders. 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.

Personal tools
Namespaces

Variants
Actions
Navigation
Toolbox