Systematic Literature Review

String 1: "Agile software development" AND ("planning strategy" OR "planning method" OR "planning framework" OR "planning approach" OR "planning policy" OR "planning procedure" OR "planning system"), searched on 17-04-2018

String 2: ( TITLE ( Agile AND planning ) ) AND ( software ) AND ( LIMIT-TO ( PUBYEAR , 2018 ) OR LIMIT- TO ( PUBYEAR , 2017 ) OR LIMIT-TO ( PUBYEAR , 2016 ) OR LIMIT-TO ( PUBYEAR , 2015 ) OR LIMIT- TO ( PUBYEAR , 2014 ) ), searched on 18-04-2018

9.6.2

Exclusion criteria

Criteria Reason for exclusion

Pre-2014 articles As Agile software development is becoming more and more popular it has also become a more popular research topic. To maintain a feasible scope, it helps to include this criterion.

English language To ensure I can understand the literature and terms are used in the same way English (the most used language) No mentioning of “planning” in the abstract of a paper. No

mentioning of “planning” in an introduction chapter of a book. Planning should be in a business working environment.

Often planning is merely touched upon in literary sources.

9.6.3

Set of literature

Action Entries

Search string 1 Google Scholar 1090

Search string 1 Scopus 10

Search string 1 Web of Science 5

Total 1105 2014-present -702 English language -21 Duplicates -3 Total 379 >4 citations/year 48 No planning -29 Inaccessible -5 Total 14

Search string 2 Scopus 23

>4 citations/year -17

No planning -4

Search string 2 Web of Science 12

>4 citations/year -12

Duplicates -1

Wrong topic (after reading) -4

88

9.6.4

Final set of literature

Number Authors Title Year

S1 P Serrador, JK Pinto Does Agile work?—A quantitative analysis of Agile project success 2015 S2 EC Conforto, F Salum, DC

Amaral…

Can Agile project management be adopted by industries other than software development?

2014

S3 A Moran MANAGING AGILE. 2016

S4 A Scheerer, T Hildenbrand… Coordination in large-scale Agile software development: A multiteam systems perspective

2014 S5 HF Cervone Improving strategic planning by adapting Agile methods to the

planning process

2014

S6 JF Tripp, C

Riemenschneider…

Job satisfaction in Agile development teams: Agile development as work redesign

2016 S7 T Suomalainen, R Kuusela… Continuous planning: an important aspect of Agile and lean

development

2015 S8 VT Heikkilä, M Paasivaara, K

Rautiainen…

Operational release planning in large-scale Scrum with multiple stakeholders–A longitudinal case study at F-Secure Corporation

2015

S9 BP Douglass AGILE systems engineering 2015

S10 D Leffingwell SAFe® 4.0 Reference Guide: Scaled Agile Framework® for Lean Software and Systems Engineering

2016 S11 Torrecilla-Salinas, C.J.,

Sedeño, J., Escalona, M.J., Mejías, M.

Estimating, planning and managing Agile Web development projects under a value-based perspective

89

9.6.5

Conceptual matrix

This conceptual matrix is a summary of a larger conceptual matrix containing all found relevant information from the sources.

Table 34 SLR - conceptual matrix

Number Source Authors Year Research subjects Conclusion Mentioned strategies Key findings

1

Does Agile work?—A quantitative analysis of

Agile project success P Serrador, JK Pinto 2015

859 participants from several countries with various managerial positions

The level of Agile used in a project does have a statistically significant impact on all three dimensions of project success, as judged by efficiency, stakeholder satisfaction, and perception of overall project performance

Traditional planning, iterative methodologies, upfront planning, planning games, replanning

Agile as an iterative methodology has a positive impact to project success relative to traditional planning methods. Also, it is explained that upfront planning is required, and planning games are explained

2

Can Agile project management be adopted by industries other than software development? EC Conforto, F Salum, DC Amaral… 2014 19 medium and large-sized companies from different industry sectors considering innovative projects

