200 likes | 384 Vues
From Alphabet Theories to Win-Win. Varady Emese 248. Today’s menu. Software Project Management as a Theory Human nature-based SPM theories Theory X Theory Y Theory Z Theory W. The Art of Software Project Management. Integration of software technology Economics Human relationships:
E N D
From Alphabet Theories to Win-Win VaradyEmese 248
Today’s menu • Software Project Management as a Theory • Human nature-based SPM theories • Theory X • Theory Y • Theory Z • Theory W
The Art of Software Project Management • Integration of • software technology • Economics • Human relationships: • different type of people • cooperation between groups
Partial Guidelines Use disciplined reviews Do it top-down Prove everything correct Do it outside-in Use walk-throughs Programming standards Independent test teams Chief Programmer teams Measurable milestones Early requirements baseline Program Library Involve the user Structured Programming Configuration management Design verification Project work authorizations End-item acceptance plan Automated aids Unit development folders
Attempts for S.P.M Principles Government software acquisition: strong procedural aspects – weak human relationships Weinberg(1971 - The Psychology of Computer Programming): strong human-relations – weak economic aspects Reife (1986): 5 principles Boehm(1983 – Theory-W): 7 principles
Frederick Taylor: Theory X People • People inherently dislike work • They have to be coerced into working • They prefer being told what to do • Management - organizing elements in the interest of economic ends • people: motivating, controlling their actions, modify their behavior • Manager: persuading, rewarding, punishing, controlling
Drawbacks Not for long term Stunned people’s creativity, adaptiveness, self esteem Unable to cope with change
McGregor: Theory Y Want to take interest in work Motivations, potential for development, satifsaction -> commitment to work Seeks responsibility Management - Organizing elements in the interest of economic ends - People achieve own goals <-> organizational objectives
Drawbacks Difficulties dealing with problems To much faith in people Manipulation
Ouchi: Theory Z cooperative and intimate working relationships between employees (& manager) Sense of order Discipline High need to be supported by the company • Shared values • Major decisions = consensus • Job for life • Main concern: • Employee’s well-being • Stable employment • High productivity
Drawbacks High degree of confidence in workers Workers generalists not specialists Promotions tend to be slower Focuses only on a single organization
Theory W: Win- win Project managers winners all participants winners Plan the flight and fly the plan Identify and manage you risks
Win-win, win-lose, lose-lose Quick & sloppy product: win for developer – lose for the maintainer and customer Unrealistic schedule, incompatible people, poor planning => lose-lose Win-win = attention to people’s interest & expectation
Theory-W Win-Win Steps • Establish a set of win-win preconditions • Understand how people want to win • Establish reasonable expectations • Match people’s tasks to their win conditions • Provide a supportive environment • Structure a win-win software process • Establish a realistic process plan • Keep people involved • Provide feedback • Structure a win-win software product • Match the product to the users’ and maintainers’ win conditions
Strategic Guidelines Derived from Win-Win Preconditions Win-Win Precondition Developer Team Users Maintainers Customers • Operations • concept • Operations • procedures • Cost-benefit analysis • Career path development • Mission Analysis • Operations • concept • Prototyping • Requirements • spec • Early users’ manual Understand win conditions • Requirements scrub • Team building, negotiating, communicating Reasonable expectations • Resource allocation • Change control participation Match tasks to win conditions • User-spec reviews • Prototype exercise • Quality assurance • Status tracking • Early error detection • Customer training Supportive environment preparation • User training • Cutover preparation • Modern programming practices
Strategic Guidelines Derived from Product, Process Guidelines Guideline Users Maintainers Customers Development Team • Operational plan • Installation and training plans • Life-cycle support plan • Development plans Process Planning • Risk management plans Process Involvement • System engineering plan participation • Review participation • Prototype exercise • System engineering plan participation • Review participation • Quality assurance • Cost-benefit reviews, approvals • Delegation • Planning participation • Team building, negotiating, communicating Process Feedback • Reviews • Reviews • Status tracking, controlling • Performance feedback • Service-oriented • Efficient • Easy to learn • Easy to use • Tailorable • Easy to modify • Programming standards Product Structuring • Efficient • Correct • Feasible • Easy to modify • Balanced • Correct
Questions? Note: notite la slideurigasitijos, la “notes”
Bibliography http://www.lindgren-packendorff.com/packendorff_1995_scjm.pdf http://en.wikipedia.org/wiki/Theory_Z_of_Ouchi http://petervenn.tripod.com/brochure/complete/xyz.htm http://www.referenceforbusiness.com/management/Str-Ti/Theory-X-and-Theory-Y.html