1. Christine DUBOIS AGILCOM duboisc@hotmail.fr

3. ASP.NET Ajax C# VSTS VB.NET SQL Server AVANTAPRES

4. Pourquoi une méthode Agile ? Quelles nouveautés dans la version 2010 de la plateforme ALM Microsoft ?

5. Conceptual Level Logical Level Physical Level What How Using Traditional Approach AGILE

6. Personification of user groups Represented as an individual Personification of user groups Represented as an individual Good personas are memorable and three dimensional Good personas are memorable and three dimensional Personas consider personality, work environment and characteristics Personas consider personality, work environment and characteristics Persona should be useful for decision making Persona should be useful for decision making Personas should have a memorable name Personas should have a memorable name Persona Benefits They separate “you” from your application’s customers By making them “real” they are easier to discuss They are more specific than RUP actors e.g. several personas for different demographics They help with role play activities They separate “you” from your application’s customers By making them “real” they are easier to discuss They are more specific than RUP actors e.g. several personas for different demographics They help with role play activities

7. Persona Practices for Capturing User Stories Start with the goal Break the goal into a list of steps Start with “Persona does step” Then “Solution shows result” Use action verbs to enumerate steps Write scenarios in the user’s language Don’t detail alternate and exception paths initially Start with the goal Break the goal into a list of steps Start with “Persona does step” Then “Solution shows result” Use action verbs to enumerate steps Write scenarios in the user’s language Don’t detail alternate and exception paths initially Steps for persona to accomplish goal Steps for persona to accomplish goal User stories Goal

10. Project Transparency Effectively plan and deliver the right software Collaboration Software quality Build applications that really work High level of quality (QA and QC) Deliver what customers ask for !

11. No More Planning Black Box No More Late Surprises No More Parallel Development Pain No More Bewildering Admin No More No Repro No More Build Breaks No More Butterfly Effects or Legacy Fear No More UI Regressions No More Missed Requirements or Changes No More Waiting for Build Setup No More Performance Regressions

12. Top-to-Bottom Traceability Requirements Traceability Parent/Child Relationships Rollup and Drilldown Agile Planning Built-in product backlog mgmt Built-in iteration planning Easily customizable Great Project Integration Full dependency linking Full round-tripping w/ TFS

13. Planning

14. Reporting for mere mortals Generate reports from queries Manipulate data with Excel Friendlier OLAP cube Share the knowledge Embed reports via MOSS

15. First class branches Server-side branch creation Visualize branch relationships Track change across branches History Timeline Richer Annotate Conflict resolution Visual Studio TFS Branching Guide 2010 http://tfsbranchingguideiii.codeplex.com/

16. Branching

17. MMC-based admin UI for common tasks Change service accounts Configure data tier Configure SSL Add /change SharePoint Configure reporting/analysis services Configure Team System Web Access Manage project collections Access log files

18. Admin site

19. Generate Graph Documents to explore the relationships and organization : Graphs are generated By Assembly, by Namespace or By Class Can be navigated to visualize dependencies Partial graphs can be created by using Architecture Explorer Layer Diagrams show organization and constraints

20. Helps you to modelize User Requirements Use case diagram Who uses the system and what they do with it Conceptual class diagram Glossary of types that are used to describe the requirements; the types visible at the system's interface. Activity diagram Flow of work and information between activities performed by users and system or its parts. Sequence diagram Sequence of interactions between users and system or its parts. An alternative view to the activity diagram. Component Diagram show the major parts of the system

21. Dependency Graph

22. The actionable bug Steps to reproduce System information Screen shots Full screen video, indexed Trace debug log Test environment

23. Create tighter Dev/Test interaction Code UI Test is a new test type. Enables creating UI test automation. Supports: Web UI (IE & FF Beta Support) Windows Forms Windows Presentation Foundation

24. Test Manager 2010 UI Test

25. Test Impact Analysis Works with Code Coverage data in TFS. Compares code changes with coverage data. Recommends tests to run based on coverage impacted. Gated check-in Checks changes into a shelfset on server. Merges changes with main and runs build. If successful, commits changes to main.

26. Maintains groups of Virtual machines for Testing Rapidly provisions Virtual Machines Can be copied, check pointed, shared Developer has access to tester’s environment Network fencing enables you to run a copy of the environment

28. For more Information please contact Christine DUBOIS Consultant Trainer Dynamics &.NET duboisc@hotmail.fr Tel : +33 (0)4 50 10 49 70 Mobile: +33 (0)6 08 02 99 11 http://blogs.developpeur.org/cdubois Bernard Fedotoff Architecte, Consultant ALM bfedotoff@hotmail.com Tel : +33 (0)4 50 10 49 70 Mobile: +33 (0)6 12 54 93 12 http://blogs.developpeur.org/bfedotoff http://www.agilcom.ch 10 route de Nanfray PAE du Levray 74960 CRAN-GEVRIER FRANCE