Enterprise Scrum is a business-oriented,scalable, general empirical management and execution framework. It can help manage with more agility any business process including Company Management, Strategy, Marketing, Sales, Product Development, Software Development, Basic Research, Compliance Management, Business Process Redesign, Entrepeneurship and Start-Ups, etc.

Thought Leadership

We have experience in using Enterprise Scrum to agilize any business process.

Some people want to matrix their people into multiple projects, or having the same team do multiple projects simultaneously. Although Scrum doesn’t explicitly say that these are “bad ideas”, they are. They involve something that in Lean Development is called “task switching”, and it is part of a bigger Lean Principle called “Eliminate Waste”. Although, there is not a formal historical connection from Scrum to Lean, we have to remember that many of the companies that were doing product development analyzed by Nonaka and Takeuchi in their seminal paper “The NEW new product development game” (if you don’t have a copy of the paper get it here: http://www.enterprisescrum.com/publications/), like Honda, Canon, Fujitsu/Xerox, Panasonic had employed by the late 1970s and early 1980s, many consultants from Toyota that brought the Lean ideas to with them and apply them, not only to Production systems (as in Toyota Production Systems), but to Development. In fact, that difference about what Production and Development, is what determines the scope of applicability for Scrum: Scrum is a portable empirical process execution framework. (More of this stuff at http://www.enterprisescrum.com/enterprise-scrum ). But this is a fact: you can reverse Scrum and see many Lean Principles at work. For this reason, I say that Scrum is Lean (in the American Value and Effectiveness way). Of course, Scrum is really Agile, as are other Agile methods, because it not only cares about Delivering Value (through efficiency and avoiding waste), but by Doing the Right Thing first (prioritizing the Product Backlog), but in addition it also has Customer Focus, Embracing Change, and Focus on Individuals and Interactions.

If you do Scrum you must read the paper above “The NEW new product development game” by Nonaka and Takeuchi, HBR, 1996. I have read it no less than 10 times, and continue to search for inspiration on it. It is required reading for everyone doing Scrum. Find it here: http://www.enterprisescrum.com/publications/

We avoid waste in Scrum because we want to maximize the efficiency ratio of our Scrum implementation. We define the efficiency ratio as:

Er = Sum of all Value Adding tasks/Sum of ALL tasks

When there is little waste is closer to 1. When there is a lot of waste (like in a typical CMM implementation), it is closer to zero. Keep this mind when tweaking Scrum (or anything else really).

Having said that, there are a lot of other ways to avoid waste in Scrum:

• Partially Done Work – we try to move from Sprint to Sprint without it!

• Extra Processes – we avoid thick useless documents, bureaucracy and approvals for “talking to the right people”, for example

•

• Task Switching – we avoid working on “too many things” during a Sprint – 1) multiple-project by the same team, 2) individuals matrixed in multiple projects, 3) very many tasks by an individual within a project

Note to the managers in this list: Matrix the least amount of people – matrix destroys efficiency because it involves “task switching”

• Waiting – we avoid waiting -- that’s why in Scrum we get feedback daily and have a ScrumMaster that resolves issues to minimize waiting time through the Daily Scrums

• Motion – we avoid “hand-offs”, phases and assembly lines – instead we socialize knowledge to avoid moving things from one specialist to another one whenever we can

When this ratio is large, it can ruin your Sprint productivity by using too many cycles making corrections for previous Sprints. That is why in Scrum we need to integrate and test everyday and we prefer continuous integration and layered automated testing. A good measure, a fitness test of your software if you will, but certainly not the only “goodness measure”, is the percentage of completed acceptance tests for all PBIs and User Stories defined as:

Whereas this fraction is grand, it can bankrupt your Scurry productivity by using furthermore numerous times making punishments for previous Rushs. That is reason in Scrum we demand to blend further audition ordinary further we pick continuous integration besides layered automated testing.

The voluntary association is actually a corporation consisting regarding volunteers. Such organizations may be able to operate without having legal formalities, counting on jurisdiction, similar to informal clubs.

A scrum (short for scrummage) is a method of restarting play in rugby football. Depending on whether it is in rugby union or rugby league, the scrum is utilised either after an accidental infringement.

A key difference between the two sports is that in rugby union both sets of forwards try to push the opposition backwards whilst competing for the ball and thus the team that did not throw the ball into the scrum have some chance of winning the possession.