Scrum: Creating Great Products and Critical Systems – What to Worry About, What’s Missing, and How to Fix It

• This presentation was created for a conference series or symposium and does not necessarily reflect the positions and views of the Software Engineering Institute.

• Abstract

  This TSP Symposium 2014 presentation explains that the interest in Agile/Scrum software development practices continues to grow as companies seek more efficient methods of developing software while meeting market demands for delivery. Scrum is a software development methodology based on Agile principles. Agile methodologies promote a project management process that encourages frequent inspection and adaptation; a leadership philosophy using teamwork, self-organization, and accountability; and strong customer involvement.

  However, Scrum/Agile implementations don't always go as planned, and without some due diligence, chaos is easy. In this session, Neil enumerates the problems to look out for and provides example corrective actions:
  

  • Scrum/Agile overview
  • What to use from the Agile Manifesto
  • Definition of Scrum
  • Scrum risks to look out for and what to do about them:
  • Mistaking speed for progress
    
  • One-liner requirements (the devil in the details)
  • Missing architecture/design
  • Missing final system test/validation
  • Missing configuration management
  • Missing risk management
  • Missing process assurance (known as ScrumBut)
• Slides