For years I’ve heard people complain that process improvement is pie in the sky concepts that don’t work in the real world. First of all, that’s crap. Second of all, process improvement doesn’t work, until it does, and everybody’s looking to do the new-new thing.
Jamie Flinchbaugh’s blog post on “The Founder” is a great take and means that I’ll be watching this movie soon!
Source: The Founder and Experimentation — Jamie Flinchbaugh
Learning what works and what doesn’t work is driven by experimentation, real-world trials that inform us about cause and effect. How do we improve the ability to experiment? By reducing the cost, the effort, the friction required to test what
Click here for the complete article.
Rethinking What’s Next in Software Development
Al Shalloway is an acknowledged thought leader in how we design and develop software. In this post, he begins the conversation about where we are headed next. It seems that everyone is in software development these days and most agree that we need to improve. Al notes that the original manifesto mentions the Agile Manifesto mentions “the team 17 times, the customer 3 times, business twice and management not at all.” But rather than impaling the sacred Agile Manifesto cow, he offers us a place to start the conversation with his personal manifesto.
I think this is a wonderful place to start a conversation about where we go from here. If you have an opinion about how the software business needs to change, I encourage you to read this post.
A Personal Manifesto | Net Objectives
May 28, 2017 — Posted by Al Shalloway
Background and the Agile Manifesto.I have been asked several times to help in the rewrite of an Agile Manifesto. After having been involved in Snowbird 10 (the reunion of some of the original Agile Manifesto authors along with some others from the Lean/Kanban community) I realized there is no “Agile” community. Rather we have many sub-communities that are so diverse it is hard to think of them as being under one umbrella.
click here for more…
Source: A Personal Manifesto | Net Objectives blog
Is Kanban Right for your team? Yep.
This is a nice post from the folks at Breath Agile.
You’ve got the best performers in your team, yet they falter. If this sound familiar to you, it is time to look at a different approach that can help
Source: How to know if Kanban is right for your team? | Breathe Agile
I am asked on a fairly regular basis, “What can I do to help my career and ensure I stay relevant in the marketplace.” After writing several emails to people with my recommendations, I decided to jot
Source: Keeping Your Career Options Fresh | Bob Hubbard | Pulse | LinkedIn
Lots of us use a personal kanban to visualize our daily work. Kanban is a great way to see what you’re doing and what needs to be done. This article addresses a couple of real problems with kanban. How do I handle different types of tasks? What is the ‘right’ level of detail? I found this useful and I hope you will too.
Bob H 10/28/2016
This question comes up not only in Personal Kanban but also for teams and enterprise (portfolio) kanban boards as well. It is a great question – and quite often tricky to answer! What should be the level of work breakdown that gets visualized on the Kanban board? Should each card on your Kanban board be a project or a mini-project? Or should be each task that you can think of that you need to do at the lowest (smallest duration) level?
Click the link to continue to the article: How Granular should my (Personal) Kanban Board be? | The #1 Blog on Agile, Kanban and Project Management – Digite
More great insights from David Marquet!
Leadership Nudge™ – STOP TELLING PEOPLE WHAT TO DO This week’s Leadership Nudge comes from my visit to France. I was in Saint-Tropez where I saw some incredibly beautiful sail boats. I am always amazed at how well the crews function when sailing these magnificent craft. When these guys round the mark there’s not a lot…
via Stop Telling People What To Do — David Marquet