article thumbnail

Scrum: A Brief History of a Long-Lived Hype

Scrum.org

In the end, the sources I used for describing the evolutions of the definition of Scrum are: The paper “SCRUM Software Development Process” by Ken Schwaber (1995, 1996). The Scrum Guide” by Ken Schwaber and Jeff Sutherland (2011, 2013, 2016, 2017). Phases, meetings, time-boxes, events. Controls, deliverables, artifacts.

2010 232
article thumbnail

5 Ways Project Management Will Evolve

LiquidPlanner

In my current role, we’re moving from a manual process of pulling out key data points to then share via a monthly report to smart dashboards that dynamically capture and reflect key information in our project management tool that includes dashboards to support reporting. This is a trend I can’t wait to jump on. Talent challenges.

Insiders

Sign Up for our Newsletter

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

article thumbnail

How I ended up becoming a (Professional) Scrum trainer

Gunther Verheyen

In April 2010, at an event of the Agile Consortium Belgium in Brussels, I asked Jeff Sutherland about this new organization founded by his former companion. I had been closely following up on the emergence and growth of Scrum.org as it coincided with a personal process of professional recovery. It intrigued me.

SCRUM 103
article thumbnail

Scrum Methodology: Roles, Events & Artifacts

ProjectManager.com

Scrum is a framework that consists of values, roles , events and artifacts. Individuals and interactions over processes and tools: Processes and tools are important in software development, but individuals and how they interact with those processes and tools are more important. Scrum Events. Learn More!

SCRUM 338
article thumbnail

A Beginner’s Guide to Scrum Ceremonies

ProjectManager.com

People report honestly on what they did, what they plan on doing and how they might be getting blocked in the process, and this is all done in front of their peers. Because scrum is part of an agile process, it is all about change, which includes getting feedback and quickly acting on it. They’re started to be called events.

SCRUM 203
article thumbnail

Disciplined Agile & SAFe

International Institute for Learning

DA was developed in 2011 by Scott Ambler and Mark Lines and is based on Scott’s work at Rational Software and IBM. Synchronization is achieved through a quarterly 2-day, “big-room planning” event. DA defines “process blades” to describe common enterprise capabilities. They emerged about a decade after the Agile Manifesto.

Agile 59
article thumbnail

Scrum: A Brief History of a Long-Lived Hype

Gunther Verheyen

For every source I have described the same three topics to show what Scrum consisted of at the time (regardless the different terms used), what the ‘definition’ of Scrum was at the time: Roles, responsibilities, accountabilities Controls, deliverables, artifacts Phases, meetings, time-boxes, events.

2010 141