The companies surveyed have some characteristics and organizational enablers similar to companies from the software industry, which is considered a source of motivation to develop and pursue the application of Agile management practices

Traditional planning, iterative methodologies, project planning responsibility, intermediate approach

It shouldn't necessary be a manager who is responsible for planning. There can also be shared responsibility within a team. This can be done in an intermediate approach which is positioned between the traditional and Agile approach

3 MANAGING AGILE. A Moran 2016 na na

Traditional planning, iterative methodologies, upfront planning, planning games, adaptive planning, customer engagement, Extreme Programming (XP), Dynamic Systems Development Methods (DSDM)/Timeboxing, Scaled Agile Framework (SAFe), Forecasting based planning, multi-tiered planning, MoSCoW prioritization, Configuration Management Planning, Increment planning

Planning poker is introduced as an example of a planning game. Furthermore, many planning methods are explained

4

Coordination in large- scale Agile software development: A multiteam systems perspective A Scheerer, T Hildenbrand… 2014 A large enterprise software development organization

Coordination strategies lie on a continuum between organic and mechanistic coordination types. If the communication network is completely interconnected, dividing into individual teams is ineffective. A purely mechanistic strategy contradicts the lean and Agile principled of empowered teams and embracing change

Upfront planning, planning games, organic planning, communication focused, strategic planning

The explanation of the continuum between organic and mechanistic planning as well as communication focused and strategic planning

90 5

Improving strategic planning by adapting Agile methods to the

planning process HF Cervone 2014 na

In order to adapt Agile planning methods, one should allow for gradual change, facilitate the adoption, obtain frequent feedback, gain trust by showing value and track progress using tools and methods

Traditional planning, iterative methodologies, Scrum model

That the use of tools and methods are important as usually Agile focuses more on communication

6

Job satisfaction in Agile development teams: Agile development as work redesign JF Tripp, C Riemenschneider… 2016 252 software- development professionals

Agile software development and planning management practices

improve job satisfaction Traditional planning, iterative methodologies

Agile software development and planning management practices improve job satisfaction

7

Continuous planning: an important aspect of Agile and lean development T Suomalainen, R Kuusela… 2015 Three large Finnish-based ICT companies with more than 1,000 employees

The research findings highlight the importance of continuous planning throughout an entire organization including the elements of continuous planning (organizational planning, strategic planning and business planning) and their tight interrelation

Traditional planning, strategic planning, continuous planning, organizational planning, roadmapping, business planning

How even with continuous planning there are different planning levels such as organizational planning and business planning. Also, that a roadmap should be a living document

8

Operational release planning in large-scale Scrum with multiple stakeholders–A longitudinal case study at F-Secure Corporation VT Heikkilä, M Paasivaara, K Rautiainen… 2015 A large Finnish software company

We identified the following ways the method ameliorates the difficult characteristics of the release planning problem: the communication between the development organization

and the Product

Management enabled by the events allows both of them to better understand the requirements from the business and the technical points of view

Traditional planning, iterative methodologies, release iteration planning method, model-based release planning

With planning for a release there has to be an understanding between the development team and management. This is actually a prioritization problem which can possibly be solved by a model

9

AGILE systems

engineering BP Douglass 2015 na na

Traditional planning, iterative methodologies, planning games, model-based release planning None

10

SAFe® 4.0 Reference Guide: Scaled Agile Framework® for Lean Software and Systems

Engineering D Leffingwell 2016 na na

Iterative methodologies, Scaled Agile Framework

(SAFe) None

11

Estimating, planning and managing Agile Web development projects under a value- based perspective Torrecilla-Salinas, C.J., Sedeño, J., Escalona, M.J., Mejías, M. 2015 A project team of four members (multi-disciplinary)

Using an Agile approach to plan, estimate and manage Web projects is a fit.

Iterative methodologies, planning games, Extreme Programming (XP), continuous planning

Business value isn't considered when playing a planning game like planning poker, this should be addressed in a different way

91