Revelation: A big bang for a user's favorite product

Marty Cagan Published on February 9, 2010

Translator: Tanfong/revisers: Panshi Lin Ai Xu Dingxiang

What is "Big bang" type release?

This refers to a project team after months of effort to hit their work in a large new product launch.

Big Bang is not equal to waterfall development (the history of waterfall development, please refer to the Book of Revelation: Create user Favorite products, chapter 27th), but it is the most common in the waterfall development of the final link. Not only will the Big Bang release be used in waterfall development, but the scrum team is actually forced to use the Big Bang release.

Why did the Big Bang press conference have problems?

Because it's almost never going well. Usually the time is tight, the task is heavy, the release of the content is always more and more (management is impatient, as long as they want to add more features). Before long, the problem comes, you either overhaul big change, or painfully in the function of the cut.

In addition, the use of large-bang-released products, there is little time for you to be based on the actual data after the function of the adjustment. Many times, the results and expectations are different, but at this time has been powerless.

In addition, if you make too many changes at once, the stability of the site will be severely tested, because only after the line can you discover these problems and try to solve them. Even if there is no stability problems, users will be a one-time change in the site is too big and disgusted.

Since there are so many problems, why do you choose to do Big Bang?

There may be several reasons for this.

Sometimes it is because the marketing department wants to hold a big release event to shock, and they feel that the product should not be exposed until the activity is ready. It's a good thing we don't have to do big release activities as usual. Even if such activities are held, it should be understood that Big Bang marketing is not equal to the launch of Big Bang products. You can develop products in a step-by-step way, release new features at 1.1 o '-point, and make it almost impossible for users to notice any changes.

Sometimes the project completion time is too challenging for the supervisor to finish the task on time, and the product team has to reduce the time to test and release to ensure that there is enough time for product development. I know this is the last resort, but the product should not be developed in this way. If you really want to publish on time, the best way is to take incremental development and deployment. Let the product on time line does not necessarily use the Big Bang release mode.

Some companies, especially large companies, insist on project review and process supervision, thus "successfully" led the team to waterfall development, and finally had to choose the Big Bang release. For example, they would say: "You can continue to study this idea, but before you really do it, you have to pass the review." "So they have to do a review before releasing any functionality." This makes it difficult to steer the team towards waterfall development. Maybe you have to give your boss a "report show", but you have a lot of work to do, don't be discouraged by this little hindrance. In fact, you might be able to make a good impression if you take the prototype and the real user feedback to the boss for review. As soon as the review is over, continue with your incremental build, deployment, and testing.

So if someone asks you to take a big bang, try to replace it with incremental design, build, test, and publish.

Original link: http://www.svpg.com/big-bang-releases/

This article is an excerpt from the author's blog from the Book of Revelation: Creating users ' favorite products. This book introduces the practical experience and idea of modern software (Internet) product management from three angles of people, process and product. I hereby thank Mr. Marty Cagan for his authorization.

Article source: Seven printed tribal reprint please indicate the source link.