Seminar: Agile Development with Team System

1
Seminar Agile Developmentwith Team System

• Roy Osherove
• Principal, Team Agile
• www.TeamAgile.com
• Blog ISerializable.com

2
About Roy

• Consultant
• Methodology
• .NET Architecture, Design
• www.TeamAgile.com
• Team System
• Sela Group, Israel
• www.Sela.co.il
• Blogger
• www.ISerializable.com

3
Agenda
4
Attention Slides are different than print!

• Download
• http//files.osherove.com/vsts/TechEdAgileWithVSTS
  .zip
• or
• http//tinyurl.com/ymfkmx

5
Introduction to Agile Methodologies and Concepts

• Roy Osherove
• Principal, Team Agile
• www.TeamAgile.com
• Blog ISerializable.com

6
Agenda

• Defining Agile Development
• Main differences between Agile and traditional
  methodologies
• Good Agile, Bad Agile
• Agile with Team System
• Team System as softwares ERP
• Unit testing TDD
• Continuous Integration
• Scrum for Team System
• When NOT to use Team System

7
Defining Agile Development

• Better communication
• Customer, your team, other teams
• executable requirements, less unneeded
  documentation
• Deal with constant change
• Shorter iterations
• Simpler and stricter requirements management
• Have practices that help mitigate the risk of
  change
• Unit testing, continuous integration etc..
• Improve and adapt the way you work to your team
• Give value quick, by priority
• Incremental development, keep it simple
• Customer has more responsibility

8
The Agile Manifesto

• We are uncovering better ways of developing
  software by doing it and helping others do it.
  Through this work we have come to value
• Individuals and interactions over
• processes and tools
• Working software over
• comprehensive documentation
• Customer collaboration over
• contract negotiation
• Responding to change over
• following a plan
• That is, while there is value in the items on
  the right, we value the items on the left more.

9
What are we trying to solve?

• High failure rate of projects
• Time, Budget, Quality, Cancellation
• Find out about problems much earlier in the
  process
• Compensate for not predicting the future
• Will the client will change their mind?
• Do we really know how much it will cost to build?
• Did we make the design good enough?
• Did we take all the requirements?
• Will our team stay the same throughout?
• Do we understand the task fully?

10
How to predict the future
11
Simple steps to predict the future

• Will the client will change their mind?
• Only if we let them
• Do we really know how much it will cost to build?
• Lets assume we do
• Did we make the design good enough?
• Well design for as long as needed
• Did we take all the requirements?
• Well make it into a science
• Will our team stay the same throughout?
• Well make sure it wont matter
• Do we understand the task fully?
• Lets assume we do

12
The perfect prediction
13
Something is going to change
14
Agile properties

• Engineering
• Predictive
• Process-Oriented

• Agile
• Adaptive
• People-Oriented

15
Small Risk Management Techniques

• Imagine its the end of the project
• Fire the Guru?

16
A bridge apart

• Case of the perfect plan

17
Dealing with unpredictability

• Short Iterations
• Keep it simple
• A better priority mechanism
• Team based estimation

18
Some example methodologies

• XP, Scrum

19
eXtreme Programming
Scrum

• Short iterations
• Customer prioritization
• Team estimation
• Clear and simple artifacts
• Reports, documentation
• Daily meeting (Scrum)
• Adjustable process

20
Overview of Scrum
21
(No Transcript)
22
Customer Engineering activities in XP
Customer

• Writes customer Stories
• Writes customer Tests
• Runs tests at end of iteration

Developers

• Pair Programming
• Unit Testing
• Test Driven Development
• Refactoring
• Continuous Integration

23
Overview of Scrum
24
Problems with Agile

• Early adopters often encounter resistance
• Some practices seem to contradict common sense
• Some practices have a learning curve
• Best with very experienced team members
• Requires active customer participation in
  process

25
Good agile, Bad Agile
26
Famous last words

• Agile solves all our problems
• If we make them do it Agile, itll work
• Lets do it all at once
• Were doing great now Im sure this will make
  it even better

27
Hard Lessons

• Dont force it, just try to direct and give the
  tools to learn
• Not everything fits
• Adapt what you need to fit your team
• Adjust gradually
• Not a silver bullet
• But a way to find and react to things earlier
• Just a set of best practices with name

28
Bottling Agile

• Certifications

29
Agile with Team System

• Introduction to Team System
• Team System and the software Process

30
(No Transcript)
31
Expanding Visual Studio
32
Expanding Visual Studio
ERP
33
Process Templates

• Works Items
• Reports
• Roles permissions
• MSF Agile
• MSF for CMMI
• Scrum for Team System
• More

34
In short

• Agile works
• It can work with Team System
• Que Sera Sera

35
Que sera sera

• When I was just a new team lead
• One of the clients came to me
• Will we succeed?
• How much will it cost?
• Can we finish in half the time?

36
Chorus

• Yes, of course we can,
• Whatever you ask will be
• The future is known to me
• What you ask will be

37
Que sera sera

• The second week the project ran
• The client called and told me this
• I changed my mind, we need something else
• Can you change it? Youre da man.

38
Chorus

• Yes, I think we can
• If we work really hard, we will
• Well work nights, ignore the pain
• Please dont change your mind again

39

• On the 10th month the client called
• And said that hes moving the project abroad
• Were running too late
• Were doing it wrong
• It seems like this is our fate

40

• Que sera sera
• Whatever will be will be
• The projects moved overseas
• Que sera sera

41
Thank you!

• Roy_at_TeamAgile.com

42
(No Transcript)