Mars development documentary: Agile development One Thousand and One Nights 4 months: Classification of user stories (II)

(Preface,One,II., 3, 4, 5)

 

Try Classification

There are various classification methods to reorganize user stories. below is my own classification, not a mature method. When using these methods, you must understand the intent rather than the method, so that you can flexibly modify it when you have other intentions.

Granularity		Visible to customers		Visible to product manager	Visible to the development team
Product Features	Data level	Epic	Restructuring debt
	Operation Level	Function
Version release description	Enhancement level	Enhanced		External Defects	Internal Defects

Granularity dimension

Data is the business data that a group of users want to operate on.For example, a system with user management must have "users, roles, permissions ......" The data to be operated. A file is a "business" data that the System user can understand, rather than a non-technical data (such as a database table ). Data is a noun.

Operations are business operations on a group or multiple groups of data.To "create roles" and "delete users" for operations on a group of data, for example, "Assign roles to users" for operations on multiple groups of data ", the operation is the business operation of the System user (that is, the operation of "working at ordinary times"; As mentioned earlier, "Move the button above the screen" is not the user's business operation ). Operations are all a verb.

The so-called enhancement refers to the content used for attributions, inactive comments, and complements.. For example, start the case1It is what users do for convenience, neither the data to be managed by users nor the operations that users usually work on.

This dimension is easy to understand at the "customer visibility" level.

For example, to describe the features of a product, you only need to display the customer's visible epic and features.

For example, when describing the product version release description (upgrade announcement), you should display the changed epic, function, and enhancement.

Degree of presentation

In addition to what customers can see, there are some things that need to be known by product managers and development teams themselves. The scope they know is forward, that is, what customers can see, what product managers can see, what product managers can see, And what development teams can see.

There are two types of defects: the ones proposed by the customer and discovered by the customer. The former will be displayed to the customer (in the product upgrade announcement), and the latter will be available to the product manager.

Reconstruction is caused by the convenience of development, maintainability, performance, and re-design of functional implementation methods., You do not need to disclose it to the customer and Product Manager (although the product manager often knows ).

Debt is what developers may leave behind as a "shortcut". This "possible problem" means that problems may occur after changes to the functions and structures in the future, rather than problems with the current operations (which should be called defects ). Therefore, you do not need to correct it now, but you also need to leave a mark for future reference.

Actual usage

In actual projects, I found that such classification may vary depending on different projects. For example, we want to add three types of internal poems, internal functions, and Internal enhancements recently, because some functions are made for internal development convenience, and there are also differences in files, operations, and enhancements.

We also set different stories like "as ......, Yes ......, So that ......" But it is not very mature and will be shared with you later.

Therefore, the classification method is often changed in specific management, so the content of this article will change in the future. You should also rethink whether the previous classification is appropriate in each project.

Appendix: syntax templates for different types of stories

About a month ago, when we wrote a help document for the Martian, we summarized the syntax templates for different types of user stories.

The Martian installation package will be released within one month. Please log on to the case site with cheny and visit the product "Martian". When you hover your mouse over the Help button, you can see the explanations, examples, and syntax descriptions of different user stories.