News for hackers. Stuff that matters.

Cu-chulainn

Ask HN: How to deal with disaster BD function

As a product manager how do you deal with a situation where the "BD" team are hopeless but senior management doesn't seem inclined to bite the bullet?They have no plan. They're not sure if they're doing BD or pure sales. When I listen to our BD director trying to talk about our capability it just sounds like semi-coherent babbling.Is there anything I could be doing as a product manager to try...

( Read More... | no comments | 2 points | on HN )
Re:Undebt: How We Refactored 3M Lines of Code on Wednesday August 24, 2016 @09:57AM (#12352016)
That's exactly what "Lean" is all about. When you spot an issue "pull the Andon cord" and stop the line, deal with the issue then and there. You then potentially conduct Kaizen to address the process to ensure the issue doesn't happen again.

At core all of Agile Software Development is aiming to mirror Lean in the manufacturing world. At the core of which is the concept of minimizing work-in-progress. Because WIP may result in waste if you subsequently find a problem that renders the WIP null and void. Hence the drive for continuous flow to minimize WIP and a "stop the line" mentality to spot and address issues when they arise.

I'm often amazed at how many people "doing" agile through sprints don't understand that the sprint is just an artificial mechanism to minimize WIP.

Not dealing with technical debt when it occurs is just increasing WIP.