Transforming Your Software Development Process with Agile Scrum Methodology
Agile/Scrum has been around in Da Nang city for about 15 years. I would love to take this chance to write some notes about this concept.
By definition: Scrum is an agile project management framework that helps teams structure and manage their work through a set of values, principles, and practices. By definition, Scrum is a lightweight framework that helps people, teams and organizations generate value through adaptive solutions for complex problems.
A Scrum Master to foster an environment where:
- A Product Owner orders the work for a complex problem into a Product Backlog.
- The Scrum Team turns a selection of the work into an Increment of value during a Sprint.
- The Scrum Team and its stakeholders inspect the results and adjust for the next Sprint.
Scrum is founded on empiricism and lean thinking.
Then, here it comes, the mighty PDCA.
Plan-Do-Check-Act (also known as “PDCA”) is a cyclic process that was conceptualized by Walter Shewhart and widely promoted by Edward Deming – two founders of most of the quality philosophies that are followed today. This concept is a cycle for bringing about a change which, when implemented and repeated, would yield repeated improvements in any process.
PDCA cycle should be used in following cases:
- When opting for continuous improvement.
- When initiating a new improvement project.
- When making a new or modified design of a process, product or service.
- When defining a repetitive work process.
- When preparing data collection and analysis so as to verify and prioritize problems or root causes.
- When applying any change.