Using the Essential Unified Process with Visual Studio Team System

Using the Essential Unified Process with Visual Studio Team System Ian Spence and Craig Lucia

Agenda • Introduction • A new paradigm with several exciting innovations: • Practice separation • Practice user experience • Practice smartness • Innovations that can help you today: • Making process adoption easy / making VSTS adoption easy • Demonstration • Final words

What is the Essential Unified Process? • The first Next Generation Process • A pre-built assembly of 8 core practices • The foundation for the creation of your own processes • A framework for the addition of further practices

Building on our heritage Ericsson Approach Late ’60s Objectory Process ‘87 –’96 The Unified Process ‘97 –’98 IBM Rational Unified Process ‘99 –’05 Good Software

Essential Unified Process – Key characteristics • A complete, useable software development process • Delivered in the way that suits you on the platform that you use • That’s easy to adopt and tailor •  Agile •  Lightweight •  Universal •  Extensible •  Scalable •  Complete •  Sufficient •  Comprehensive •  Recursive •  Free •  Open Source •  Adaptive •  Easy to Use Use Case Architecture Iterative Component Product

Bringing more power and flexibility to VSTS • VSTS unites the team around a single way-of-working • VSTS is very good tool for tracking and managing work • On top of this, we can add MORE capabilities: • Practice separation • Process composition • Dynamic task generation • It is not just the work items that we define, it is the way they are used + Enhancing Visual Studio Team System

More than just a Unified Process…. …the first of a new generation of software development processes.

A Next Generation Process is not monolithic Process becomes second nature In the future, an ever present but invisible process And the innovations of a new paradigm Practice Separation Practice Smartness Practice User Experience Practice is a First Class Citizen the unit of adoption, planning and execution of process A new paradigm From the successes in modern software development Unified Process Camp Process Maturity Camp Agile Methods Camp

NEW A Next Generation Process is not monolithic Process becomes second nature In the future, an ever present but invisible process And the innovations of a new paradigm Practice Separation Practice Smartness Practice User Experience Practice is a First Class Citizen the unit of adoption, planning and execution of process A new paradigm From the successes in modern software development Unified Process Camp Process Maturity Camp Agile Methods Camp

Balancing the practitioners’ view and the process engineers’ view I need to get things done There must be uniformity and consistency Process Engineer Practitioner Making the Essential Unified Process easy to use, easy to adopt and even more effective

What is a Practice? Pragmatics • A Practice is a set of activities to give value to a particular stakeholder of a software organization • A Practice – explicit knowledge waiting to be put into action • A set of compatible process elements that can be added to a process to address a risk or extend an existing practice • A practice includes its own verification providing it with a clear beginning and an end, and allowing it to be independently applied • Our practices are supplied as a set of cards and guidelines defining a way of doing something More precisely • A use-case module in our AOSD book • It has a beginning and an end • It may be a peer practice or extend an existing practice

EssUP Practices Iteration Use Case Architecture Title Component Modeling Team Process Product The Practices in the Essential Unified Process TechnicalPractices Where is testing? It is everywhere! Social Engineering Practices Process Practices Organizational Practices

EssUP Practices Systems Engineering SOA Enterprise Architecture Product Line Eng. Business Use-Case Iteration Use Case Architecture Title Domain Modeling Robustness Analysis REUSE Model Driven Architecture Aspect Orientation Component Modeling Technical Practices Social Engineering Practices Prince2 6 Sigma Extended CMMI PSP / TSP Process Practices Team Process Product Pair Programming Portfolio Management Organizational Practices ProgramManagement Building a process eco-system around 8 Essential Practices • There will be 100s of practices extending the essentials

Title Modeling PRINCE2 Practices can be applied individually A team starting out with use cases A large formal project Use Case Existing Local Practices Iterative A small team doing maintenance Component Use Case Architecture Iterative Use Case Component Team Process Team ..or in any combination (with or without the introduction of local practices)

All within VSTS Practice Add Practice Practice Practice Instantiate only the practices you need within VSTS. Incrementally compose the process and the project schema.

Practice Browser Practice Explorer For Browsing Authoring, and Composing Practices

Today, process descriptions are designed for process engineers • Usually presented in books or web pages. • That nobody reads • Usually out-of-date • And not what’s actually done • Not accessible or easy to work with • And don’t contain the advice you need It’s a law of nature: Most people don’t read books, especially long process descriptions.

Apply card game metaphor for practice descriptions • A card contains concise description of things to produce and things to do, etc. • A practice is a set of cards • A team/individual works on a set of instance cards * Ward Cunningham invented CRC cards, published in 1989

The “Essentials” are in the cards

I do test cases Supported by simple guidelines and references Reference books RUP Knowledge Base Intelligent Agents

See the cards within VSTS Process Guidance

Using the Essential Unified Process with Visual Studio Team System