The two main management software project management: traditional project management (predictive project management), agile project management;
Traditional project management (predictive project management): waterfall, part of the iterative development model, which requires the start of the project, needs clearly enough, enough document specification, iterative process needs to change more frequently, their distress is often caused by the greater of the project. I believe that many IT teams have tried, not repeat them here.
Agile Project Management as a new project management model, simplifies the process of traditional items, freed from the tedious process and detailed documentation. But do not plan on behalf of agility, a lot of people's idea of "agile fail to plan." This is wrong, whether "probacklog, scrum, Kanban, ignite map, burndown, user stories, etc." approach and work is Who do work basis? That is agile iterative, incremental delivery, which represents the XP, Scrum is one of the most widely used method, the core idea: embrace change, rapid delivery of software is available to customers through an iterative sprint, and to determine the direction of the product through the feedback, the products to maximize the benefits.
1. Management Process
Complete project management process consists of five processes: initiating, planning, executing, monitoring, finishing;
Agile project management framework: the idea, presumably, to explore, to adapt to the end.
- Envisioning Phase: Determine the product idea, project scope, project team and the team to work. Usually user stories way to dig deep;
- Speculate stages: the development of functional release planning, iteration planning and milestones to ensure delivery of products of conception (product roadmap - component teams - Project Charter - Process shear). The story mode workshop usually Deeply and determination;
- Exploration stage: in the short term can provide the function tested, constantly spying on the market \ customer feedback, reduce project risks and uncertain type; usually Scrum in probacklog, Kanban, burndown, ignite map, rates, etc. the way;
- Adaptation period: the audit results of the current delivery and current team's performance, rate, through the story point, MVP, sprint, daily station will, review, review other ways to protect the sustainability team;
- Closure: termination of the project, through the assessment, review, published to celebrate and experience exchange programs;
Traditional project (referred to as conventional): The range, speed, cost, quality, human resources, communication, risk, procurement, stakeholder management, each link there is initiating, planning, executing, monitoring, finishing. Attempts by maintaining the status quo, the software industry is a high-risk industry, embrace change, to adapt to change is a good way.
Agile Project (agility): simplifies the tedious process and detailed documentation, advocated self-organizing teams, centralized office, face to face. Scrum represented with: simple, continuous integration, continuous delivery, value, priority, changing the face of fierce embrace the principle of changing markets and evolving technologies. In agile, the project was into different levels: strategic, product, release, iteration will stop daily. The delivery is also divided into several levels: must have, should have, could have, some will not. , To demand a reasonable division through an iterative cycle, and through a time-based Sprint box to do security for the release of the software to reduce risk and improve software benefits;
Traditional triangle: range, cost and schedule (invariable range)
Agility iron triangle: schedule, scope, cost (schedule immutable)
Agile Triangle: value, quality, triple constraints (cost, schedule, scope)
Agility triangle:
1, the value of goal : to provide delivery of products
2, quality objectives : to provide reliable, adaptable deliverables
3, constraint target : within acceptable constraints and realize the value and quality objectives
Second, risk control
Project risks are present in any one project, in the event, the project will have a positive or negative impact.
Traditional project management: from the source to eliminate the risk and strive to risk management planning, risk identification through the process, comprehensive documentation, and risk qualitative / quantitative analysis of the risks to the solution. There is not a qualitative software industry, it may come from customers, markets, outdated technology and other unexpected factors, slowly and surely not the way to support rapid change and response.
Agile Project Management: Agile Project Management is different from traditional project management, work-oriented rather than time-oriented developing evaluation. Estimated using relative rather than absolute estimates in the development of job evaluation and its purpose is to reserve a space corresponding to the risk. Colleagues set of front-line staff Scrum Product Owner, the customer, stakeholder participation, experience sharing, brainstorming will be transformed into small teams of independent managers, adopt flexible model, a more favorable solution to the problem.
Summary: Whether traditional, agile, that no better, only to meet the current team is the best.
For example:
Donuts example: Agile teams can quickly bring to market a minimum usable product, write stories -> iteration, delivery -> market -> Collect Feedback -> Change Plan -> iterative, incremental delivery; and so on;
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
