Find resources
Resource search filters
Blog Post
Every year, organizations spend 4-10% of their revenues on their IT organizations. Value is expected in return for these expenditures.
Here, value is defined as the financial benefit that an organization receives for expenditures. When measured, value can encompass an entire organization, or be c...
4.2 from 5 ratings
Case Study
For reasons of competitiveness the delivery of IT services of Amir Arooni's department (CIO of the Solution Delivery Center for Channels at ING NL) needed fundamental improvements. Amir Arooni, Gunther Verheyen take a look at how this was achieved.
0 from 0 ratings
Whitepaper
Professional Scrum Trainer Peter Gfader is often asked several question including: How often do you release your product to your end users? How often do your end users see and use your product? Do you release in sync with your Sprint length, after the Sprint Review? Is the Sprint Review meeting the ...
5 from 2 ratings
Whitepaper
How can my team deliver value and innovation in 24 hours without intervention from management? A "FedEx Day" can be used to show management that just a few people can deliver innovative, working products and software in only 24 hours, and how intrinsic motivators are the key to unlocking our own inn...
0 from 0 ratings
Whitepaper
Learn more from Professional Scrum Trainer Gunther Verheyen about the distinct views and similiarities between Lean and Agile. Included is the Scrum perspective to Agile to demonstrate how the tangible, yet open framework of Scrum aligns and blends the underlying thinking of Agile and Lean.
5 from 1 rating
Whitepaper
Increasing develpoment productivity is a hot topic. This paper by Professional Scrum Trainer Rob Maher focuses on increasing team productivity and discusses how changing a project staffing model can increase the productivity of project teams.
0 from 0 ratings
Publication
One of the most controversial updates to the 2011 Scrum Guide has been the removal of the term “commit” in favor of “forecast” in regards to the work selected for a Sprint. We used to say that the Development Team commits to which Product Backlog Items it will deliver by the end of the Sprint. Scrum...
4.6 from 42 ratings
Publication
Any Product Manager that has successfully delivered a product to a customer knows how incredibly important Release Planning is. Despite its importance, the 2011 Scrum Guide, published in July by Ken Schwaber and Jeff Sutherland, removes any discussion about Release Planning and the related Release B...
4.2 from 15 ratings
Blog
The chicken and pig lore of Scrum is no longer a part of the Scrum Guide. Professional Scrum Trainer Steve Porter discusses the signifigance of what some may assume to be a relatively innocuous change.
3.1 from 8 ratings
Publication
In the past, the Scrum Guide consistently used the word "priority" for the Product Backlog or noted that the Product Backlog was “prioritized.” While the Product Backlog must be ordered, ordering by priority is only one many techniques — and rarely the best one at that.
4.6 from 27 ratings
Publication
The 2011 Scrum Guide, published earlier this month by Ken Schwaber and Jeff Sutherland, makes some bold changes regarding the definition and structure of a Sprint Backlog. Professional Scrum Trainer David Starr explains these changes with help from Professional Scrum Trainer Ryan Cromwell.
5 from 1 rating