Posts Tagged ‘agile’
Don’t allow yourself to brainstorm to death.
Don’t spend countless hours trying to perfect the business plan or tinkering with the product pre-launch. Attempting to guess how your customers will react to your creation is pointless. Get ACTUAL feedback from them instead.
Accept the fact your product may look nothing like it does today a year from now.
To the point above, you may be determined to go in one direction but quickly discover that the market pulls you in another. Go where your customers take you! For example, did you know that Sony’s first product was a rice cooker? Since abandoning the rice cooker, it has merely managed to become the world’s biggest consumer electronics company.
Be your own competition.
The best way to beat the competition is to constantly be improving your products. In fact, each version should make the previous one appear obsolete. And, while your competition is focused on the current one, you should already be on to the next version. As the saying goes, it’s not easy to hit a moving target.
Interesting, slightly negative take on Lean Kanban processes…
All software development methods are compromises – imperfect attempts at managing risks and uncertainty. Sequential or serial development methods attempt to specify and fix the solution space upfront, and then manage to this fixed scope. Iterative, time-boxed development helps teams deal with uncertainty by breaking business needs down into small, concrete problems and delivering a working solution in regular steps. And iterationless, continuous-flow allows teams to rapidly test ideas and alternatives, when the problem isn’t clear and nobody is sure yet what direction to go in.
There’s no one right answer. What approach you follow depends on what your priorities and circumstances are, and what kind of problems and risks you need to solve today.
Seen this idea before, this article has a diagram.
If we do the right product right, but slowly, we might miss out on market opportunities. What if we run late and there’s a reality shift, and no one will need our product anymore?
If we do the right product fast, but in a wrong way, this means putting off problems till later. There will be only 2 options: stitch fixes over fixes and bury the product in 10 years, or re-write it from scratch, which is costly.
If we do the wrong product right and fast, hardly anyone will need it, unless we come to understand what’s wrong and make fast changes.
Ideally, we should get to the center, where the 3 circles overlap.
Nice view of product development.