"Original" Job book-product/Project Manager (II)

Product/Project manager post work Book

---------------------

Job Book coordination is an important part of the development workflow, detailing the work of each post in each stage of the development process.

one, every day routine work:

1. Immediately after starting work in the morning, the ceremony was held

2, write the summary of the ceremony to the relevant people

3, in the journal to develop today's work plan and hang to the main line

4, Upper Zen Road Check whether the progress of the task is consistent with the plan

5, the upper Zen Road check whether the bug repair is normal

6, to deal with various temporary tasks, add to the Zen Road task list, such as: Party a urgent task proposed by

7, if necessary, with the technical manager, test Manager to communicate

8, find the development progress has serious delay, and immediately communicate with the superior leader

9. Take the time to participate in the test to understand the real situation of the system

second, week one routine work:

1, the company level of the project team weekly meeting

third, the end of the week routine work:

1, the project Team week work summary meeting

2. Send the project week summary to the project team management and management team.

Iv. Phases of work:

1 , Demand discussion

Responsibilities: General Manager

Collaborators: Technical manager, Test Manager and front-end engineer.

Job Description:

Organize the meeting with party A to communicate the needs, according to the communication results with the front-end engineers to create a static prototype, and then to the party to continue to communicate, iterative, until finally through the static prototype implementation of each requirement

2 , Demand confirmation

Responsibilities: General Manager

Collaborators: Technical manager, Test Manager

Job Description:

1, the Step 1 to implement the requirements of entry into the Zen Road:

Menu path: Product à demand à ask for

Required fields: Product, ownership plan, source of demand, no need for review, requirement name, priority (set to 1), requirement description (detailed description of requirements, and static prototype page link), Copy to (Project group management)

2. Notify the Technical manager and test manager voluntarily after entering the requirement.

If necessary, organize relevant person to hold meeting and discuss the requirement details

3 , version definition

Responsibilities: General Manager

Co-author: none

Job Description:

1) Enter the upcoming release of the component version into Zen Road

Menu path: Project à version à create version

Required: Product, name number, builder, packing date (date the integration test is scheduled to be submitted)

The version number specification for each distribution is as follows:
A, version number second plus 1, the third place is 0, such as: V2.2.0
B, after the official release if there is a small change, then the third increment, such as: v2.2.1,v2.2.2 ...
In general, the release of a version of the cycle in two weeks, it is important to note that the component definition version, the version number of all components are required to be consistent, in order to call wine as an example:
There are at least a few component versions to define at this time:
A, micro-mall/PC Mall components V2.2.0
B, Order Center component V2.2.0
C, Commodity Center component V2.2.0
D, store system components V2.2.0
E, call center component V2.2.0
F, store app components V2.2.0

2) Associate the version with the requirements

Menu path: Project à demand à related demand

Required fields: and connect the version to the requirements (a requirement can be associated with multiple versions, such as: Requirement 002: Order List page support for multiple cities the different operators can only see orders from the city, this requirement involves: Order Center component V2.2.0, Commodity Center component V2.2.0, Micro Mall/ PC Mall Components V2.2.0 These versions, all to be associated with) in project-version-view bugs to see a list of bugs under this release

4. Assigning tasks

Responsibilities: Start brewing the next edition of the demand

Collaborators: Front-end engineers and other necessary personnel.

Job Description: Start brewing the next version of the demand

5. Detailed design

Responsibilities: If necessary, begin to discuss with party a the requirements of the next edition

Collaborators: Front-end engineers and other necessary personnel.

Work content: It is necessary to discuss with party a the next edition of the requirements

6. Coding and Unit Testing

Responsibilities: And party A to start in-depth discussion of the next version of the requirements

Collaborators: Front-end engineers and other necessary personnel.

Work content: And party a start in-depth discussion of the next edition of the requirements

7. Integration Testing

Responsibilities: Basically determine the main requirements for the next release

Collaborators: Front-end engineers and other necessary personnel.

Job Description:

8. Acceptance Test

Responsibilities: General Manager

Collaborators: Technical manager, Test Manager

Job Description: Sample testing of the entire system

9, the release version on-line

Responsibilities: General Manager

Collaborators: Technical manager, Test Manager

Work content: Supervise the technical manager's upgrade on-line work, responsible for submitting the relevant documents to party a

10, version Maintenance

Responsibilities: With party A to determine the next edition of the requirements

Collaborators: Technical manager, Test Manager and other necessary personnel.

Work content: Generally, within 2 days after the current version, with party A to determine the next version of all requirements (development content)

11. Discontinue Maintenance

Responsibilities: General Manager

Collaborators: Technical manager, Test Manager and other necessary personnel.

Job Description: Responsible for the operation on Zen Road, supervise the technical manager to complete the operation on SVN.

The following is my original software enterprise using Agile Development Series articles:

"original" Agile software project development and management process (i)"original" Job book-product/Project Manager (ii)"original" job book-Technical Manager (III) "original" job book-Test Manager (iv)"original" job book-Senior Programmer (v)"original" Job book-programmer (vi)"original" job book-front-end Engineer (vii)"original" Job book-Testers (eight)

"Original" Job book-product/Project Manager (II)