Skip to main content

How do I do #Stoos in my company?

Monday, Steve Denning and I held our Monthly Mashup webinar dedicated to the question, "What is Stoos?" If you haven't followed the linkedin discussion, I urge you to check it out! In any case, one of our participants, Gary from Chicago asked:
I am in the process of forming a new company which will operate in a niche within the chemicals industry.   I am not looking to change my organization, I am looking to start my organization using Stoos, Agile and Radical Management from the outset.  It would be helpful to know who within the global Stoos network might be available to consult regarding my startup keeping my developing organization on the path of being customer focused with empowered employees.
Great question! A couple of answers came back:
  • Several of the panelists are in that business (surprise!). For example, Steve & I teach a course on Radical Management. I also teach Scrum and lead Temenos visioning retreats to enable your your leadership team to create a compelling shared vision. In my own entrepreneurial work, I have gotten quite excited about the Lean Startup approach and am happy to share my excitement! 
  • Ask on the Stoos linkedin group or in the nearest Stoos Satellite - In your case, I would suggest starting a Stoos satellite; AFAIK the Denver Satellite is most active in the USA.
  • A number of the compatible frameworks have active user communities, coaches and trainers: Scrum, Kanban and Lean Startup come to mind, and these could be good places to start.
On reflecting, I'd also like to encourage you to take your destiny in to your own hands! The Agile Manifesto shows you how!

Apply the Agile Manifesto to your Company or Context

Remember the Agile Manifesto? "We are uncovering better ways of developing software..." What follows are 4 value statements and 12 principles that are surprisingly universal. Joe Justice, CEO of WIKISPEED, suggests adapting the Agile Manifesto to your situation and using the values and principles to guide your actions.

How can you apply the Agile Manifesto to your situation? Replace "develop software" with whatever you do or your company does. If you are an interior designer, you might say "We are uncovering better ways of designing homes..."

Now, go a step further! Look at your work from the perspective of the beneficiaries of your work. In the case of an interior designer: We are uncovering better ways to create living spaces for individuals and families. Now you have your own personal "Agile Manifesto!"

Once you have your own personal manifesto, you can go through the values and principles and ask yourself, how does this apply to my quest for better ways of working or creating value for my constituents? For each value and principle, identify one or two things that you can start doing differently tomorrow to apply that principle. Voilà! You're doing Stoos!

Maybe one or two of the principles don't apply to you, and that's OK. Maybe there is another principle that you have discovered, which for some reason is not in the software developer's Agile Manifesto. Is it compatible with the four values? Then that principle is OK too! You are creating your own manifesto!

Good luck! And I would love to hear back from people who go through this exercise and apply the results to their business!


Popular posts from this blog

Sample Definition of Done

Why does Scrum have a Definition of Done? Simple, everyone involved in the project needs to know and understand what Done means. Furthermore, Done should be really done, as in, 'there is nothing stopping us from earning value with this function, except maybe the go-ahead from the Product Owner. Consider the alternative:
Project Manager: Is this function done?
Developer: Yes
Project Manager: So we can ship it?
Developer: Well, No. It needs to be tested, and I need to write some documentation, but the code works, really. I tested it... (pause) ...on my machine. What's wrong with this exchange? To the developer and to the project manager, "done" means something rather different. To the developer in this case, done means: "I don't have to work on this piece of code any more (unless the tester tells me something is wrong)." The project leader is looking for a statement that the code is ready to ship.

At its most basic level, a definition of Done creates a sh…

Explaining Story Points to Management

During the February Scrum Breakfast in Zurich, the question arised, "How do I explain Story Points to Management?" A good question, and in all honesty, developers can be an even more critical audience than managers.

Traditional estimates attempt to answer the question, "how long will it take to develop X?" I could ask you a similar question, "How long does it take to get the nearest train station?

The answer, measured in time, depends on two things, the distance and the speed. Depending on whether I plan to go by car, by foot, by bicycle or (my personal favorite for short distances) trottinette, the answer can vary dramatically. So it is with software development. The productivity of a developer can vary dramatically, both as a function of innate ability and whether the task at hand plays to his strong points, so the time to produce a piece of software can vary dramatically. But the complexity of the problem doesn't depend on the person solving it, just …

Money for Nothing, Changes for Free

“Money for Nothing, Changes for Free” encourages both customers and suppliers to focus on value.

A key advantage of Scrum projects is that at least once per sprint you have something that could be shipped and no work in progress. You can change direction every sprint, and you can reevaluate whether the project is a good investment or if your money could be better spent elsewhere. Abrupt cancellation is risky for the supplier.

While the concept of an early-exit penalty is not new, Jeff Sutherland gave it a unique allure with his allusion to the Dire Straits hit.
Desired Benefit Incentivize both customers and suppliers to focus on functionality that provides genuine value.
Structure This works with Agile software projects because there is little or no work in progress. After each Sprint, functionality is either complete or not started. Work is basically on a Time and Materials basis with a cost target, often with the intention that the project should not use up the entire project budge…