How programmers distinguish roles, control risk and report work

Distinguish Roles & Control Risks:

To do each project, it is best to roughly the people who cooperate with their own class, a project in the life cycle of roughly four categories of people, owner, approvers, Critical reviewers, participants, abbreviated OACP model.

Owner refers to a person completely responsible for this project, fully owned the project, owner can only have one, there will be a number of cross-wrangling.

Approvers can also be understood as stakeholders, the interested party, the person who started the project.

Critical reviewers is a relying party of this project or a very large team, such as if the project depends on another project B, then B is Critical reviewers, there can be more than one, the owner makes every decision and Critical Reviewers communicate to ensure agreement is reached, and if no agreement is reached, the approvers can be communicated for adjudication.

Participants is a person who is associated with the project, but it is not particularly critical. These people will be able to inform you at the key point of the project without knowing the details.

As owner, we must attach great importance to the impact of critical reviewers on their own, because they are relying on the party, so often effective communication.

Reporting work:

How the report works: SBI model

Situation, the situation, that is, under what circumstances.

Behavior, action, that's what it's done.

Impact, influence, that is, what results are produced.

This is a more objective way of evaluating a person's performance, and you can use this model when organizing your report.

Original: http://blog.csdn.net/hongchangfirst/article/details/26001819

Author: Hongchangfirst

Hongchangfirst's homepage: http://blog.csdn.net/hongchangfirst

How programmers distinguish roles, control risk and report work