Scrum @ 21

Scrum at 21 – A Look Back Through the Eyes of Ken Schwaber, its co-creator I’m told that it has been 21 years since Scrum became public when Jeff Sutherland and I presented it at an Object-Oriented Programming, Systems, Languages & Applications (OOPSLA) workshop in Austin, TX in October of 1995. Time sure does fly. Things … Continue reading →

Scrum Development Kit

On Tuesday, Jeff Sutherland and I will be celebrating the twentieth anniversary of Scrum’s first public appearance. Those twenty years were my warm up for the next twenty, when I will focus on improving our professionalism. Specifically, I will be done when all Scrum teams deliver “done”, potentially shippable, in operations and usable, increments of … Continue reading →

Scaling, the Nexus, and Scrumbling

I will be conducting a Nexus workshop in Boston on November 17-18, with Richard Hundhausen and Rob Maher, based on the Nexus Guide. Of interest to many, SDK, API architectures, and remediation Scrumbles, and DevOps. Many Scrum teams deliver a “done”, potentially shippable increment at the end of each Sprint. As the number of teams rises, as the project scales, … Continue reading →

Scale Scrum Projects Better – August 25-26 Irvine CA

Workshop information Free – for desperate people without budget (but not for consultants) who are willing to provide work in kind during  the workshop. $300 – for people figuring out how to scale their project or in the middle of a scaled project that is overwhelmed with dependencies and “done” is unknown – but have … Continue reading →

Can Software Developers Meet the Need?

Marc Andreessen provided some insights into the importance of software and the software profession’s ability to meet the need at “Why Software Is Eating The World” , http://goo.gl/ob2Cvx Scrum facilitates control through frequent, regular inspection and adaptation of transparent software functionality. Transparency means the software is ready. It can either be immediately deployed or built … Continue reading →

Scrum and Continuous Improvement

Organizations usually don’t adopt Scrum because they like its name. Instead, they have heard that software development is better if they use Scrum – quicker, cheaper, higher quality, more satisfied customers and employees. Sometimes things are so bad in software development that they try Scrum just because it wasn’t what they were doing before. However, … Continue reading →