Online discussion "Agile Development user story classification and organizational structure (three)" 2012-08-28 (Tuesday) _ Agile Development

Source: Internet
Author: User
Phase One: Activity description, one, BIS, three, four, 52: Activity description, one, BIS, three, four, five, 63: Activity description, one, two, three, four, five

Topics: User stories and plans/architecture/development/testing-Martian requirements Management concept (three issue) Date: 2012-08-28 (Tuesday) 13:00~14:00 objects: Product managers, project managers, and development backbone, biased towards demand management and product design. Keywords: planning, architecture design, task management, Test History review: The first issue of the beginning of the project, whether based on the needs of outsourcing quotes, or based on the needs of internal development manpower and duration planning, need a kind of data to provide decision basis, And the user story with the function point analysis method, can evolve into "business data" and "business operation" These two kinds of large granularity of counting units, and its correspondence with the workload in the international accumulation of data many, can effectively and accurately complete this function. Phase two is mainly about when the software reaches a certain scale, different user stories cannot be simply arranged as list structures, but rather to establish dependencies so that they can be displayed at different levels, and in addition to enhancements, refactoring, and defects, these user stories should be subordinate to certain business data or business operations, and their syntax cannot be used as ... ... OK...... In order to ... ", but to study its special grammar. content of this issue: 1. Review of Phases 1 and 2 2. When you have a large number of user stories, how to use the user stories directly generate version plan. 3. What is the relationship between software architecture and user stories? Why is it that in MVC mode, the structure of user stories can be directly transformed into software technology architecture. (emphasis content) 4. What is the relationship between "use cases" and user stories in UML. 5. Why the test should be based on user stories. How to perform test case choreography based on user stories.

The product requirements management concept in this topic, most of which has been implemented in the Martian Agile development free tools, is welcome to focus on the future of the Martian articles in this blog.


Live site QQ Group: 190375042 Pmbar Project Practice Group, need to submit a resume, welcome to the project Manager to join, join the registration:

Broadcast site: The left four QQ group of the blog are broadcast, the question will be reverse broadcast to the live scene, please add the corresponding QQ group according to their place.

Contact Us

The content source of this page is from Internet, which doesn't represent Alibaba Cloud's opinion; products and services mentioned on that page don't have any relationship with Alibaba Cloud. If the content of the page makes you feel confusing, please write us an email, we will handle the problem within 5 days after receiving your email.

If you find any instances of plagiarism from the community, please send an email to: and provide relevant evidence. A staff member will contact you within 5 working days.

A Free Trial That Lets You Build Big!

Start building with 50+ products and up to 12 months usage for Elastic Compute Service

  • Sales Support

    1 on 1 presale consultation

  • After-Sales Support

    24/7 Technical Support 6 Free Tickets per Quarter Faster Response

  • Alibaba Cloud offers highly flexible support services tailored to meet your exact needs.