Posts Tagged ‘process’
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.
Some standard business process terminology: Business Process Analysis.
Interesting discussion of how a team moved to continuous deployment, including their current process:
Every new feature should ideally be pulled by more than one customer before showing up in a release.
An interesting take on modern software engineering process.
Interesting discussion on why releasing a lot is a good thing:
It’s results in a better product.It results in happier customers.It fosters happier developers.
Give your team 1 point for each “yes” answer.
A score of 12 is perfect, 11 is tolerable, but 10 or lower and you’ve got serious problems. The truth is that most software organizations are running with a score of 2 or 3, and they need serious help, because companies like Microsoft run at 12 full-time.
How do we score?