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

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

Essential Unified Process – Key characteristics Free Open Source Adaptive Easy to Use Agile Lightweight Universal Extensible Scalable Complete Sufficient Comprehensive Recursive 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 Iterative Component Architecture Use Case 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.

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

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

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

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

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 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

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

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

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

All within VSTS Practice Add 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

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

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

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

See the cards within VSTS Process Guidance