Posts tagged timebox
Applying MoSCoW principles to parenthood – and it works…!
I consider myself father first and geek second, though some people may have different ideas about this. Tonight it happened the two met. With their mother away for a week vacation, my two sons have ample opportunity to try out every trick in their book on their beloved father (that would be me). At the same time, with my significant other away, I can take out my book as well – and meet their challenge. One of the frequent battles in our home is bedtime. It’s not that they protest when asked to retire. They will happily go upstairs. But everything from there takes for ever – undressing, neatly folding up and putting away their day time clothes, getting their pyjamas on, brushing their teeth and… the bed time story.
I have tried several ‘instruments’ for speeding up this process. Some I am not particularly proud of either. And none really worked – it still takes perhaps an hour from ‘time to go the bed’ until lights out. Tonight for some bizarre reason, I decided to apply the MoSCoW principle together with a timebox. And that seems to work quite well. The ‘project’ of getting them in bed with all the Must haves, the Should’s as well and their one big Could to some extent was More >
Agile software development, the principles. Principle 3: Deliver working software frequently
This is the third of 12 posts about the principles of agile software development. Purpose is to go back to the start of the agile manifesto (http://agilemanifesto.org/principles.html) and discuss the implementation of the 12 principles in real life software engineering. Goals of agility are to go deliver software of higher quality, faster, with a higher acceptance to end-users and able to follow the changing business requirements to strive for competitive advantage.
The question is: is this going to work in practice or is this only based on a nice marketing and sales story.
Principle 3: Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale.
Old school linear development methods rely upon the assumption that an extensive specifications and design phase upfront will resolve all uncertainties and specify of all possible functionality in depth. After the design phase the development team retreat to their software factory to deliver the desired software in one big bang (in many cases many months or even more than a year later).
The result of this linear approach is a system; of witch the customer thought More >
Recent Comments