An internally focused exploration of an idea is different from an externally focused one. In my experience, noticeable differences have been related to market, revenue, customer etc. F.ex, relatively small potential improvements in work within main value streams could clearly dwarf size of investments, or have been considered already.
Anyway, here’s a kind of intranpreneur canvas that’s been useful for me a few times lately when thinking about building new software.
At LKNA13 in Chicago this year I listened to @JoshuaKerievsky talk about #techsafety.
He made me think about quite a few aspects of safety and injuries for a programmer. Here’s a few quotes and elements:
safety on team (ref own dev competence)
«working with CVS is hurting my soul.»
safe from uncertain work situation
safe to deploy – bugs, crash
safe from pressure – politics, policies
Emotional Injuries: Schedule Stress, Lost Respect, Fear of Failure, Torn Trust, etc
What’s interesting is his claim that having #techsafety as a primary value would be profitable and produce outstanding results. I think I buy into that, even if he hasn’t had time to prove it yet with his own company, @IndustrialLogic.
Essentially, a Lean Coffee is a group of people working together to learn … in an informal setting. It’s like a mini-unconference where the participants decide on the schedule.
Step 1: Everybody writes down topics they’d like to discuss on stickies ….
Step 2: Each topic is briefly described …
Step 3: … votes …
Step 4: … stickies with the most votes at the top
Step 5: Each of these stickies are discussed
Step 6: If enough time … do another stickie
When you set an agenda, you control the conversation. …. When you control the agenda, you control the lessons learned. Since we enter a meeting with only our assumptions to guide us, agendas follow our assumptions. Our assumptions are based on what we already know. But what about the things we don’t know? Quite often, it’s the conversations we don’t plan on that give us the most insight. Why not instead run our meetings to learn or to discover?
Conventional wisdom suggests that businesses hold far too many meetings attendees deem a waste of their time. …. To combat this, some call for meetings with rigid agendas.
the discussion of a stated topic is a conversation. In fact, the entire reason we are calling the meeting is to have a conversation. ….
If we want to learn from our meetings, we need to allow the conversation to be set by the very professionals we invited to the meeting in the first place. …. Allowing the group to have a say in setting the agenda gives them buy-in for the importance of the topics.
as the person who called the meeting, you can now direct the overall topic and even seed a few of the initial sticky notes. You can even set a few “must discuss” stickies at the top of the board and prioritize them the highest.
either privately or f.ex a right-most column on the board
per topic or sharing takeaways in general at the end of the lean coffee
David Joyce and Dr Peter Middleton have studied the application of (what I call) Lean-Kanban in BBC.
From the abstract:
The evidence shows that over the 12-month period, lead time to deliver software improved by 37%, consistency of delivery rose by 47%, and defects reported by customers fell 24%.
The significance of this work is showing that the use of lean methods including visual management, team-based problem solving, smaller batch sizes, and statistical process control can improve software development.
The faster delivery with a focus on creating the highest value to the customer also reduced both technical and market risks.
I’ve been listening to a talk by Don Reinertsen, and one of his points, although not the main point, is about variability: if you could reduce variability in the workflow by 10%, or you could reduce capacity utilization by 10%, by far you would prefer to reduce capacity utilization. That’s where the economic payoff is.
The reason is that increased capacity utilization increases queue size and lead time exponentially. In other words, if you try to keep all your resources busy all the time, everything takes forever to finish. This goes for both manufacturing and development. Variability in workflow, however, is bad in manufacturing, but can’t be avoided in product development, and might even be exploited.
So what else is different about development compared to manufacturing?