In our last whitepaper (Rethinking BPMN (Part 1): What is a GOOD Process Model), we…
The everything you need to know guide!
Scrum differs from traditional “waterfall” approaches to project management in many ways, but is based on sound project-management principles. Our article on Scrum as Project Management dives deeper into the similarities and differences between Scrum and traditional project management methodologies.
The first two topics covered in this article are the basic overviews of Agile Development and Scrum. Agile Development is based on the idea that the best way to meet customer needs is through the collaboration of a committed group of people, who focus on achieving results quickly, with as little overhead as possible. A key element of this is that we must trust people and their ability to collaborate, more than we trust any particular process.
In regards to Scrum, Scrum is the most widely used framework for agile development. Scrum is most often used to manage complex software and product development, using iterative and incremental practices. Scrum significantly increases productivity and reduces time to benefits relative to classic “waterfall” processes. Scrum processes enable organizations to adjust smoothly to rapidly-changing requirements, and produce a product that meets evolving business goals. As shown in the article, the agile Scrum process benefits the organization in various different ways, and results in scrum projects achieving higher customer satisfaction rates.
Now that we have gone over the introduction, the majority of the article takes a deeper look into Scrum. This includes how to write requirements in Scrum, the three Scrum roles, Scrum time boxes, and the three Scrum artifacts. Lastly, this article goes over the benefits of Scrum, the five different types of Scrum certifications, how you can become Scrum certified, and why you should become certified.
Read more to see exactly how Scrum can benefit you!
Some of the images used were designed by freepik.com