4 ms·
I don't think it's good to abandon up-front planning entirely. It's important to know what you're aiming for and to have a plan for getting there. The key thing
by nicoburns 6y ago
I don't think it's good to abandon up-front planning entirely. It's important to know what you're aiming for and to have a plan for getting there. The key thing about an agile approach is to regularly review the plan and be open to changing it as and when new information comes in.
- tremon 6y agoIt depends on the level of detail in the plan. The article says to delay the plan, not to skip it. The goal of that is to avoid fleshing out the details of parts that are not relevant to the current focus (with "focus" being defined as the scope of the current sprint). Of course, you need to know the direction of the project. But spending time on details that you cannot directly validate with implementation, risks both wasting time because of invalid assumptions, and risks wasting time because the requirements may change when you get around to implementing it. Remember that "planning a sprint" gets very deep very quickly. It's not just about setting direction, it's about deciding display names, storage types and UX interactions. The point of the article is that that level of planning should not be done months in advance.
- cestith 6y agoYour sprint planning is deeper than sprint planning some other places. Some places that at least claim to be doing Scrum will groom the backlog in one meeting, then choose which stories go on the sprint in another. Anything that needs agreement among developers is then tackled in pair programming or fairly ad-hoc "hack sessions". Implementation details, including details of code interfaces, user interfaces, and system interfaces, are left up to the contributor unless there's a need to align effort before that story is done.
- jonpurdy 6y agoTotally correct. This article is on the "totally idealistic" side, and I think it's important to know what is ideal as a benchmark when working in non-ideal situations. Executives and clients like to see timelines and total project estimates. I wrote an article* about this. The idea is that you do some rough planning, applying the principles of Agile story point estimation, and extrapolating a rough/relative timeline. Relative timelines with non-specific dates are useful for getting an idea of the scope and possible time of a project. Helps determine what should be built first, prerequisites, and what other teams might need to be involved (and at what stage). Also useful to get the product managers or executives thinking a bit more deeply about the project and perhaps reconsidering it, or reducing scope if it looks like it will be larger or take longer than expected. Once a project is kicked off, after a few sprints the initial plan can be updated based on the actual velocity of the team. * https://jonpurdy.com/pm-framework/how-to-quickly-plan-and-estimate-an-mvp/ https://jonpurdy.com/pm-framework/how-to-quickly-plan-and-es...
- maitredusoi 6y ago> Executives and clients like to see timelines Do they really need them? ;)
- marcinzm 6y agoThey need them because they all have their dependencies that they need to manage separate from this project. A client may need to plan training, transitions, budgets, deprecation of old systems, etc.
- bluGill 6y agoYes. They need to not sell the next version too soon, but start selling soon enough to develop hype. They need to decide if they should invest in updating the previous solution one more time while waiting... They need to decide if the whole is worth the cost or should they develop a different project instead.
- jonpurdy 6y agoOthers above me have mentioned the reasons why they need them. But I'll reiterate my emphasis on rough/relative timelines. Exact dates are impossible and the farther away a milestone is, the hazier the date is. As an example, a milestone a month away could be +/- a week, but a milestone a year away could be +/- three months.