Agile Data Warehousing Project Management

Agile Data Warehousing Project Management

Volumn , Issue , 2013, Pages

  Hughes, Ralph ^a  

^a NONE

Author keywords

[No Author keywords available]

Indexed keywords

EID: 85013896798     PISSN: None     EISSN: None     Source Type: Book    
DOI: 10.1016/C2011-0-06103-3     Document Type: Book

References (121)

1. Ambler, S. (2005), Agile modeling: effective practices for modeling and documentation, http://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, Accessed September 2011. http://www.agilemodeling.com/essays/initialArchitectureModeling.htm.
4. Ambler S.W., Lines M. Disciplined agile delivery: a practitioner's guide to agile software delivery in the enterprise 2012, IBM Press.
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, on 2011-09-07T13:00:23 Accessed September 2011. http://www.everyspec.com.
11. Ericson, J., (2006, April). A simple plan, information management magazine, Accessed September 2011. http://www.information-management.com/issues/20060401/1051182-1.html.
12. Fairbanks G.H. Just enough software architecture: a risk-driven approach 2010, Marshall & Brainerd.
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 1999, October 30, Addison-Wesley Professional, 1999, October 20. 1st ed.
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 2006, Addison-Wesley Professional.
18. Larman C. Agile and iterative development: a manager's guide 2004, Pearson Education, Upper Saddle River, NJ.
19. Maurer F., Martel S. On the productivity of agile software practices: an industrial case study 2002, University of Calgary, Department of Computer Science, Alberta, Canada, 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 2003, Addison-Wesley Professional.
22. Reynolds C. Introduction to business architecture 2010, Course Technology PTR.
23. Royce W.W. Managing the development of large software systems. Proceedings, IEEE WESCON 1970, August, Institute of Electrical and Electronics Engineers, New York.
24. Schwaber, K. (2004, March 10). Agile project management with scrum (Microsoft professional).
25. The Standish Group International, 1995. The Chaos Report. Accessed February 2007. http://www.standishgroup.com.
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), http://www.tdwi.org.
28. Vingrys, K., 2011m, August 17. Gaining momentum with agile, Accessed April 2012. http://www.thoughtworks.com/sites/www.thoughtworks.com/files/files/kristan-vingrys-gaining-momentum-with-agile.pdf.
29. Ambler S.W. Generalizing specialists: improving your IT career skills. Agile Modeling 2011, http://www.agilemodeling.com>.
30. Advanced Development Methods (ADM) 1995. Controlled chaos: living on the edge. Accessed February 2007. http://www.controlchaos.com/download/LivingontheEdge.pdf.
31. Astels D. Test-driven development: a practical guide: a practical guide 2003, July 12, Prentice Hall. 1st ed.
32. Beck K. Extreme programming explained: embrace change 1999, Addison-Wesley Professional.
33. Beck K. Test driven development 2002, November 18, Addison-Wesley Professional. 1st ed.
34. Behrens P. Scrum gathering-enterprise adoption. Agile Executive Blog 2005, http://trailridgeconsulting.com/blog/?m=200511, Accessed February 2007.
35. Boehm, B. (1988, May). Spiral model of software development and enhancement. Computer; 21, no. 5: 61-72, Accessed February 2006. http://sunset.usc.edu/csse/TECHRPTS/1988/usccse1988-500/usccse1988-500.pdf.
36. C3 Team, Chrysler goes to extremes. Distributed Computing, Accessed February 2007. http://www.xprogramming.com/publications/dc9810cs.pdf.
37. Control Chaos 2007, Controlled-chaos software development, Accessed February 2007. http://www.controlchaos.com/download/Controlled-ChaosSoftwareDevelopment.pdf.
38. Goldratt E. Theory of constraints 1990, North River Press, Great Barrington, MA.
39. Péraire, C., Edwards, M., Fernandes, A., Mancin, Enrico, and Carroll, K., (2007, July). The IBM rational unified process for system z, http://ibm.com/redbooks.
40. Jacobson, I., Booch, G., and Rumbaugh, J. (1999, February 14). The unified software development process.
41. Lines, M., (2012, April 6). Incremental delivery of consumable solutions requires discipline, disciplined agile delivery, Accessed May 2012. http://www.disciplinedagiledelivery.com.
42. McCarthy J. Dynamics of software development 2006, Microsoft Press, Redmond, WA.
43. Project Management Institute A guide to the project management body of knowledge 2008, December 31, Pmbok Guide. 4th ed.
44. Royce W.W. Managing the development of large software systems. Proceedings, IEEE WESCON 1970, August, Institute of Electrical and Electronics Engineers, New York.
45. Schwaber K. Agile project management with scrum 2004, Microsoft Press, Redmond, WA.
46. The Standish Group International 1999, Chaos: a recipe for success. Accessed April 2006. http://www.standishgroup.com.
47. Takeuchi H., Nonaka I. The new new product development game. Harvard Business Review 1986, Jan.-Feb.:137-146.
48. Ambler, S. (2008, May 7). Has agile peaked? Dr. Dobb's, http://www.drdobbs.com/architecture-and-design/207600615.
49. Cohen J. Statistical power analysis for the behavioral sciences 1988, Routledge Academic. 2nd ed.
50. Collier K.W. Agile analytics: a value-driven approach to business intelligence and data warehousing 2011, Addison-Wesley Professional.
51. The Standish Group International. 1999. Chaos: a recipe for success. Accessed April 2006. http://www.standishgroup.com.
52. Woodward E., Surdek S., Ganis M. A practical guide to distributed scrum 2010, July 1, IBM Press.
53. Ambler S. Introduction to user stories. Agile Modeling (Web site) 2003, http://www.agilemodeling.com/artifacts/userStory.htm, Accessed December 2011.
54. Bower G.H., Black J.B., Turner T.J. Scripts in memory for text. Cognitive Psychology 1979, 11(2):177-220.
55. Bruce P., Pederson S.M. The software development project: planning and management 1982, John Wiley & Sons.
56. Burton, S. (2011, April 28). User stories, http://blog.chaione.com/better-user-stories.
57. Cockburn A. Writing effective use cases 2001, Addison-Wesley Pearson Education.
58. Cockburn, A. (2008). A user story is to a use case as a gazelle is to a gazebo (blog), Accessed December 2011. http://alistair.cockburn.us.
59. Cohn M. User stories applied: for agile software development 2004, March 1, Addison-Wesley Professional.
60. Cohn, M. (2005, September 26). Writing effective user stories for agile requirements, http://www.mountaingoatsoftware.com/system/presentation/file/64/SDBP2005_EUS.pdf?1267636390.
61. Davies, R. (2001). The power of stories, white paper presented at XP2001 conference, Accessed December 2011. http://www.agilexp.com/presentations/PowerOfStories.pdf.
62. Jeffries R. Extreme programming adventures in C# 2004, February 4, Microsoft Press.
63. Leffingwell, D. (2006, April). Agile Journal (webzine), "Agile at scale: 7 + 7 practices for enterprise agility, Accessed December 2011. http://www.agilejournal.com/articles/columns/column-articles/33-agile-at-scale-77-practices-for-enterprise-agility.
64. Lucas, 2011. http://www.capitalcamp.org/sites/default/files/slides/Crafting-Great-User-Stories.pdf.
65. 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 2004, NASA Johnson Space Center, http://ntrs.nasa.gov/archive/nasa/casi.ntrs.nasa.gov/20100036670_2010039922.pdf Accessed December 2011.
66. Pichler, R. ,(2010). Writing good user stories, http://www.romanpichler.com/presentations/pdfs/WritingGreatUserStories.pdf.
67. Pischler, R. (2011, March). All Things Product Owner (blog), The product backlog board, Accessed December 2011. http://www.romanpichler.com/blog/product-backlog/product-backlog-board.
68. Suzanne and Robertson, J. (1999), Mastering the requirements process.
69. Rosenberg D. Use case driven object modeling with UML 1999, Addison-Wesley, Indianapolis.
70. Wake, B. (2003, August 17). INVEST in good stories, and SMART tasks, http://xp123.com/articles/invest-in-good-stories-and-smart-tasks.
71. Nielsen, (2011). ConneXions lifestage group distribution, Accessed January 2012. http://www.claritas.com/samples/sitereports/connexions_lg_11.pdf.
72. Schwaber, K. (2004, March 10). Agile project management with scrum (Microsoft Professional).
73. Silverston, L. (2001). The data model resource book.
74. The Data Warehousing Institute 2011, TDWI data modeling: data analysis and design for BI and data warehousing systems (course book), http://www.tdwi.org.
75. Spewak S.H. Enterprise architecture planning: developing 1993, Wiley. 2nd ed.
76. Kimball Group (2011), Kimball Forum, dimensional modeling and data architecture, Accessed February 2012. http://forum.kimballgroup.com.
77. Zachman J.P. The zachman framework evolution. Zachman International (Web site) 2011, http://www.zachman.com/ea-articles-reference/54-the-zachman-framework-evolution
78. Camerer C.F., Johnson E.J. The process-performance paradox in expert judgment: how can experts know so much and predict so badly?. Towards a general theory of expertise: prospects and limits 1991, Cambridge Press, New York. K.A. Ericsson, J. Smith (Eds.).
79. Cohn, M. (2005, September 26). Writing effective user stories for agile requirements, http://www.mountaingoatsoftware.com/system/presentation/file/64/SDBP2005_EUS.pdf?1267636390.
80. DeMarco T. Controlling software projects 1986, Prentice Hall, Upper Saddle River, NJ. 1st ed.
81. Goode E. Among the inept, researchers discover, ignorance is bliss 2000, January 18, New York Times, http://www.nytimes.com/library/national/science/health/011800hth-behavior-incompetents.html, Accessed April 2007.
82. Jairus, H. and Lum, K.T. (2002). Improving software size estimates by using probabilistic pairwise comparison matrices. Accessed April 2007. http://trs-new.jpl.nasa.gov/dspace/bitstream/2014/37964/1/04-0903.pdf.
83. Janis I.L. Groupthink. Psychology Today 1971, 5(6). 43-46, 74-76.
84. Jorgenson, M. et al., (2000). Human judgment in effort estimation of software projects, Proceedings of the 22nd international conference on software engineering. Accessed March 2007. http://www.cs.uvic.ca/icse2000/papers/2_Survey/p12.pdf.
85. 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.
86. Jorgenson, M. and Sjoberg, D. (2006),Expert estimation of software development work: learning through feedback. Accessed March 2007. http://www.simula.no/research/engineering/publications.
87. Kimball R. Data warehouse role models. Data Warehouse Architect 1997, August, http://www.kimballgroup.com/html/articles_search/articles1997/9708d05.html, Accessed October 2011.
88. Kimball, R. (1998, September). Data warehouse architect, Help for hierarchies, Accessed October 2011. http://www.kimballgroup.com/html/articles_search/articles1998/9809d05.html.
89. Little, T. (2004). Agility, uncertainty, and software project estimation. Accessed March 2007. http://www.agilealliance.org/show/1418.
90. Miranda E. Improving subjective estimations using the paired comparisons method. International Forum on COCOMO and Software Cost Estimation 2000, Accessed March 2007.
91. McConnell S. Software estimation: demystifying the black art 2006, Microsoft Press.
92. Project Management Institute, (2008), December 31. A guide to the project management body of knowledge (Pmbok Guide,4e).
93. The Standish Group International. (1999). Chaos: a recipe for success. Accessed April 2006. http://www.standishgroup.com.
94. Bank for International Settlements (2012). About the basel committee, Accessed June 2012. http://www.bis.org/bcbs/about.htm.
95. Burns L. Building the agile database: how to build a successful application using agile without sacrificing data management 2011, Technics publications, LLC.
96. Date C.J., Darwen H., Lorentzos N.A. Temporal data and the relational model: a detailed investigation into the application of interval and relation theory to the problem of temporal database management 2003, Elsevier Ltd., Oxford.
97. Kalido, (2008). Kalido dynamic information warehouse technical overview, http://www.kalido.com.
98. 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
99. Linstedt, D. and Graziano, K. (2011). Super charge your data warehouse, createspace.
100. Linstedt, D., Graziano, K. and Hultgren, H. ( 2009). The new business supermodel. The business of data vault modelling, 2nd ed., http://Lulu.com.
101. 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.
102. The Economist,(2007, July 26). Five years of Sarbanes-Oxley.
103. Zachman J.A. A framework for information systems architecture. IBM Systems Journal 1987, 26(3):276-292.
104. Ambler, S.W. (2009). Scaling agile software development: reality over rhetoric, IBM, http://aplndc.com/eventSlides/Year2009/2009-03-ScalingAgileSoftwareDevelopment-ScottAmbler-March2009.pdf.
105. 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.
106. Anderson D., Anderson L.A. Beyond change management: how to achieve breakthrough results through conscious change leadership 2010, October, Pfeiffer. 2nd ed.
107. Connors R., Smith T. Change the culture, change the game: the breakthrough strategy for energizing your organization and creating accountability for results 2011, January 4, Portfolio Hardcover.
108. Charan R. What the CEO wants you to know: how your company really works 2001, Crown Business.
109. Bell S., Orzen M. Lean IT, enabling and sustaining your lean transformation 2010, Productivity Press, ISBN 978-1-4398-1757-5. Shingo Prize Research Award 2011.
110. Clark B., Horowitz E., Westland C., Madachy R., Selby R. Cost models for future software life cycle processes: COCOMO 2.0. Annals of software engineering special volume on software process and product measurement 1995, J.C. Baltzer AG, Science Publishers, Amsterdam, The Netherlands. J.D. Arthur, S.M. Henry (Eds.).
111. 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.
112. Connors R., Smith T. Change the culture, change the game: the breakthrough strategy for energizing your organization and creating accountability 2011, Portfolio Hardcover.
113. Glazer, H. et al. (2008, November). CMMI or Agile: why not embrace both! (CMU/SEI-2008-TN-003), TECHNICAL NOTE, software engineering institute, Accessed March 2012. http://www.sei.cmu.edu/reports/08tn003.pdf.
114. Hughes, R. (2008). Agile data warehousing, iUniverse.
115. Hughes R. Enterprise BI architecture groups: the key to effective agile data warehousing programs. Data Integration, BI & Collaboration 2011, Cutter Consortium, Arlington, MA, Vol. 11, No. 5.
116. Ladas C. Scrumban-essays on kanban systems for lean software development 2009, Modus Cooperandi Press.
117. Pettit R. An 'agile maturity model?'. Agile Journal 2006, http://www.agilejournal.com/articles/columns/the-agile-manager/52-an-qagile-maturity-modelq
118. Schwaber, K. (2004, March 10). Agile project management with scrum (Microsoft Professional).
119. Software Engineering Institute (SEI),(2006). CMMI for Develoment (v1.2). Accessed August 2007. http://www.sei.cmu.edu/cmmi/models.
120. Tuckman B. Psychological Bulletin. Developmental sequence in small groups 1965, 63(6):384-399. PMID 14314073. 10.1037/h0022100.
121. Watkins M. The first 90 days: critical success strategies for new leaders at all levels 2003, September 18, Harvard Business Review Press.