Upload
eddie-weatherley
View
230
Download
2
Embed Size (px)
Citation preview
AGILCOM
Architecture
Conseil
Formatio
n
ASP.NET AjaxC#VSTSVB.NETSQL Server
Les coachAVANT APRES
AgendaPourquoi une méthode Agile ?Quelles nouveautés dans la version 2010 de la plateforme ALM Microsoft ?
AGILE vs Traditional Approach
Conceptual Level
Logical Level
Physical Level
What
How
Using
Traditional Approach
AGILE
Identifying and Creating Personas
Personification of user groups Represented as an individualPersonification of user groups Represented as an individual
Good personas are memorable and three dimensionalGood 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 makingPersona should be useful for decision making
Personas should have a memorable namePersonas should have a memorable name
Persona BenefitsPersona 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
Techniques for Capturing User Stories
PersonaPersona
Practices for Capturing User StoriesPractices 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 goalSteps for persona to accomplish goal
User storiesUser stories
GoalGoal
Visual Studio Team System 2008
Visual Studio Team System 2010
Project TransparencyEffectively plan and deliver the right software
CollaborationSoftware quality
Build applications that really workHigh level of quality (QA and QC)
Deliver what customers ask for !
Visual Studio Team System 2010 Pillars
New FeaturesNo More Planning Black BoxNo More Late SurprisesNo More Parallel Development PainNo More Bewildering AdminNo More No ReproNo More Build BreaksNo More Butterfly Effects or Legacy FearNo More UI RegressionsNo More Missed Requirements or ChangesNo More Waiting for Build SetupNo More Performance Regressions
No More Planning Black Box
Top-to-Bottom TraceabilityRequirements TraceabilityParent/Child RelationshipsRollup and Drilldown
Agile PlanningBuilt-in product backlog mgmtBuilt-in iteration planningEasily customizable
Great Project IntegrationFull dependency linking Full round-tripping w/ TFS
Demo
Planning
No More Late Surprises
Reporting for mere mortalsGenerate reports from queriesManipulate data with ExcelFriendlier OLAP cube
Share the knowledgeEmbed reports via MOSS
No More Parallel Development Pain
First class branchesServer-side branch creationVisualize branch relationshipsTrack change across branches
HistoryTimelineRicher Annotate
Conflict resolution
Visual Studio TFS Branching Guide 2010http://tfsbranchingguideiii.codeplex.com/
Demo
Branching
No More Bewildering Admin
MMC-based adminUI for common tasks
Change service accountsConfigure data tierConfigure SSLAdd /change SharePointConfigure reporting/analysis servicesConfigure Team System Web AccessManage project collections
Access log files
Demo
Admin site
No more butterfly effectGenerate Graph Documents to explore the relationships and organization :
Graphs are generated By Assembly, by Namespace or By ClassCan be navigated to visualize dependenciesPartial graphs can be created by using Architecture ExplorerLayer Diagrams show organization and constraints
UML DiagramsHelps you to modelize User RequirementsUse case diagram
Who uses the system and what they do with it
Conceptual class diagramGlossary of types that are used to describe the requirements; the types visible at the system's interface.
Activity diagramFlow of work and information between activities performed by users and system or its parts.
Sequence diagramSequence of interactions between users and system or its parts. An alternative view to the activity diagram.
Component Diagramshow the major parts of the system
Demo
Dependency Graph
No More ‘Repro’
The actionable bugSteps to reproduceSystem informationScreen shotsFull screen video, indexedTrace debug logTest environment
No more UI regressions or missed requirementsCreate 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 FormsWindows Presentation Foundation
Demo
Test Manager 2010UI Test
No more Build Breaks
Test Impact AnalysisWorks with Code Coverage data in TFS.Compares code changes with coverage data.Recommends tests to run based on coverage impacted.
Gated check-inChecks changes into a shelfset on server.Merges changes with main and runs build.If successful, commits changes to main.
Lab ManagementMaintains groups of Virtual machines for TestingRapidly provisions Virtual MachinesCan be copied, check pointed, sharedDeveloper has access to tester’s environmentNetwork fencing enables you to run a copy of the
environment
Conclusion
Thank you for your Attention!For more Information please contact
Christine DUBOISConsultant Trainer Dynamics & .NET
[email protected] Tel : +33 (0)4 50 10 49 70Mobile : +33 (0)6 08 02 99 11http://blogs.developpeur.org/cdubois
Bernard FedotoffArchitecte, Consultant ALM
[email protected] Tel : +33 (0)4 50 10 49 70Mobile : +33 (0)6 12 54 93 12http://blogs.developpeur.org/bfedotoff
http://www.agilcom.ch 10 route de NanfrayPAE du Levray74960 CRAN-GEVRIERFRANCE