An Introduction to Scrum: Roles, Ceremonies, and Processes for Agile Teams
Scrum is perfect for small, remote teams working on complex software products. But its rapid rise in popularity has meant that Agile Project Management with Scrum is often not fully understood, even by those who have been exposed to it.
In this series, I hope to clear up some of the confusion around terminology, while providing a clear framework on how we implement Scrum across the majority of the projects we deliver at Scalable Path.
Table Of Contents
Agile vs Waterfall
By deciding to build your software with Scrum, you are also embracing the Agile methodology. Agile was a response to a problem: software projects were coming in over deadline and over budget.
Probably the most famous cautionary tales come to us via Microsoft: Windows 95 was late. Windows 2000 was late. Windows Vista was seriously late. All of these releases were built using a traditional project management method called Waterfall.
- Planning
- Design
- Development
- Testing
- Delivery
The Waterfall method has a long, distinguished history, but was found lacking for software development in the Internet age. An age where products become dated quickly and are often in a permanent state of evolution.
Today, Microsoft has fully embraced Agile. This is because Agile turned previous approaches on their head, well on their side at least.
