[Reprint] Project risk management seven kinds of weapons-peacock feather

Source: Internet
Author: User
Tags rounds

Updated the project plan of the small handsome Ben thought it was all right, but just after a week, Mei found Shian, because the project has been postponed. As a result, Xiao Shuai opened the manuscript of Professor degree.

"The real victory is not your weapon, it must use your confidence." No matter how terrible the weapon is, it is not equal to human confidence. ”

Key Words :

Confidence comes from the fully confident!

Peacock Feather has long gone, he lent Koritsu is just " confidence ". "The real victory is not your weapon, it must use your confidence." No matter how terrible the weapon is, it is not equal to human confidence. ”

Interpretation:

The project team's confidence comes from the progress of transparency, below we look at the progress of the risk of the exclusive weapon: Peacock feather.

There are several scenarios where there may be a progress risk:

    • First, there are deadlines for projects, such as with some kind of activities (Baidu World Congress, Hackathon activities, 618, etc.);

    • Secondly, the technical programme is more complex and needs to be adjusted according to the progress of the project;

    • Third, the project objectives in the process of change, more aggressive, compression of the project cycle;

    • IV, with third-party dependencies (cross-team, cross-BG, out-of-company), whose progress is not controlled;

    • Five, the project task decomposition confusion, progress is not transparent, there is no milestone planning situation.

The effective response is:

    • First, the appropriate buffer is set aside from the planning stage;

    • Second, close tracking, through the Burndown chart and other ways to pre-anticipate the project schedule problem;

    • Then, fast iteration, small steps, set a reasonable priority for work, once the problem occurs, you can reduce the demand range according to the value and priority;

    • Finally, to ensure that the person responsible for the follow-up, to achieve rapid response.

Next go to a real project, first the project features are as follows:
    • Product Development stage: the direction of exploration after successful need to accelerate the promotion

    • Project Organizational structure: cross-team

    • Team Organizational structure: module team

    • Product Type: Platform

    • Project period: Medium (1-3 months)

    • Category: Platform category, micro-innovation, research and development, strategy-based

    • Development Model: Iteration

    • Risk Identification phase: Project Kickoff when

    • risk Trigger Phase : Iteration 5 (through Burndown chart to discover that the original target cannot be completed by the end of the year)

    • Risk Type: Progress risk

    • Risk Description: The project in the company has a number of competitive products, in order to highlight the siege, establish a word of mouth, the boss of the project team put forward the goal is not satisfied, decided on this basis multiplied by 10! That is, in the effect of each dimension to achieve 10 times times the goal! The goal is too aggressive and the project team believes that the risk of achieving this goal is enormous.

Risk Assessment :

    • First, the project team is not in a hurry to persuade the boss to change his goals in the event of great pressure. Instead, the project team spent about a week, after 6 rounds of discussions about technical feasibility, eventually accepting new goals and giving a very aggressive schedule, while identifying the huge risks.

    • Second, in the scheduling phase, the project team divides the entire project into five directions, each of which splits the overall objectives into weekly milestones based on business value priorities for easy follow-up.

    • Then, synchronize the entire program and risk to the entire project team.

    • Finally and most important, agree with the boss, one months later, that is, the first key milestone, re-evaluate the feasibility of the project objectives, if necessary, then according to the actual data to adjust the target.

Risk monitoring :

    • Risk monitoring process, focus on this high-quality risk.

    • Project in the process, the project personnel into a closed state, rapid iteration, the daily Stand, communication progress, in order to quickly solve the problem.

    • The role of the project ensures that the most important sub-direction objectives are prioritized and that human and resource priorities are adjusted to the priority sub-direction.

    • At the beginning of the project, the dashboard of the whole project is established, and the progress of each sub-direction can be monitored in real time.

    • At the same time, ensure that every two weeks and the boss synchronize progress, seek support and listen to feedback.


Problem occurs:

    • After monitoring 5 rounds of iterations, we found the problem. The Blue line in the figure is a Burndown chart of five iterations, which is predicted by this trend, the red line in the figure, we will have a lot of work to do at the end of the year, that is, the target cannot be reached at the end of the year.

    • In detail, progress was made in 4 sub-directions in 5 sub-directions, and the fifth direction was not progressing because of the low priority.


Problem solving:

    • As a result, the project team and the boss communicated based on the data and, based on this trend and priority , proposed a reduction in the scope of the project, leaving the fifth sub-direction for project two.

    • The proposal has been endorsed by the boss, and the new goal remains challenging and risky. The project team first informs all the new targets and adjusts the schedule and schedule quickly, adapting the manpower and resources to a new iteration quickly. The Green line in the figure is the adjusted Burndown chart, which finally completes the new target at the end of the year.

See here, small handsome suddenly enlightened, with Xiao Mei discuss how to use Peacock ling to solve the current project problems. To know the funeral, and listen to tell.

Blog to: "Project risk management seven kinds of weapons Peacock Ling | Baidu Agile Coach"

[Reprint] Project risk management seven kinds of weapons-peacock feather

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: info-contact@alibabacloud.com 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.