Adaptive Software Development (ASD) embodies principles that teach continuous adaptation to the work at hand is the status quo. ASD was created to replace traditional Waterfall variants. In a general sense, ASD processes represent a repeating series of speculate, collaborate and learn cycles. “Speculate” refers to the planning paradox—outcomes are unpredictable, therefore, endless suppositions on […]
A Good SDLC = Team Empowerment
A good SDLC does not force developers to use any specific methodology such as Waterfall or Agile. Instead, it empowers project teams to decide which practices to use, within guidelines, for each project. Once the choice is made the teams remain on that pathway until production deployment. Team empowerment is a greatly misunderstood concept. Empowerment […]
Who’s to Blame for Troubled Projects, IT or the Business?
There is enough empirical evidence to say that poor requirements contribute to the majority of project failures. Look at these study conclusions published over a 13 year period beginning in 1995: Requirements problems have been proven to contribute to 20-25% of all project failures. The average project overran its budget 189% and its schedule by […]
Best of the Best Practices
In Chapter 2 of The Ultimate Guide to the SDLC, 12 historical system development models, both agile and waterfall based, are compared as well as one hybrid and one philosophy. The best practices from each model are extracted and extrapolated into a best of best practices model. None of the Waterfall or Agile models provide […]
IT Governance and the SDLC – Part 2: Upfront Requirements Elicitation
When discussing investment opportunities at governance meetings, senior managers invariably ask: “How much will the project cost us?” In the early phases of opportunity talks many IT leaders respond with the “SWAG” (Scientific Widely Aimed Guess) based on experiential supposition. Later, after governance approves a deeper investigation into the cost, IT leadership returns to governance […]
Recent Comments