2013
DOI: 10.1007/978-3-642-44930-7_14
|View full text |Cite
|
Sign up to set email alerts
|

Exploring the Tensions between Software Project Portfolio Management and Agile Methods: A Research in Progress Paper

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
3
1
1

Citation Types

0
7
0
1

Year Published

2016
2016
2023
2023

Publication Types

Select...
4
1

Relationship

1
4

Authors

Journals

citations
Cited by 6 publications
(8 citation statements)
references
References 31 publications
0
7
0
1
Order By: Relevance
“…This makes portfolio-level agility hard to achieve as corporate strategy may change relatively slowly even in a dynamic environment (Rumelt, 2011). What research that does look at common purpose suggests the articulation and sharing of purpose is particularly challenging in agile where individual projects, operating myopically in silos, may prioritise individual customer needs above the portfolio (Sweetman & Conboy, 2013). Furthermore, software departments are often viewed as "order takers" (J.…”
Section: Common Purposementioning
confidence: 99%
See 1 more Smart Citation
“…This makes portfolio-level agility hard to achieve as corporate strategy may change relatively slowly even in a dynamic environment (Rumelt, 2011). What research that does look at common purpose suggests the articulation and sharing of purpose is particularly challenging in agile where individual projects, operating myopically in silos, may prioritise individual customer needs above the portfolio (Sweetman & Conboy, 2013). Furthermore, software departments are often viewed as "order takers" (J.…”
Section: Common Purposementioning
confidence: 99%
“…While software projects rarely operate in isolation and generally contribute to some broader portfolio or organisational agenda (De Reyck et al, 2005;Hatzakis, Lycett, & Serrano, 2007), agile project management increases the number of interactions at the portfolio level. This is because agile's increased focus on the customer increases complexity at the portfolio level as agile projects in a portfolio must reconcile tensions between customer needs and organisational strategy (Sweetman & Conboy, 2013). In addition, the autonomy and improvisation inherent in agile methods have implications for a portfolio of interdependent agile projects as greater coordination is needed between dynamic projects to ensure the emergent portfolio remains aligned to the intended portfolio.…”
Section: Introductionmentioning
confidence: 99%
“…Adopting traditional portfolio management is challenging for agile and lean software companies . In contrast with the iterative nature of agile methods, traditional portfolio management constitutes a linear process, which also views development as a separate phase to identifying, prioritizing, allocating, balancing, and reviewing the offerings in a portfolio .…”
Section: Portfolio Management In Agile and Lean Software Companiesmentioning
confidence: 99%
“…Today, a growing number of software companies have adopted agile and lean approaches to be successful in global markets; software companies must incorporate frequently changing customer requirements during product and service development, without compromising on quality. However, the adoption of agile and lean approaches in the software industry has brought about challenges in the management of products and services in companies' portfolios . Kalliney reports on the lack of awareness of the impacts of agile and lean approaches to portfolio management when a company begins to adopt them.…”
Section: Introductionmentioning
confidence: 99%
See 1 more Smart Citation