Book Open Access

Agile Scrum: Your Quick Start Guide with Step-by-Step Instructions

Graffius, Scott M.

Scott M. Graffius is the CEO of Exceptional PPM and PMO Solutions™, a professional services firm, where he partners with client companies to help them achieve their strategic objectives and business initiatives through project management leadership. The consultancy provides project, program, portfolio, and PMO management services inclusive of agile, traditional, and hybrid development and delivery frameworks. Business results include upgraded responsiveness to business needs, faster delivery and time-to-market, improved on-budget performance, higher customer and stakeholder satisfaction, and greater competitive advantage. 

A fantastic agile transformation experience and result with a client organization in the entertainment industry was the inspiration for Scott’s book, Agile Scrum: Your Quick Start Guide with Step-by-Step Instructions. It helps technical and non-technical teams develop and deliver products in short cycles with rapid adaptation to change, fast time-to-market, and continuous improvement—which supports innovation and drives competitive advantage. The book has garnered 17 first place awards from national and international competitions. Scott and Agile Scrum: Your Quick Start Guide with Step-by-Step Instructions have been featured in Yahoo Finance, the Boston Herald, NBC WRAL, the Dallas Business Journal, the PM World Journal, BookLife by Publisher’s Weekly, Learning Solutions, Innovation Management, and additional media publications. A trailer, high-resolution images, reviews, a detailed list of awards, and more are available in the digital media kit at

