In Agenda Series 1 (Agenda Series (1) How to Use Two Sets of Tools to Identify Requirements), the compass mainly solves the problem of where, and defines the scope in the main pain points of a group of users. The map mainly solves the problem of what, and today we Number List will talk about the problem of "how to do" how.
When the user's feedback has been grasped in hand, according to the user's future journey and the grasped "core scenario", the converted demand, how to plan the demand systematically? How to connect them together into something that can be delivered to users.
In the early stage of product birth, the most important thing in actual work is to be close to users and product planning. Let us first introduce an agile concept.
01 Agile Iteration
According to the agile development method, it needs to be fast enough and iterate in small steps to quickly meet the needs of users (I am not good enough at this point).
Therefore, an iteration is usually done every 1-2 weeks, and several iterations are done together to release a user-aware version.
(Picture invaded and deleted)
1. Story : Story
It refers to a complete user story (function point). If it is based on the event process, it can be a whole link of a user's participation in the schedule. For example, in the schedule, I will make a "group calendar". Allow teams of more than two people to share a working hours panel. The details of that story will at least include:
1) Early stage
At least the administrator role and the member role are involved, the manager acts as the initiator, and the member role can participate in the schedule occurrence.