Summary
In this chapter, we set a primary goal for this book of identifying the sweet spot between agile, feedback-driven software processes and disciplined, plan-driven software processes. We then dissected a software process into its subcomponents and analyzed each subcomponent individually, discussing the trade-offs that you can make within each layer. We followed that with a “fact or fiction” discussion that focused on the human-centric communication issues related to software process.
The next chapter presents a brief introduction to ICONIX Process, a use case-driven approach that uses a minimalist core subset of UML. In Chapter 4, we’ll next attempt to define a minimalist core subset of agile practices. Then we’ll see how close we came to the sweet spot by exploring the design and code for our example project.
This is a preview of subscription content, log in via an institution to check access.
Access this chapter
Tax calculation will be finalised at checkout
Purchases are for personal use only
Preview
Unable to display preview. Download preview PDF.
References
Barry Boehm, “Get Ready for Agile Methods, with Care,” IEEE Computer, January 2002, pp. 64–69.
Doug Rosenberg and Kendall Scott, “Goldilocks and the Three Software Processes,” ObjectiveView, Issue 5, p. 35. (This article is available for download from www.iconixsw.com/Articles/Articles.html and also from www.ratio.co.uk/objectiveview.html.)
This is the Agile Modeling core practice “Iterate to Another Artifact” (Scott W. Ambler, Agile Modeling: Effective Practices for eXtreme Programming and the Unified Process [Hoboken, NJ: John Wiley & Sons, 2002], p. 44). The premise is that each modeling artifact (use case, business process diagram, robustness diagram, etc.) provides insight into a particular area, so if you find yourself getting stuck on one artifact, try switching iteratively to a different artifact to get unstuck.
Alistair Cockburn, Agile Software Development (New York: Addison-Wesley, 2001).
Ibid.
Chuck Suscheck, private e-mail to Doug Rosenberg, January 2004.
Rights and permissions
Copyright information
© 2005 Doug Rosenberg, Matt Stephens, and Mark Collins-Cope
About this chapter
Cite this chapter
(2005). Characteristics of a Good Software Process. In: Agile Development with ICONIX Process. A-Press. https://doi.org/10.1007/978-1-4302-0009-3_2
Download citation
DOI: https://doi.org/10.1007/978-1-4302-0009-3_2
Publisher Name: A-Press
Print ISBN: 978-1-59059-464-3
Online ISBN: 978-1-4302-0009-3
eBook Packages: Professional and Applied ComputingApress Access BooksProfessional and Applied Computing (R0)