References

Chapter 1

1. Ambler, S. (2005), Agile modeling: effective practices for modeling and documentation, <www.agilemodeling.com>.

2. Ambler, S. (2008, May 7), Has agile peaked? Dr. Dobb’s, <http://www.drdobbs.com/architecture-and-design/207600615>.

3. Ambler, S. (2011). Architecture envisioning: an agile best practice, agile modeling, <http://www.agilemodeling.com/essays/initialArchitectureModeling.htm> Accessed September 2011.

4. Ambler SW, Lines M. Disciplined agile delivery: a practitioner’s guide to agile software delivery in the enterprise IBM Press 2012.

5. Anderson, D.J and Reinertsen, D.G. (2010, April 7). Kanban: successful evolutionary change for your technology business.

6. Beck, K. and Andres, C. (2004, November 26). Extreme programming explained: embrace change (2nd ed.).

7. Benefield, G. (2008, January). Rolling out agile in a large enterprise, proceedings of the 41st annual Hawaii International Conference on System Sciences, 1 Location: Waikoloa, HI, 461–46.

8. Cockburn, A. (2004, October 29). Crystal clear: a human-powered methodology for small teams.

9. Cohn, M. (2009, November 5). Succeeding with agile: software development using scrum.

10. Department of Defense, (1985). Military standard: defense system, software development, DOD-STD-2167, Washington, DC, <http://www.everyspec.com> on 2011-09-07T13:00:23 Accessed September 2011.

11. Ericson, J., (2006, April). A simple plan, information management magazine, <http://www.information-management.com/issues/20060401/1051182-1.html> Accessed September 2011.

12. Fairbanks GH. Just enough software architecture: a risk-driven approach Marshall & Brainerd 2010.

13. Highsmith, J.A. (1999, December). Adaptive software development: a collaborative approach to managing complex systems.

14. Hunt A, Thomas D. The pragmatic programmer: from journeyman to master 1st ed. Addison-Wesley Professional 1999, October 30; 1999, October 20.

15. Jacobson, I., Booch, G., and Rumbaugh, J. (1999, February 14). The unified software development process.

16. Jarzombek, J., (1999). The 5th annual JAWS S3 proceedings; cited in Larman 2004.

17. Kroll P, MacIsaac B. Agility and discipline made easy: practices from openUP and RUP Addison-Wesley Professional 2006.

18. Larman C. Agile and iterative development : a manager’s guide Upper Saddle River, NJ: Pearson Education; 2004.

19. Maurer F, Martel S. On the productivity of agile software practices: an industrial case study Alberta, Canada: University of Calgary, Department of Computer Science; 2002; T2N 1N4.

20. Palmer, S.R. and Felsing, J.M. (2002, February 21). A practical guide to feature-driven development.

21. Poppendieck M, Poppendieck T. Lean software development: an agile toolkit Addison-Wesley Professional 2003.

22. Reynolds C. Introduction to business architecture Course Technology PTR 2010.

23. Royce WW. Managing the development of large software systems Proceedings, IEEE WESCON New York: Institute of Electrical and Electronics Engineers; 1970, August.

24. Schwaber, K. (2004, March 10). Agile project management with scrum (Microsoft professional).

25. The Standish Group International, 1995. The Chaos Report. <http://www.standishgroup.com> Accessed February 2007.

26. DSDM Consortium and J. Stapleton (2003, January 13). DSDM: business focused development, (2nd ed).

27. The Data Warehousing Institute, 2011. TDWI data modeling: data analysis and design for BI and data warehousing systems (course book), <www.tdwi.org>.

28. Vingrys, K., 2011m, August 17. Gaining momentum with agile, <www.thoughtworks.com>, <http://www.thoughtworks.com/sites/www.thoughtworks.com/files/files/kristan-vingrys-gaining-momentum-with-agile.pdf> Accessed April 2012.

Chapter 2

1. Ambler SW. Generalizing specialists: improving your IT career skills. Agile Modeling 2011; <http://www.agilemodeling.com>.

2. Advanced Development Methods (ADM) 1995. Controlled chaos: living on the edge. <http://www.controlchaos.com/download/LivingontheEdge.pdf> Accessed February 2007.

3. Astels D. Test-driven development: a practical guide: a practical guide 1st ed. Prentice Hall 2003, July 12.

4. Beck K. Extreme programming explained: embrace change Addison-Wesley Professional 1999.

5. Beck K. Test driven development 1st ed. Addison-Wesley Professional 2002, November 18.

6. Behrens P. Scrum gathering—enterprise adoption. Agile Executive Blog 2005; <http://trailridgeconsulting.com/blog/?m=200511> Accessed February 2007.

