Overview: Agile methodologies promote a project-management process that encourages frequent inspection and adaptation, and a leadership philosophy using teamwork, self-organization and accountability. Implementation of Scrum across industry runs the gamut from organizations that use all of the practices to organizations that only use a few of them. This means that just declaring, "We use Scrum," or "We are Agile," does not guarantee any specific level of Agile usage or quality.
This is a significant concern in a critical system environment (IT and safety-critical applications). However, Scrum can be used to develop critical software systems, but additional engineering and management practices need to be considered to ensure that robust products are developed and risk and inefficiencies are minimized. In this presentation we will explain how Scrum can be used in any organization and additions that can clarify customer needs, manage project risks and reduce inefficiencies while maintaining the benefits of Scrum.
Areas Covered in the Session:
Over-zealous use of the agile manifesto
Having a good enough backlog - quality and review
Do you have end-user involvement?
No release plan, only scoping for one iteration at a time
Embracing change - when is too much?
Ensuring that everything that needs to be done (e.g., design and test) can be done in an iteration
Managing surprises, managing risk
Refactoring and code ownership isn't free
Self-organizing teams - can they self-organize?
Scrum masters don't like the things they have to do
Be careful with the "Pigs and Chickens" terms
What is design and where does it fit?
Who Will Benefit:
Senior Managers wanting to use Scrum and manage quality and risk
Project or program managers leading teams using Scrum
Scrum Masters / Coaches
Internal company Project Management Office (PMO) leaders and members
Internal process improvement coaches tasked with improving the organization's cost, schedule, quality performance and want to implement Scrum.