Driving Continuous Improvement
Find a vast array of advanced scrum topics and patterns that can increase your Team’s Velocity. Online courses and classes for Scrum Masters, Scrum Product Owners, and those team members seeking continuous improvement. If you’re not a member, visit our pricing and plans page for more detail.
Patterns: Finish Early, Accelerate Faster
Finish Early, Accelerate Faster (FEAF) is a Scrum pattern language composed of a number of Scrum Patterns used together. FEAF is an incredibly powerful pattern language because it will help new Teams establish good practices and take experienced Teams Hyper-Productive; defined as a Velocity 400% higher than a Teams’ initial Velocity.
Scrum Retrospectives
One of the core principles in Scrum is the idea of continuous improvement. Each Sprint the Team engages in an inspect-and-adapt cycle during the Retrospective meeting. Beyond that though, the Scrum Guide doesn’t offer much insight into how to run a successful Retrospective and how to use the meeting to improve production, quality, and velocity.
All Continuous Improvement Topics
Toyota Chairman Fujio Cho: Why He Matters
Business 2.0, 1 Jul 2006 Why He Matters: High oil prices? Toyota says, Bring it on. In May, as the average cost of a gallon of gas approached $3, Toyota reported a 17 percent sales increase over the year before, even as General Motors and Ford saw declines of 16 and 2...
InfoQ and the Roots of Scrum
The JAOO Conference is coming up next week in Denmark. This is one of the leading annual software developer conferences and highly recommended. Last year, I presented at the JAOO conference on the Roots of Scrum. It was a great conference with about 900 Java and .NET...
SirsiDynix Scrum Paper: International Conference on Complex Systems
In response to questions about hyperproductive Scrum teams, please take a look at the SirsiDynix project, the most productive large Java project ever documented. A 56 member distributed/outsourced team was split between Provo, Utah; Denver, Colorado; Waterloo, Canada;...
Scrum Tuning: Program Management with Scrum – Boston
Scrum Tuning: Program Management with Scrum 1-2 Nov 2006 Boston Sign up using buttons on left side of page ... Take your ScrumMaster certification or knowledge of basic Scrum, Agile and lean practices to the next level! Get Agile at Patientkeeper, one of the most...
All-At-Once Scrum: The Agile Enterprise
At the Agile 2005 conference in Denver, I presented a research paper on a multi-team, multi-product Scrum which has a daily Scrum-of-Scrums meetings and a weekly MetaScrum where all Sprints are started, stopped, or changed by a broad base of company stakeholders. Thus...
John Scumniotales New Blog: Agile Project Development
In 1993, Easel Corporation acquired a German Smalltalk compiler company and hired me to lead a team to produce Object Studio for Smalltalk. We were a Microsoft partner and they must have liked our name as they later created Visual Studio. I essentially had a position...
Distributed Scrum: Agile Project Management with Outsourced Development Teams
Recently, I had to complete a research paper on distributed programming for the Agile 2006 Conference in a two day weekend. Russian XP expert and project leader, Anton Viktorov, flew into Boston from St. Petersburg to help write up the SirsiDynix project. Over...
No Silver Bullet: Essence and Accidents of Software Engineering
Fred Brooks comments: Much of present-day software-acquisition procedure rests upon the assumption that one can specify a satisfactory system in advance, get bids for its construction, have it built, and install it. I think this assumption is fundamentally wrong, and...
Microsoft Vista: Scrum or Not-Scrum
Peter Krantz rants on Scrum, Lies, and Red Tape at the Microsoft Vista project (see below). He's in Stockholm and I'm on a SAS flight over Greenland returning from two weeks in Sweden and Denmark doing several ScrumMaster Certification Classes. While Microsoft adopted...
Why the Three Questions in the Daily Scrum Meeting?
In 2017, Ken Schwaber and I made the three questions in the Daily Scrum optional because we saw too many "zombie" teams that were giving lip service to the questions - not collaborating, not replanning, not swarming, and not removing impediments. Also, we saw backlog...