微软项目管理MSF V4.0

1、Lean Thinking in MSF v4.0,David J. Anderson Program Manager, Microsoft,Lessons learnedfrom Feature-Driven Development,How Do You Charge For Your Art?,Agenda,Background Lean Thinking in FDD Value Flow Pull Visual Control Continuous Improvement Right First Time & Pokayoke Lean Thinking in MSF v4.0 & V

2、STS,Singapore Story,Peter Coad,Jeff De Luca,Feature Driven Development,FDD and the Agile Manifesto,Kent BeckMike BeedleArie van BennekumAlistair CockburnWard CunninghamMartin Fowler,James GrenningJim HighsmithAndrew HuntRon JeffriesJon KernBrian Marick,Robert C. MartinSteve MellorKen SchwaberJeff Su

3、therlandDave Thomas,Jon Kern, Director of Consulting at Togethersoft stands in for Peter Coad at Snowbird, Feb 2001,Book Published September 2003,Declaration of Interdependence,We increase return on investment by making continuous flow of value our focus. We deliver reliable results by engaging cust

4、omers in frequent interactions and shared ownership. We manage uncertainty through iterations, anticipation and adaptation. We unleash creativity and innovation by recognizing that individuals are the ultimate source of value, and creating an environment where they can make a difference. We boost pe

5、rformance through group accountability for results and shared responsibility for team effectiveness. We improve effectiveness and reliability through situationally specific strategies, processes and practices. 2005 David Anderson, Sanjiv Augustine, Christopher Avery, Alistair Cockburn, Mike Cohn, Do

6、ug DeCarlo, Donna Fitzgerald, Jim Highsmith, Ole Jepsen, Lowell Lindstrom, Todd Little, Kent McDonald, Pollyanna Pixton, Preston Smith and Robert Wysocki.,/,Agenda,Background Lean Thinking in FDD Value Flow Pull Visual Control Continuous Improvement Right

7、First Time & Pokayoke Lean Thinking in MSF v4.0 & VSTS,Value,Feature as unit of customer value Tiny piece of client-valued functionality which can be delivered in less than 2 man weeks Business Logic Feature of|to|from|for E.g. list availability of conference venues for given dates and attendee numb

8、ers,FDD Value Stream,Develop an Overall Model,Build Feature List,Plan By Feature,Design By Feature,Build By Feature,Marketing Requirements,Finished Code,Test,Build Cycle,Bug Reports,Engineering Lead Time,FDD Milestones & EV,Smooth Flow,WIP,Lead Time,Littles Law Confirmed in Software Engineering,Ragg

9、ed Flow,Maintaining Flow,Daily “scrum” meeting Aggressive issue log management Generalist vs. specialist workforce Can be deployed to areas where flow is slow or stalled,Pull,Understand the capacity in terms of Features per unit of time Pull new features from a demand backlog at the same rate featur

10、es are delivered to system test Feature list is prioritized by the customer using Kano modeling,Visual Control - Project Dashboard,Visual Control - Feature Milestones,Visual Control - Batch of Work,Continuous Improvement,More Real Project Data,More WIP Control Analysis,Right First Time & Pokayoke,Co

11、ad Method Modeling Techniques Enables postponement (decide late) Design Error prevention Patterns Design Review Code Review,Postponement (of component definition),Pinks and yellows are re-usable across multiple greens the core Enterprise Components,Greens and blues are re-usable across discrete Ente

12、rprise Applications modeled as sequences of pinks,Rework is avoided,Agenda,Background Lean Thinking in FDD Value Flow Pull Visual Control Continuous Improvement Right First Time & Pokayoke Lean Thinking in MSF v4.0 & VSTS,Single Product Backlog,Single backlog of all Work Items (Reqts, Tasks, Bugs, etc.),Queries to filter, view, report,Details for each entry,Complete change history,Project Portal,Process Handbook,Logical Infrastructure Designer,Services assignedto logical infrastructure,Architecture validatedagainst operationalsettings and constraints,Pokayoke - Unit Tests,Unit Te