1/7/2004CSG - Project Delivery at UT Austin1 Making a Model Perform Adopting a methodology to your environment

1/7/2004CSG - Project Delivery at UT Austin2 Outline Key elements of XP UT – the Basics Fitting XP and UT together Versioning – Product Delivery The Garden – what makes it work?

1/7/2004CSG - Project Delivery at UT Austin3 The Four Values of XP Communication Simplicity Feedback Courage

1/7/2004CSG - Project Delivery at UT Austin4 Are there really variables in university software development?  Quality ???  Time ???  Resources ???  Scope ???

1/7/2004CSG - Project Delivery at UT Austin5 Are there really variables in university software development?  Quality – No  Time – Little  Resources – Seldom effectual  Scope – YES!

1/7/2004CSG - Project Delivery at UT Austin6 Key Principals of XP methodology Reliance on SCOPE Quality Work Involvement of Business Experts Incremental development and release Continuous testing Embracing change

1/7/2004CSG - Project Delivery at UT Austin7 Key Principals of XP methodology Accepted responsibility Local Adaptation Teach Learning Play to win Work with people’s instincts Small initial investment

1/7/2004CSG - Project Delivery at UT Austin8 UT – the Basics Six month training program Limited but robust and versatile toolset Evolution of toolset Full and real time integration Developer efficiency tools

1/7/2004CSG - Project Delivery at UT Austin9 Fitting XP and UT together XP Understand the business needs Emphasize communication Quick feedback Collective ownership UT Hire Business Analysts Adopt cultural norm thru Centralized Training

1/7/2004CSG - Project Delivery at UT Austin10 Fitting XP and UT together XP Stress quality Practice 80/20 rule Coding standards Be inclusive in your team Iterative delivery Simplicity UT Cultivate common protocol Simplicity and maintainability Involve Systems Staff

1/7/2004CSG - Project Delivery at UT Austin11 Fitting XP and UT together XP On site Customer Pairs Programming Teach Learning UT Deploy Trainees to Business Units Cross-department collaboration Pairs Programming Consistent Education R&D team

1/7/2004CSG - Project Delivery at UT Austin12 Versioning - A new delivery method Semi-annual project selection and delivery –Communicates to the community –Clear beginnings and endings –Framework to assist managers –Context of constant evolution –Rotates leadership

1/7/2004CSG - Project Delivery at UT Austin13 Versioning – Is it XP? Rough plan to start Short releases Iterative metaphor adjustments Testing plans Constant refactoring and reintegration Collective ownership

1/7/2004CSG - Project Delivery at UT Austin14 What is “Versioning” Shrink-wrapped Controllable cycles Community involvement Small teams – 3 to 8 Product Manager and Project Manager

1/7/2004CSG - Project Delivery at UT Austin15 What is “Versioning” Visible deadlines and celebration Courage to adjust scope Constant communication Flexibility Maintenance Management 360 evaluations

1/7/2004CSG - Project Delivery at UT Austin16 What is “Versioning” Stress estimates Expand the definition of Success Hard timelines with flexible release Identify stakeholders Inclusion of a user community

1/7/2004CSG - Project Delivery at UT Austin17 What is “Versioning” Focus on customers Product Life Cycle plan Post mortem of each cycle

1/7/2004CSG - Project Delivery at UT Austin18 The Garden Environmental requirements Articulated vision Management embrace change Flattened structure Reward at all levels Walk the Talk - Release of ownership

1/7/2004CSG - Project Delivery at UT Austin19 The Garden Environmental requirements Support scope redefinition Training Constant opportunities for creativity Failure tolerance Recognition of achievement

1/7/2004CSG - Project Delivery at UT Austin20 Challenges ahead for UT Improve collaboration Integrate larger refactoring projects Staff need for consistency Career path definition

1/7/2004CSG - Project Delivery at UT Austin21 Q&A Sheila Ochner –