Embed Size (px)
Citation preview
MSc. Business InformaticsResearch PresentationRobert Bradbury
The Development of Software Project Management Methods in support of Agile adoption in Organisations
Informatics Research Centre, Henley Business School
23 March 2011
Assumptions
●PRINCE 2●Agile adoption is increasing – nature of use
is changing from standalone projects to corporate programmes
●Organisations still need to capture proven project factors ?
●Model developed to ensure a repeatable process
Robert Bradbury
Slide 1 Robert Bradbury
Challenges for Stakeholders
Stage vs. Time driven
- Nerur, RadhaKanta Mahapatra, Mangalaraj, 2005
Slide 2 Robert Bradbury
Key Findings from Research
●K. Richards, 2007 still using stage-driven development
●Need for a balance between extreme methodologies to
effectively reflect projects
“strong processes can help a firm improve quality and
productivity …, potential trade-offs exist with respect to
creativity and innovation”.
- Cusumano et al., 2009
●Benefits of a mixed methodology approach:
“To make the most of established methodologies and
frameworks, a combine/mix approach is required to get the
best results”
- Rehman A. and Rashid H., 2007
Slide 3 Robert Bradbury
Slide 4 Robert Bradbury
Aims and Objectives of Research
A1: Investigate control and management features in Agile software developmentO1.1: Analyse Agile projects semiotically
O1.2: Develop hypotheses for control in Agile environments
A2: Identify individual elements of PRINCE 2 that can add control for any specific development sprints
O2.1: Identify elements of PRINCE 2 2009 which bring
control methodology
(differing from the 2005 version that K.Richards research based on)
O2.2: Consider how Agile factors trigger the need for PRINCE 2 elements
Slide 5: Aims and Objectives of Research Robert Bradbury
A3: Develop a model for structuring control in Agile projects
O3.1: Speculate formulae for the application of
PRINCE 2 elements tailored to feature
methodologies
O3.2: Inductively develop and validate the model in
different environments
Slide 6: Aims and Objectives of Research Robert Bradbury
Slide 7: A3: Develop a model for the structuring of Agile projects Robert Bradbury
Hypotheses (from work on objectives in Aims 1 & 2)
●Apply more higher order control (from Semiotic Framework) in Agile management
●Apply Management Products from PRINCE 2
●Use dynamic, feature-specific methodologies
Model Screenshots
Slide 8: A3: Develop a model for the structuring of Agile projects Robert Bradbury
Slide 9: A3: Develop a model for the structuring of Agile projects Robert Bradbury
Organisation Specific Configuration
Slide 10: A3: Develop a model for the structuring of Agile projects Robert Bradbury
Structural Management Specific Configuration
Slide 11: A3: Develop a model for the structuring of Agile projects Robert Bradbury
Project Overview Page – Role and Feature Selection
Slide 12: A3: Develop a model for the structuring of Agile projects Robert Bradbury
Stakeholder Survey
Slide 13: A3: Develop a model for the structuring of Agile projects Robert Bradbury
Stakeholder Data Capture
Slide 14: A3: Develop a model for the structuring of Agile projects Robert Bradbury
Model Processing
Slide 15: A3: Develop a model for the structuring of Agile projects Robert Bradbury
Evaluation of Closeness to Stakeholder Expectations(Results Folder)
Evaluation
Slide 16 Robert Bradbury
A1: Investigate control in software project management
A2: Identify elements of PRINCE 2 that can add control
A3: Develop a model for structuring control in Agile projects
