Preparing the Project

Alan Cline

Chapter Chapter 4 in Agile Development in the Real World, 2015, pp 75-90 from Springer

Abstract: Abstract In the early days of agile, agilists wanted to avoid all upfront work before the iterations of requirements, coding, and testing started: no architecture, no initial requirements, not even getting their development environment set up. (The emergent design fans still use this approach.) I think this is an overreaction to the waterfall method. The pendulum of popular development style swung from too-much-upfront work to no-upfront work. Fortunately, that pendulum is swinging back to some upfront work that some agilists call upfront learning.

Keywords: Team Productivity; User Story; Initial Requirement; Business Analyst; Technical Team (search for similar items in EconPapers)
Date: 2015
References: Add references at CitEc
Citations:

There are no downloads for this item, see the EconPapers FAQ for hints about obtaining it.

Related works:
This item may be available elsewhere in EconPapers: Search for items with the same title.

Export reference: BibTeX RIS (EndNote, ProCite, RefMan) HTML/Text

Persistent link: https://EconPapers.repec.org/RePEc:spr:sprchp:978-1-4842-1679-8_4

Ordering information: This item can be ordered from
http://www.springer.com/9781484216798

DOI: 10.1007/978-1-4842-1679-8_4

Access Statistics for this chapter

More chapters in Springer Books from Springer
Bibliographic data for series maintained by Sonal Shukla () and Springer Nature Abstracting and Indexing ().