7. Boehm, B. (1988, May). Spiral model of software development and enhancement. Computer; 21, no. 5: 61-72, <http://sunset.usc.edu/csse/TECHRPTS/1988/usccse1988-500/usccse1988-500.pdf> Accessed February 2006.

8. C3 Team, Chrysler goes to extremes. Distributed Computing <http://www.xprogramming.com/publications/dc9810cs.pdf> Accessed February 2007.

9. Control Chaos 2007, Controlled-chaos software development. <http://www.controlchaos.com/download/Controlled-ChaosSoftwareDevelopment.pdf> Accessed February 2007.

10. Goldratt E. Theory of constraints Great Barrington, MA: North River Press; 1990.

11. Péraire, C., Edwards, M., Fernandes, A., Mancin, Enrico, and Carroll, K., (2007, July). The IBM rational unified process for system z, <ibm.com/redbooks>.

12. Jacobson, I., Booch, G., and Rumbaugh, J. (1999, February 14). The unified software development process.

13. Lines, M., (2012, April 6). Incremental delivery of consumable solutions requires discipline, disciplined agile delivery, <http://www.disciplinedagiledelivery.com> Accessed May 2012.

14. McCarthy J. Dynamics of software development Redmond, WA: Microsoft Press; 2006.

15. Project Management Institute. A guide to the project management body of knowledge 4th ed. Pmbok Guide 2008, December 31.

16. Royce WW. Managing the development of large software systems Proceedings, IEEE WESCON New York: Institute of Electrical and Electronics Engineers; 1970, August.

17. Schwaber K. Agile project management with scrum Redmond, WA: Microsoft Press; 2004.

18. The Standish Group International 1999, Chaos: a recipe for success. <http://www.standishgroup.com> Accessed April 2006.

19. Takeuchi H, Nonaka I. The new new product development game. Harvard Business Review. 1986;Jan.-Feb:137–146.

Chapter 3

1. Ambler, S. (2008, May 7). Has agile peaked? Dr. Dobb’s, <http://www.drdobbs.com/architecture-and-design/207600615>.

2. Cohen J. Statistical power analysis for the behavioral sciences 2nd ed. Routledge Academic 1988.

3. Collier KW. Agile analytics: a value-driven approach to business intelligence and data warehousing Addison-Wesley Professional 2011.

4. The Standish Group International. 1999. Chaos: a recipe for success. <http://www.standishgroup.com> Accessed April 2006.

5. Woodward E, Surdek S, Ganis M. A practical guide to distributed scrum IBM Press 2010, July 1.

Chapter 4

1. Ambler S. Introduction to user stories. Agile Modeling (Web site) 2003; <http://www.agilemodeling.com/artifacts/userStory.htm> Accessed December 2011.

2. Bower GH, Black JB, Turner TJ. Scripts in memory for text. Cognitive Psychology. 1979;11(2):177–220.

3. Bruce P, Pederson SM. The software development project: planning and management John Wiley & Sons 1982.

4. Burton, S. (2011, April 28). User stories, <http://blog.chaione.com/better-user-stories>.

5. Cockburn A. Writing effective use cases Addison-Wesley Pearson Education 2001.

6. Cockburn, A. (2008). A user story is to a use case as a gazelle is to a gazebo (blog), <http://alistair.cockburn.us> Accessed December 2011.

7. Cohn M. User stories applied: for agile software development Addison-Wesley Professional 2004, March 1.

8. Cohn, M. (2005, September 26). Writing effective user stories for agile requirements, <http://www.mountaingoatsoftware.com/system/presentation/file/64/SDBP2005_EUS.pdf?1267636390>.

9. Davies, R. (2001). The power of stories, white paper presented at XP2001 conference, <http://www.agilexp.com/presentations/PowerOfStories.pdf> Accessed December 2011.

10. Jeffries R. Extreme programming adventures in C# Microsoft Press 2004, February 4.

11. Leffingwell, D. (2006, April). Agile Journal (webzine), “Agile at scale: 7 + 7 practices for enterprise agility, <http://www.agilejournal.com/articles/columns/column-articles/33-agile-at-scale-77-practices-for-enterprise-agility> Accessed December 2011.

12. Lucas, 2011. <http://www.capitalcamp.org/sites/default/files/slides/Crafting-Great-User-Stories.pdf>.

13. Haskins B, Stecklein J, Brandon D, Moroney G, Lovell R, Dabney J. Error cost escalation through the project life cycle, Proceedings of the INCOSE Symposium. NASA Johnson Space Center 2004; <http://ntrs.nasa.gov/archive/nasa/casi.ntrs.nasa.gov/20100036670_2010039922.pdf> Accessed December 2011.

