Top Internet of Things Daily & Weekly

Faster. Faster. Faster. – Hacker Noon

Faster. Faster. Faster. – Maybe not. Good advice from @johncutlefish 
#Prodmgmt #IoT

  • The last thing stakeholders want, in this case, is to flip the script.There’s a legacy here.With project work, someone comes to you and asks for software that does X,Y, and Z. For fixed bid work, you get paid cold hard cash when you kick-off the project, hit some milestones, and…
  • You run the risk of incentivizing larger “batches” (due to the transactional / startup costs of projects in comparison to dedicated teams).
  • It really makes difference.I see many organizations interpret incremental delivery like this:We lay out all the “stories”, add up all the “points”, and finish the project in little increments.
  • In many cases, the organization is persuaded that benefits realization is a “long term” thing, and that there is no possible way to measure/learn prior to done.
  • In a build-measure-learn approach, things might look a bit like this:The team is tasked with moving some user/customer/business metric.

On the left, we have the build-measure-learn loop. And on the right we have the common build-build-build. Think about “fast” in the context of these two approaches. With build-measure-learn, we are…

Faster. Faster. Faster.I’d like to talk about fast.On the left, we have the build-measure-learn loop. And on the right we have the common build-build-build.Think about “fast” in the context of these two approaches. With build-measure-learn, we are optimizing for learning. We move around the loop as quickly as possible. It might look slower to someone on the outside, but we are learning more quickly. With build-build-build, we optimize for output. We ship as quickly as possible. Sometimes output is the right tactic, but sometimes it leads to this:One winner in five tries. Not good! Time for a silver bullet (joke).The problem is, we tend not to kill the features. So we have to 1) maintain the complexity, and 2) work around the complexity when adding additional functionality. Poor Ops! They’re often left running all of this under-used functionality, and somehow have a problem getting more headcount. Anyway.If we aren’t careful, we also miss good opportunities:Note how we are able to pursue alternative paths with build-measure-learn. We kill some ideas, test new ideas, and amplify what works. With build-build-build, we’re about executing to a pre-determined plan. The last thing stakeholders want, in this case, is to flip the script.There’s a legacy here.With project work, someone comes to you and asks for software that does X,Y, and Z. For fixed bid work, you get paid cold hard cash when you kick-off the project, hit some milestones, and deliver the project. Perhaps you also agree to host/maintain the software, in which case you collect…

Faster. Faster. Faster. – Hacker Noon

Comments are closed, but trackbacks and pingbacks are open.