The first month of "Martian development documentary: One Thousand and One night of agile development": the birth of a product

(Preface, one, two, three, four, five)

 

The first month: the birth of a product

 

There was no king, no Prime Minister, no Queen capable of telling stories, and no requirement documents. The development started like this:

Why not write the requirement document first?

Because agile development does not write documents! No.

When planning this product, we have a great wish: to use this product to manage the product's own R & D. Although this does not mean that there is no requirement for a document that looks like a word, we still want to use only the features of the product as much as possible.

On the day when the project started, we had only one business plan in our hands (specifically in our mind), plus a general list of features of this product.

So how do you know what features to develop?

At least at the beginning, this issue is not very important.

Because agile tools have been available for at least 10 years, what functions should be available in them? They can be found on previous websites. However, it is not our goal to complete these functions or even surpass them. In the software field, a market that has been in operation for 10 years should be a market without any investment value.

Unless new values are discovered.

How was a product born?

Restricted by trade secrets, we will not write down the new values and business strategies we found at that time. The following describes what should happen when the next product was born.

Almost all products have similar products before they are developed.

Almost all products have followed up with similar products after development.

Almost all new companies are smaller than their predecessors and cannot catch up with their predecessors.

Almost all old companies are larger than their later generations, and they are easy to turn to the latter.

If you don't want to be dragged to death by the camels in front of you, and do not want to be trampled to death by the elephants in the back, you have to go a way that neither camels nor elephants can walk.There are so few such paths that many people have spent many years to find one, but fortunately we have not only found it, it seems that we have installed a street lamp.

Early Development meant to prove that this new path was feasible, rather than re-exploring the camel path.So at the very beginning, we don't need a complete list of functions, but the core value and some functions that can reflect that core value..

This is the core principle of new product development.

What should we develop first?

At that time, we chose the "user story display" function. This is the first feature we will use. Add, edit, and delete data directly in the database. Since we chose advanced technologies such as Asp.net, mvc2.0 (now using 3.0), and LINQ, the story was displayed on the screen in the first week. The first wish is fulfilled.

After another month, the addition, deletion, modification, and query operations were completed. In addition, a cluster editing interface was created, listing dozens of stories, which was extremely magnificent.

This seems to indicate that the future will be smooth sailing.