14. Pichler, R. ,(2010). Writing good user stories, <http://www.romanpichler.com/presentations/pdfs/WritingGreatUserStories.pdf>.

15. Pischler, R. (2011, March). All Things Product Owner (blog), The product backlog board, <http://www.romanpichler.com/blog/product-backlog/product-backlog-board> Accessed December 2011.

16. Suzanne and Robertson, J. (1999), Mastering the requirements process.

17. Rosenberg D. Use case driven object modeling with UML Indianapolis: Addison-Wesley; 1999.

18. Wake, B. (2003, August 17). INVEST in good stories, and SMART tasks, <http://xp123.com/articles/invest-in-good-stories-and-smart-tasks>.

Chapter 5

1. Nielsen, (2011). ConneXions lifestage group distribution, <www.claritas.com/samples/sitereports/connexions_lg_11.pdf> Accessed January 2012.

2. Schwaber, K. (2004, March 10). Agile project management with scrum (Microsoft Professional).

3. Silverston, L. (2001). The data model resource book.

4. The Data Warehousing Institute 2011, TDWI data modeling: data analysis and design for BI and data warehousing systems (course book), <www.tdwi.org>.

Chapter 6

1. Spewak SH. Enterprise architecture planning: developing 2nd ed. Wiley 1993.

2. Kimball Group (2011), Kimball Forum, dimensional modeling and data architecture,<http://forum.kimballgroup.com> Accessed February 2012.

3. Zachman JP. The zachman framework evolution. Zachman International (Web site) 2011; <http://www.zachman.com/ea-articles-reference/54-the-zachman-framework-evolution>.

Chapter 7

1. Camerer CF, Johnson EJ. The process-performance paradox in expert judgment: how can experts know so much and predict so badly?. In: Ericsson KA, Smith J, eds. Towards a general theory of expertise: prospects and limits. New York: Cambridge Press; 1991.

2. Cohn, M. (2005, September 26). Writing effective user stories for agile requirements, <http://www.mountaingoatsoftware.com/system/presentation/file/64/SDBP2005_EUS.pdf?1267636390>.

3. DeMarco T. Controlling software projects 1st ed. Upper Saddle River, NJ: Prentice Hall; 1986.

4. Goode E. Among the inept, researchers discover, ignorance is bliss New York Times 2000, January 18; <http://www.nytimes.com/library/national/science/health/011800hth-behavior-incompetents.html> Accessed April 2007.

5. Jairus, H. and Lum, K.T. (2002). Improving software size estimates by using probabilistic pairwise comparison matrices. <http://trs-new.jpl.nasa.gov/dspace/bitstream/2014/37964/1/04-0903.pdf> Accessed April 2007.

6. Janis IL. Groupthink. Psychology Today. 1971;5 43–46, 74–76.

7. Jorgenson, M. et al., (2000). Human judgment in effort estimation of software projects, Proceedings of the 22nd international conference on software engineering. <http://www.cs.uvic.ca/icse2000/papers/2_Survey/p12.pdf> Accessed March 2007.

8. Jorgenson M, et al. A review of studies on expert estimation of software development effort. Document Actions Journal of Systems and Software. 2004;70(no. 1-2):37–60 <http://www.simula.no/research/engineering/publications> Accessed March 2007.

9. Jorgenson, M. and Sjoberg, D. (2006), Expert estimation of software development work: learning through feedback. <http://www.simula.no/research/engineering/publications> Accessed March 2007.

10. Kimball R. Data warehouse role models. Data Warehouse Architect 1997, August; <http://www.kimballgroup.com/html/articles_search/articles1997/9708d05.html> Accessed October 2011.

11. Kimball, R. (1998, September). Data warehouse architect, Help for hierarchies, <http://www.kimballgroup.com/html/articles_search/articles1998/9809d05.html> Accessed October 2011.

12. Little, T. (2004). Agility, uncertainty, and software project estimation. <http://www.agilealliance.org/show/1418> Accessed March 2007.

13. Miranda E. Improving subjective estimations using the paired comparisons method. International Forum on COCOMO and Software Cost Estimation 2000; <http://sunset.usc.edu/Activities/oct24-27-00/Presentations/Miranda.pdf> Accessed March 2007.

14. McConnell S. Software estimation: demystifying the black art Microsoft Press 2006.

15. Project Management Institute, (2008), December 31. A guide to the project management body of knowledge (Pmbok Guide,4e).

16. The Standish Group International. (1999). Chaos: a recipe for success. <http://www.standishgroup.com> Accessed April 2006.

Chapter 8