Technical editors: Chris Hare and Colin Giffen.
Files (273.1 kB)
Name Size
Agile Scrum v180210 720x1000 300dpi 279 KB.jpg
273.1 kB Download
  • Abrahamsson, P., Salo, O., Ronkainen, J., and Warsta, J. (2002). Agile Software Development Methods: Review and Analysis. Oulu, Finland: VTT Electronics.

  • Accenture (2015). Next Generation Technology Delivery. Dublin, Ireland: Accenture.

  • Acuna, S. T., Gomez, M., and Juristo, N. (2009). How Do Personality, Team Processes and Task Characteristics Relate to Job Satisfaction and Software Quality? Information and Software Technology, 51 (3): 627-639. DOI:

  • Ahola, J., Frühwirth, C., Helenius, M., Kutvonen, L., Myllylahti, J., Nyberg, T., Pietikäinen, A., Pietikäinen, P., Röning, J., Ruohomaa, S., Särs, C., Siiskonen, T., Vähä-Sipilä, A., and Ylimannela, V. (2014). Handbook of Secure Agile Software Development Life Cycle. Oulu, Finland: University of Oulu.

  • Al-Zewairi, M., Biltawi, M., Etaiwi, W., and Shaout, A. (2017) Agile Software Development Methodologies: Survey of Surveys. Journal of Computer and Communications, 5 (5): 74-97. DOI: 10.4236/jcc.2017.55007.

  • American Management Association (2016). The Quest for Innovation: A Global Study of Innovation Management. New York, NY: American Management Association.

  • Anderson, S. P. (2011). Seductive Interaction Design: Creating Playful, Fun, and Effective User Experiences. Berkeley, CA: New Riders.

  • Andrews, A., and Bevolo, M. (2004). Understanding Digital Futures. Design Management Journal, 15 (1): 50–57. DOI: 10.1111/j.1948-7169.2004.tb00150.

  • Atlas, A. (2009). Accidental Adoption: The Story of Scrum at Agile Conference, 2009: 135-140. DOI: 10.1109/AGILE.2009.10.

  • Azizyan, G., Magarian, M., and Kajko-Mattson, M. (2012). The Dilemma of Tool Selection for Agile Project Management. 7th International Conference on Software Engineering Advances (ICSEA 2012): 605-614. ISBN: 978-1-61208-230-1.

  • Bass, L., Clements, P., and Kazman, R. (2012). Software Architecture in Practice—Third Edition. Upper Saddle River, NJ: Addison-Wesley Professional.

  • Beck, K., Beedle, M., van Bennekum, A., Cockburn, A., Cunningham, W., Fowler, M., Grenning, J., Highsmith, J., Hunt, A., Jeffries, R., Kern, J., Marick, B., Martin, R. C., Mellor, S., Schwaber, K., Sutherland, J. and Thomas, D. (2001). Manifesto for Agile Software Development. Retrieved from Manifesto for Agile Software Development:

  • Boehm, B. (2002). Get Ready for Agile Methods, with Care. IEEE Computer, 32 (1): 64-69. DOI: 10.1109/2.976920.

  • Boerman, M. P., Lubsen, Z., Tamburri, D. A., and Visser, J. (2015). Measuring and Monitoring Agile Development Status. 2015 IEEE/ACM 6th International Workshop on Emerging Trends in Software Metrics, 0 (0): 54-62. DOI: 10.1109/WETSoM.2015.15.

  • Brown, K. A., Hyer, N. L., and Ettenson, R. (2013). The Question Every Project Team Should Answer. MIT Sloan Management Review, 55 (1): 49-57.

  • CA Technologies (2015). Agile Operations. New York, NY: CA Technologies.

  • Canty, D. (2015). Agile for Project Managers. Boca Raton, FL: CRC Press.

  • CEB (2015). Future of Government IT: Adaptive IT. Arlington, VA: CEB, Inc.

  • Ceschi, M., Sillitti, A., Succi, G., and De Panfilis, S. (2005). Project Management in Plan-based and Agile Companies. IEEE Software, 22 (3): 21-27. DOI: 10.1109/MS.2005.75.

  • Cho, J. (2008). Issues and Challenges of Agile Software Development with Scrum. Journal of Management Information Systems, 9 (2): 188-195.

  • Cisco (2016). How Cisco IT Uses Agile Development with Distributed Teams and Complex Projects. San Jose, CA: Cisco Systems, Inc.

  • Citigroup (2013). Disruptive Innovation: Ten Things to Stop and Think About. New York, NY: Citigroup.

  • Cohn, M. (2005). Agile Estimating and Planning. Upper Salle River, NJ: Pearson Education, Inc.

  • CollabNet (2014). Agile Project Development at Intel: A Scrum Odyssey. San Francisco, CA: CollabNet, Inc.

  • Conboy, K. (2009). Agility from First Principles: Reconstructing the Concept of Agility in Information Systems Development. Information Systems Research, 20 (3): 329-354. DOI: 10.1287/isre.1090.0236.

  • Conforto, E. C., Salum, F., Amaral, D. C., da Silva, S. L., and Magnanini de Almeida, L. F. (2014). Can Agile Project Management Be Adopted by Industries Other than Software Development? Project Management Journal, 45 (3): 21–34. DOI: 10.1002/pmj.21410.

  • DeCarlo, D. (2004). eXtreme Project Management: Using Leadership, Principles, and Tools to Deliver Value in the Face of Volatility. San Francisco, CA: Jossey-Bass.

  • Deloitte Touche Tohmatsu (2011). Don't Fear Change, Embrace It: Advancing the Case for Agile Methods in Systems Integration. New York, NY: Deloitte Touche Tohmatsu Limited.

  • Deloitte Touche Tohmatsu (2014). How FrAgile is Your Agile? Six Common Pitfalls Facing Agile Project Teams. New York, NY: Deloitte Touche Tohmatsu Limited.

  • Deloitte Touche Tohmatsu (2015). Scaling Agile at Financial Institutions: Lessons from the Trenches. New York, NY: Deloitte Touche Tohmatsu Limited.

  • Dinakar, K. (2009). Agile Development: Overcoming a Short-Term Focus in Implementing Best Practices. Pittsburgh, PA: Carnegie Mellon University.

  • Dybå, T., and Dingsøyr, T. (2008). Empirical Studies of Agile Software Development: A Systematic Review. Information and Software Technology, 50 (9-10): 833-859.

  • Economist Intelligence Unit, The (2015). Implementing the Project Portfolio: A Vital C-Suite Focus. Newtown Square, PA: Project Management Institute, Inc.

  • Ernst & Young (2014). Sustaining Digital Leadership! Agile Technology Strategies for Growth, Business Models and Customer Engagement. London, England: Ernst & Young.

  • Esposito, R., Kraenzel, C. J., Pepin, C. G., and Stein, A. I. (2011). The New Workplace: Are You Ready? How to Capture Business Value. Somers, NY: IBM Global Services.

  • Fitzgerald, B., Hartnett, G., and Conboy, K. (2006). Customising Agile Methods to Software Practices at Intel Shannon. European Journal of Information Systems, 15 (2): 200-213. DOI: 10.1057/palgrave.ejis.3000605.

  • Forbes (2016). Lessons from Leaders: Marrying the Art and Science of Performance Improvement. Jersey City, NJ: Forbes Media.

  • Freudenberg, S., and Sharp, H. (2010). The Top 10 Burning Research Questions from Practitioners. IEEE Software, 27 (5): 8-9. DOI: 10.1109/MS.2010.129.

  • Gandomani, T. J., Zulzalil, H., Ghani, A. A. A., Sultan, A. B. M., and Nafchi, M. Z. (2013). Obstacles in Moving to Agile Software Development Methods; at a Glance. Journal of Computer Science, 9 (5): 620-625. DOI: 10.3844/jcssp.2013.620.625.

  • Gartner (2014). Taming the Digital Dragon: The 2014 CIO Agenda. Stamford, CT: Gartner, Inc.

  • Gartner (2014). Top 10 Strategic Predications for 2015 and Beyond: Digital Business is Driving Big Change. Stamford, CT: Gartner, Inc.

  • Gill, M. (2013). The Luxury Retailer's Guide to Agile Commerce. Cambridge, MA: Forrester Research, Inc.

  • Glazer, H., Dalton, J., Anderson, D., Konrad, M., and Shrum, S. (2008). CMMI or Agile: Why Not Embrace Both! Pittsburgh, PA: Carnegie Mellon University.

  • Google (2015). Design Sprint Methods: Playbook for Start Ups and Designers. Mountain View, CA: Google.

  • Gorans, P., and Kruchten, P. (2014). A Guide to Critical Success Factors in Agile Delivery. Washington, DC: IBM Center for The Business of Government.

  • Graffius, S. M. (2016). Agile in 60 Minutes: An Overview for Executives. Los Angeles, CA: Exceptional PPM and PMO Solutions.

  • Graffius, S. M. (2016). Implementing Your Value-Driven Center of Excellence PMO with a Flexible Framework to Support Agile, Traditional, and Hybrid Approaches to Development and Delivery. Los Angeles, CA: Exceptional PPM and PMO Solutions.

  • Gruber, J. (2010). Apple's Constant Iterations. Macworld, 27 (4): 100.

  • Harrington, H. J., Voehl, F., and Voehl, C. F. (2014). Model for Sustainable Change. Newtown Square, PA: Project Management Institute.

  • Harvard Business Review (2015). Agile Practice: The Competitive Advantage for a Digital Age. Boston, MA: Harvard Business Publishing.

  • Hewlett-Packard (2013). Manage Projects Effectively: HP Project and Portfolio Management Center and HP Agile Manager. Palo Alto, CA: Hewlett-Packard Development Company LP.

  • Hinsen, K. (2015). Technical Debt in Computational Science. Computing in Science and Engineering, 17 (6): 103-107. DOI: 10.1109/MCSE.2015.113.

  • Hoda, R., Noble, J., and Marshall, S. (2013). Self-Organizing Roles on Agile Software Development Teams. Software Engineering, 39 (3): 422-444. DOI: 10.1109/TSE.2012.30.

  • IBM (2014). The IBM Agile Information Governance Process. Somers, NY: IBM Corporation.

  • Institute of Practitioners in Advertising (2014). A is for Agility. London, United Kingdom: Institute of Practitioners in Advertising.

  • International Council on Systems Engineering (2004). Systems Engineering Handbook. Seattle, WA: International Council on Systems Engineering.

  • Ismail, U., Qadri, S. and Fahad, M. (2015) Requirement Elicitation for Open Source Software by Using SCRUM and Feature Driven Development. International Journal of Natural and Engineering Sciences, 9 (1): 38-43.

  • Jahr, M. (2014). A Hybrid Approach to Quantitative Software Project Scheduling Within Agile Frameworks. Project Management Journal, 45 (3): 35-45. DOI: 10.1002/pmj.21411.

  • Johnson, J., Boucher, K. D., Connors, K., and Robinson, J. (2001, February/March). Collaboration: Development and Management—Collaborating on Project Success. Software Magazine, 21 (2): Supplement.

  • Kayes, I., Sarker, M., and Chakareski, J. (2016). Product Backlog Rating: A Case Study on Measuring Test Quality in Scrum. Innovations in Systems and Software Engineering, 12 (4): 303-317. DOI: 10.1007/s11334-016-0271-0.

  • Keith, C. (2010). Agile Game Development with Scrum. Boston, MA: Pearson Education, Inc.

  • Kerzner, H. (2013). Project Management: A Systems Approach to Planning, Scheduling, and Controlling—Eleventh Edition. Hoboken, NJ: John Wiley & Sons, Inc.

  • KPMG (2011). Agile in the IT World. Amstelveen, Netherlands: KPMG International.

  • KPMG (2015). Moving Agility to the CIO Agenda: Towards Enterprise-Grade Agile Management. Amstelveen, Netherlands: KPMG International.

  • Larman, C., and Basili, V. R. (2003). Iterative and Incremental Development: A Brief History. Computer, 36 (6): 47-56. DOI: 10.1109/MC.2003.1204375.

  • Larman, C., and Vodde, B. (2010). Practices for Scaling Lean and Agile Development. Upper Saddle River, NJ: Addison-Wesley.

  • Larusdottir, M. K., Cajander, A., and Gulliksen, J. (2014): Informal Feedback Rather Than Performance Measurements — User Centred Evaluation in Scrum Projects. Behaviour and Information Technology, 33 (11): 1118-1135. DOI: 10.1080/0144929X.2013.857430.

  • Lukens, S., and Rogers, S. B. (2006). The Agile CFO: Enabling the Innovation Path to Growth. Somers, NY: IBM Corporation.

  • Malik, S. (2005). Enterprise Dashboards: Design and Best Practices for IT. Hoboken, NJ: John Wiley & Sons, Inc.

  • McConnell, S. (1996). Rapid Development: Taming Wild Software Schedules. Redmond, WA: Microsoft Press.

  • Medinilla, A. (2012). Agile Management: Leadership in an Agile Environment. New York, NY: Springer.

  • Moore, G. A. (2014). Crossing the Chasm, Third Edition: Marketing and Selling Disruptive Products to Mainstream Customers. New York, NY: HarperBusiness Publishers.

  • Morampudi, N. S., and Gaurav, R. (2013). Evaluating Strengths and Weaknesses of Agile Scrum Framework Using Knowledge Management. International Journal of Computer Applications, 65 (23): 1-6. DOI: 10.5120/11221-6058.

  • Northrop Grumman (2013). Health IT: Agile Project Management Office (PMO). Falls Church, VA: Northrop Grumman Corporation.

  • Oracle (2011). Accelerate Product Innovation and Maximize Profitability: Agile Product Lifecycle Management. Redwood Shores, CA: Oracle Corporation.

  • Orr, A. (2014). Maximize the Synergies Between ITIL and DevOps. London, United Kingdom: AXELOS.

  • Penton Media (2016). 15th Annual 50 Top Event Companies. Special Events, 35 (4): 12-14.

  • Performance Institute, The (2013). Program Management for Agile: Retooling Your Approach for Agile Success. Alexandria, VA: The Performance Institute.

  • Perrin, R. (2008). Real World Project Management: Beyond Conventional Wisdom, Best Practices and Project Methodologies. Hoboken, NJ: John Wiley & Sons, Inc.

  • Pikkarainen, M., Haikara, J., Salo, O., Abrahamsson, P., and Still, J. (2008). The Impact of Agile Practices on Communication in Software Development. Empirical Software Engineering, 13 (3): 303-337. DOI: 10.1007/s10664-008-9063-9.

  • Pohlman, W. (2017). IEEE Computer Society/Software Engineering Institute Watts S. Humphrey Software Process Achievement (SPA) Award 2016: Nationwide (CMU/SEI-2017-TR-003). Retrieved from the Software Engineering Institute, Carnegie Mellon University website:

  • Poppendieck, M., and Poppendieck, T. (2003). Lean Software Development: An Agile Toolkit. Upper Salle River, NJ: Addison-Wesley.

  • Pratt, E. (2013). Towards an Agile Authoring Methodology: Learning from the Lean Methodology. San Jose, CA: Adobe Systems Incorporated.

  • Price, L. (2014). People Leadership: From Control to Vision. CIO New Zealand, 17 (4): 6.

  • PricewaterhouseCoopers (2013). Scale Agile Throughout the Enterprise: A PwC Point of View. London, United Kingdom: PricewaterhouseCoopers LLP.

  • PricewaterhouseCoopers (2014). Adopting and Agile Methodology: Requirements-gathering and Delivery. London, United Kingdom: PricewaterhouseCoopers LLP.

  • Project Management Institute (2013). A Guide to the Project Management Body of Knowledge—Fifth Edition. Newtown Square, PA: Project Management Institute.

  • Project Management Institute (2014). Change Readiness: Focusing Change Management Where It Counts. Newtown Square, PA: Project Management Institute.

  • Project Management Solutions (2014). The State of the Project Management Office (PMO): 2014. Glen Mills, PA: Project Management Solutions, Inc.

  • Protiviti (2015). Agile Technology Controls for Startups—a Contradiction in Terms or a Real Opportunity? New York, NY: Protiviti, Inc.

  • Qumer, A., and Henderson-Sellers, B. (2008) An Evaluation of the Degree of Agility in Six Agile Methods and Its Applicability for Method Engineering. Information and Software Technology, 50 (4): 280-295.

  • Ramadan, N., and Megahed, S. (2016). Requirements Engineering in Scrum Framework. International Journal of Computer Applications, 149 (8): 24-29. DOI: 10.5120/ijca2016911530.

  • Rising, L., and Janoff, N. S. (2000). The Scrum Software Development Process for Small Teams. IEEE Software, 17 (4): 26-32. DOI: 10.1109/52.854065.

  • Robinson, P. K., and Hsieh, L. (2016). Reshoring: A Strategic Renewal of Luxury Clothing Supply Chains. Operations Management Research, 9 (3): 89-101. DOI: 10.1007/s12063-016-0116-x.

  • Sampaio, A., Vasconcelos, A., and Sampaio, P. R. F. (2004). Assessing Agile Methods: An Empirical Study. Journal of the Brazilian Computer Society, 10 (2): 21-48. DOI: 10.1007/BF03192357.

  • Schneiderman, M. (2013). Digital Dashboards: Best Practices and Lessons Learned. Princeton, NJ: Information Age Associates.

  • Schwaber, K. (2006). The Enterprise and SCRUM: Best Practices. Redmond, WA: Microsoft Press.

  • Scrum Alliance (2013). The State of Scrum: Benchmarks and Guidelines. Newtown Square, PA:

  • Sharif, B., Khan, S. A., and Bhatti, M. W. (2012). Measuring the Impact of Changing Requirements on Software Project Cost: An Empirical Investigation. International Journal of Computer Science Issues, 9 (3): 170-174.

  • Solinski, A., and Petersen, K. (2016). Prioritizing Agile Benefits and Limitations in Relation to Practice Usage. Software Quality Journal, 24 (2): 447-482. DOI: 10.1007/s11219-014-9253-3.

  • Strålin, T., Gnanasambandam, C., Andén, P., Comella-Dorda, S., and Burkacky, O. (2016). Software Development Handbook: Transforming for the Digital Age. Stockholm, Sweden: McKinsey & Company, Inc.

  • Sutherland, J., Harrison, N., and Riddle, J. (2014). Teams that Finish Early Accelerate Faster: A Pattern Language for High Performing Scrum Teams. Presented at 2014 47th Hawaii International Conference on System Science. System Sciences: 4722-4728. DOI: 10.1109/HICSS.2014.580.

  • Sutherland, R. (2011). Rory Sutherland: The Wiki Man. London, United Kingdom: It's Nice That, and Ogilvy Group Ltd.

  • Takeuchi, H., and Nonaka, I. (1986). The New New Product Development Game. Harvard Business Review, 64 (1): 137-146.

  • Technology Business Management Council (2014). DirecTV: Fail Fast, Innovate Often. Bellevue, WA: Technology Business Management Council.

  • Thompson, K. (2011). Agile for Executives. Foster City, CA: cPrime, Inc.

  • Vatier, C. (2015). Incubator or Respirator? Why You Need to Change the Way You Innovate. Now. Dublin, Ireland: Accenture.

  • VersionOne (2016). 10th Annual State of Agile Survey. Atlanta, GA: VersionOne, Inc.

  • Vijay, D., and Ganapathy, G. (2014). Guidelines to Minimize the Cost of Software Quality in Agile Scrum Process. International Journal of Software Engineering and Applications, 5 (3). DOI: 10.5121/ijsea.2014.5305.

  • Wake, B. (2003). INVEST in Good Stories, and SMART Tasks. Retrieved at

  • Wale-Kolade, A., and Nielsen, P. A. (2016). Apathy towards the Integration of Usability Work: A Case of System Justification. Interacting with Computers, 28 (4): 437-450. DOI: 10.1093/iwc/iwv016.

  • Weill, P., and Ross, J. W. (2004). IT Governance on One Page. Cambridge, MA: Massachusetts Institute of Technology.

  • West, D. (2011). Water-Scrum-Fall is the Reality of Agile for Most Organizations Today. Cambridge, MA: Forrester Research, Inc.

  • Whitaker, S. (2014). The Benefits of Tailoring: Making a Project Management Methodology Fit. Newtown Square, PA: Project Management Institute, Inc.

All versions This version
Views 2424
Downloads 22
Data volume 546.2 kB546.2 kB
Unique views 1717
Unique downloads 22


Cite as