I'm sure you know how deadlines work: collect the requirements/expectations & grok through them (understand them)estimate the effort needed to deliver the outcome, quantify risks, "guesstimate" unknown unknowns, ...... and "collide" what you've got with current commitments & team availability (to assemble a rough allocation plan)the result will be the estimated date for the moment when feature will be available to the end-users/clientsstrive to make it happenNo-brainer. This mechanism didn't change much since the "waterfall era". Surprisingly (or not ...) deadlines still exist in the "agile world" - just the delivery is sliced into smaller "sprints" & the…
All posts in ability to deliver
TL;DR Many engineering organizations postpone their most ambitious plans due to cost constraints for so long that they start to believe that it's only money that limits their capabilities. When they eventually get funds, they learn (in a painful way) that scaling up in an efficient manner is not really a matter of funding (actually it's one of LESS meaningful factors) -> software engineering is a very fragile process w/o a simple formula to define Ability to Deliver (Execute) in a period of time. Instead, there are several important components with lower than linear positive impact (above…
What's the most popular Agile method these days? FDD? Nah, no-one ever has seen a living FDDer - this method has been made up so there are at least 3 Agile methods on the list ... XP? Another fake - it's just a collection of programming techniques that: everyone has heard about barely anyone literally applies but all pretend to ... Scrum? Actually, Scrum is almost as rare as XP - it's the Scrum's lingo that is truly commonly used (it's passe to be a Team Leader these days, so everyone renames to Scrum Master) The most popular Agile method is Jesus-Driven…