Skip to main content

A Month of Thoughts for the Day

One month ago, I started tweeting regularly a Thought for the Day on Scrum and Radical Management. It's hard to find old tweets, so here is a compendium of my #RMTftD's since I started.

Do you like these? Then follow me at @peterstev and be sure to retweet the thoughts that you think are worth repeating...

8.6 To be smart, first play nice. "The Wisdom of the Dog" http://bo.st/kgbrwm
9.6 Better to have 80% of your features 100% done then 100% of your features 80% done.
10.6 Radical Mgmt = Scrum + (Delight the Customer, Leadership Storytelling) - (Product Owner, ScrumMaster, Software Baggage).

12.6 Tomorrow is a bank holiday. It's OK to let the battery on your smart phone run down.
13.6 Today is a holiday. Leave your Smartphone off. Who are those people at the kitchen table? Enjoy the day with them!
14.6 Do you follow your own advice?
15.6 I know having less work in progress is the key to better response times. How do I clear my todo-list?
16.6 What was your best work experience? Everyone motivated & focused, great results & happy customers? Are you living that now?
17.6 Radical mgmt is how decent people normally think, speak & act before organizations corrupt them. Feels like coming home.

19.6 Secret of apple stores' success? Don't try to sell! WTF? APPLE is an approach to customer service. http://onforb.es/mQC4hf

20.6 Discipline and loyalty can coexist with motivated, empowered staff. http://onforb.es/mQC4hf
21.6 Change Leaders: Which is more promising? One 70% solution everyone supports or several 100% solutions everybody fights?
22.6 Reframing the problem can lead to deep insight on how to achieve customer delight: http://bit.ly/lhk00e
23.6 Once your common ground 70% solution is clear, you realize you have a 95% solution. The rest no longer bothers you.
24.6 A creative "Yes and" expands and builds on each other's ideas. 'Yes, but..." traps you in debate.

27.6 Continuous Innovation & improvement are key to corporate growth. Scrum & Kanban are proven approaches to achieving them.
28.6 Each sprint improves product and team. The Producet Owner has the vision for the product. Who has the vision for the team?
29.6 Agile is about Quality. What is the essence of your management philiosophy?
30.6 The purpose of an organization is to delight the customer! How would you feel, if you were a customer of your own company?

3.7 This week - thoughts from Fred Reichheld - 'The Ultimate Question: Driving Good Profits and True Growth'
4.7 Dominant players have economic advantage. If this is not used to make customers :-), position and advantage will not last
5.7 When a customer feels mislead, mistreated ignored or coerced, then profits from that customer are bad. http://bit.ly/ggZbv1
6.7 Bad Profits are about extracting value from the customers, not creating value.
7.7 Bad profits work their damage by creating detractors - people who will avoid your product if they can and warn others away
8.7 When did you last recommend a product or company? When did you last warn a friend away from a product or company? Why?

And here are the most recent Thoughts for the Day on Scrum and Radical Management. To stay up to date, follow @peterstev

Comments

Popular posts from this blog

Scaling Scrum: SAFe, DAD, or LeSS?

Participants in last week's Scrum MasterClass wanted to evaluate approaches to scaling Scrum and Agile for their large enterprise. So I set out to review the available frameworks. Which one is best for your situation?

Recently a number of approaches have started gaining attention, including the Scaled Agile Framework ("SAFe") by Dean Leffingwell, Disciplined Agile Development (DAD), by Scott Ambler, and Large Scale Scrum (LeSS), by Craig Larman and Bas Vodde. (Follow the links for white papers or overviews of each approach).

How to compare these approaches? My starting point is Scrum in the team. Scrum has proven very effective at helping teams perform, even though it does not directly address the issues surrounding larger organizations and teams. An approach to scaling Scrum should not be inconsistent with Scrum itself.

Scrum implements a small number of principles and constraints: Inspect and Adapt. An interdisciplinary Team solves the problem. Deliver something of va…

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…

10 Warning Signs, that your team is not self-organizing

How do you know that self-organization is working? The Bern Chapter of Scrum Breakfast Club looked into this questions, and identified the following warning signs (which I have taken the liberty of translating).

The team reports to the Scrum Master at the Daily ScrumPeople wait for instructions from the Scrum MasterTeam members don't hold each other responsible [for their commitments]The same impediment comes up twice"That's the way it is" => resignation"I" instead of "We"Flip charts are lonelyCulture of conflict-avoidanceDecisions processes are unclear, nor are they discussedPersonal goals are more important than team goals
To this list I would add my a couple of my favorites:
you don't see a triangle on the task board (not working according prioritization of stories)after the daily Scrum, people return directly to their desks (no collaboration)there are a least as many stories in progress as team members (no pairing)
P.S. You can join the …