Differences

This shows you the differences between two versions of the page.

--- why_should_we_start_without_doing_a_complete_analysis [2020/06/02 14:21] – external edit 127.0.0.1
+++ why_should_we_start_without_doing_a_complete_analysis [2020/06/10 12:50] (current) – ↷ Links adapted because of a move operation hans
@@ Line 1: / Line 1: @@
 ====== Why Should We Start Without Doing a Complete Analysis? ======
-Or "Why shouldn't we do a traditional phase gate approach to projects?"
+> Or "Why shouldn't we do a traditional phase gate approach to projects?"
+> Or "How can we start working and still deliver 'on time'?"
-Or "How can we start working and still deliver 'on time'?"
-====== Premise ======
 When you move to agile, there is a tendency to say "we'll do this agile thing with developers, but we will keep our traditional phase gate approach to approving budgets". After all, to decide whether we should spend the money "we will need to know how much it will cost and that means we will have to do some level of analysis before making any decisions."
@@ Line 16: / Line 13: @@
   * We talked about small vs large batch sizes (where a big release of project funding is definitely a big batch) as described in [[what_is_the_effect_of_batch_size_on_how_long_something_takes_to_get_done|What Is The Effect of Batch Size On How Long It Takes to Get Something Done?]]
-But there is something even more basic than that
+But there is something even more basic than that.
 ====== Just Start ======
@@ Line 36: / Line 33: @@
 Of course not.
-This is not to say that we don't do approval for work when we take on an agile approach. Of course we do. We just minimize the analysis based on what is realistically possible, then start working anything that gets through while using [[blog:how_can_we_understand_the_real_value_of_fast_feedback_and_deciding_late|fast feedback]] to adjust the course we are heading based on latest information. In particular, we end up making more smaller bets based on current information, perhaps releasing money every quarter instead of developing a "committed plan" for years in advance.
+This is not to say that we don't do approval for work when we take on an agile approach. Of course we do. We just minimize the analysis based on what is realistically possible, then start working anything that gets through while using [[how_can_we_understand_the_real_value_of_fast_feedback_and_deciding_late|fast feedback]] to adjust the course we are heading based on latest information. In particular, we end up making more smaller bets based on current information, perhaps releasing money every quarter instead of developing a "committed plan" for years in advance.
 And yes, I understand, this is a change in the thinking. It will probably mean you will have to get the finance people, the business people, and the marketing folks involved in the change in thinking process. But given the economic benefits that could result, isn't the change worth the effort?
 {{tag>FAQ ProductBacklog Lean Waste Triage JustStart Scope}}
-~~LINKBACK~~
-~~DISCUSSION~~