1. Bank for International Settlements (2012). About the basel committee, <http://www.bis.org/bcbs/about.htm> Accessed June 2012.

2. Burns L. Building the agile database: how to build a successful application using agile without sacrificing data management Technics publications 2011; LLC.

3. Date CJ, Darwen H, Lorentzos NA. Temporal data and the relational model: a detailed investigation into the application of interval and relation theory to the problem of temporal database management Oxford: Elsevier Ltd.; 2003.

4. Kalido, (2008). Kalido dynamic information warehouse technical overview, <www.kalido.com>.

5. Kent W. A simple guide to five normal forms in relational database theory. Communications of the ACM. 1983, February;26(2):120–125 <http://www.bkent.net/Doc/simple5.htm>.

6. Linstedt, D. and Graziano, K. (2011). Super charge your data warehouse, createspace.

7. Linstedt, D., Graziano, K. and Hultgren, H. (2009). The new business supermodel. The business of data vault modelling, 2nd ed., <Lulu.com>.

8. Rönnbäck L, Regardt O, Bergholtz M, Johannesson P, Wohed P. Anchor modeling—agile information modeling in evolving data environments. Data & Knowledge Engineering. 2010;69:1229–1253.

9. The Economist,(2007, July 26). Five years of Sarbanes–Oxley.

10. Zachman JA. A framework for information systems architecture. IBM Systems Journal. 1987;26(3):276–292.

Chapter 9

1. Ambler, S.W. (2009). Scaling agile software development: reality over rhetoric, IBM, <http://aplndc.com/eventSlides/Year2009/2009-03-ScalingAgileSoftwareDevelopment-ScottAmbler-March2009.pdf>.

2. Ambler, S. and Kroll, P. (2011). Applying agile and lean principles to the governance of software and systems development (white paper), IBM, <http://public.dhe.ibm.com/common/ssi/ecm/en/raw14000usen/RAW14000USEN.PDF>.

3. Anderson D, Anderson LA. Beyond change management: how to achieve breakthrough results through conscious change leadership 2nd ed. Pfeiffer 2010, October.

4. Connors R, Smith T. Change the culture, change the game: the breakthrough strategy for energizing your organization and creating accountability for results Portfolio Hardcover 2011, January 4.

5. Charan R. What the CEO wants you to know: how your company really works Crown Business 2001.

6. Bell S, Orzen M. Lean IT, enabling and sustaining your lean transformation Productivity Press 2010; ISBN 978-1-4398-1757-5. Shingo Prize Research Award 2011.

7. Clark B, Horowitz E, Westland C, Madachy R, Selby R. Cost models for future software life cycle processes: COCOMO 2.0. In: Arthur JD, Henry SM, eds. Annals of software engineering special volume on software process and product measurement. Amsterdam, The Netherlands: J.C. Baltzer AG, Science Publishers; 1995.

8. Cartlidge, A. et al., (2007). An introductory overview of ITIL V3, itSMF Ltd, 2007, itSMF Ltd, <http://www.best-management-practice.com/gempdf/itSMF_An_Introductory_Overview_of_ITIL_V3.pdf>.

9. Connors R, Smith T. Change the culture, change the game: the breakthrough strategy for energizing your organization and creating accountability Portfolio Hardcover 2011.

10. Glazer, H. et al. (2008, November). CMMI or Agile: why not embrace both! (CMU/SEI-2008-TN-003), TECHNICAL NOTE, software engineering institute, <http://www.sei.cmu.edu/reports/08tn003.pdf> Accessed March 2012.

11. Hughes, R. (2008). Agile data warehousing, iUniverse.

12. Hughes R. Enterprise BI architecture groups: the key to effective agile data warehousing programs. Data Integration, BI & Collaboration Arlington, MA: Cutter Consortium; 2011; Vol. 11, No. 5.

13. Ladas C. Scrumban—essays on kanban systems for lean software development Modus Cooperandi Press 2009.

14. Pettit R. An ‘agile maturity model?’. Agile Journal 2006; <http://www.agilejournal.com/articles/columns/the-agile-manager/52-an-qagile-maturity-modelq>.

15. Schwaber, K. (2004, March 10). Agile project management with scrum (Microsoft Professional).

16. Software Engineering Institute (SEI),(2006). CMMI for Develoment (v1.2). <http://www.sei.cmu.edu/cmmi/models> Accessed August 2007.

17. Tuckman B. Psychological Bulletin. Developmental sequence in small groups. 1965;63(6):384–399. doi 10.1037/h0022100 PMID 14314073.

18. Watkins M. The first 90 days: critical success strategies for new leaders at all levels Harvard Business Review Press 2003, September 18.