Agile software development
The objective of an agile development team is to regularly release high-quality software so new features can be introduced and feedback collected. The goals of a traditional operations team are often in direct opposition as they focus on stability and uptime usually by seeking to minimize change.
Agile methods are empirical and encourage each and every project to measure its velocity and performance. Agile methods also encourage teams to inspect and adapt; changing their method and practices on the fly.
This short video introduces some ideas that will help us map why we can’t get agile going and take effective steps to actually succeed with it.
Today’s market is rapidly changing. Equipped users no longer accept or buy tools not reflecting perfectly their needs and buy instead “+1” recommended products providing “delight factor”. Typical company introduces structured and hierarchical organization in order to deal with complex task decomposition.
Tom Gilb presents the limitations and dangers of using Agile user stories to describe and manage requirements at the Smidig 2012 conference in Oslo.
Refactoring can pry panic’s fingers away from your poor, overburdened adrenal glands and restore your sanity. Not that it went missing, of course. Never that!
