微软产品开发管理-1.pptVIP

The goal: Build to spec on time The risk: People: Customers, personnel, organization, skills Process Mission, budget, cost, schedule, design, build, test Technology Security, dev and test environment, tools, availability Environment Competition, economic, regulation, legal Retired Risks Risk Assessment Document Top 10 3. Plan 5. Control 2. Analyze 1. Identify Risk Statements 4. Track The ongoing deliverable of this process is a living risk assessment document Research projects during minor releases Market trends and advances Competitor innovations and directions Evaluate technologies Capability, quality, sophistication Ease of use Team skills Prototype Identify key risks Define experiments Simulate end result Balance among resource, feature set and schedule Define tasks and estimates Parallel development Schedule commitment Schedule ownership Credibility/Predictability Daily builds and smoke tests The heartbeat of your project Crucial to maintain project consistency, integration, quality and visibility Tracing bugs Weekly bug status report Bug threshold Status meetings Have a specific purpose Involve PM, QA, and UE Keep it short and frequent Keep a list of outstanding issues Managing by walking around (MBWA) Shows you are involved and care about the project Some people not comfortable speaking at meetings Regular one-on-one with team members Sharing information Share success Share failure Changing Course Get the facts, but don’t overanalyze Involves others in the discussion Use external teams to augment dev and test Cut features instead of extending schedule Changing Speed When to increase pressure To meet milestones To recover from a missed date To response to external competitive pressure How to increase pressure Duration – be clear how long overtime will last Comfort – make overtime enjoyable Spirit – team commitment Progress – show the team the progress Appreciation – recognize team’s effort Test in real world Feedback (features, performance, UI) Marketing