Slide della sessione "Typical developer day" tenuta da Gian Maria Ricci durante l'evento "ALM@Work" di DomusDotNet del 28/09/2012

1. Typical developer day
Ricci Gian Maria
http://blogs.ugidotnet.org/rgm
http://www.codewrecks.com
alkampfer@nablasoft.com
@alkampfer
…

2. Agenda
• The new team explorer and IDE
• Plan and activate your task
• How to manage interruptions of work
• Code Review / Gather feedback
• Cure the health of the build
• Use branching to do complex-work
• Intellitrace to the max in production environments
• Preemptive integration with TFS
• Extend your VS.

3. New Team explorer
Task based
• My Work
• Pending Changes
• Work Items
• ...
Make developers concentrate on «what to
do»
More coincise and «browse-like» use
More functionality (Es. search WI)

4. My Work
New First Level menu of Team Explorer
Visualize the task that are associated to the
user
• In progress work
• Suspended Work
• Available Work Items
• Code Reviews

5. An intro to planning
Each ALM process has the concept of
“planning”
Usually planning phase is used to
Decide user story for the next iteration
Decompose user stories in task
Assign tasks to people or resource type
Planning is a vital part of a developers life,
to avoid “what should I do next” syndrome

6. Available Work Items
It is the easiest way to visualize a list of task
available to current user
Is a simple shortcut to a series of default
query
You can personalize a query and save into
My Query to change the logic behind
Is the starting point of your work

7. In Progress Work
Summarize the “stuff” you are working with
Work Items active
Source Control Pending changes.
Inform the team on “who is working with”
Supports the concept of “suspension of
work”
Mitigate “context switch”
Manage interruptions

8. Interruption of works
Caused usually by “more priority task to do
in the middle of the current task”
Hotfix bug in production
Hotfix bug in dev because the team is blocked
Broken build
Change of priority
This is usually associated to a cost for
“context switching”
Welcome “suspend work” in VS2012

9. Code review and feedback
Ask for work review by other member of the
team
Not familiar with the project / area
Code is complex ex. Heavy multithreading
Unsure of something
Feedback by the users
New feedback tool
Integrated in TFS

10. Use Branch to organize code lines
A single line of code is dangerous
Branch can save your time
Branch for production code
Branch for long and complex feature to add
Avoid “fear of the merge”

11. Use Branch to organize code lines

12. Intellitrace ™
Known as historical debugger
Introduced in VS2010
With VS2012 is available to use in
production
PowerShell based integration
Simple to use by IT team
Seamless start-stop trace on production server

13. Preemptive integration
Instrument assembly to automatically send
“incident” on exception
Integrated on TFS-Visual Studio
Incident collector provide the bridge with TFS
Generates Work Items on incident
Dedicated section of Team Explorer
Greatly reduced time-to-support
Makes user happier

14. Extend VS with plugin
In VS2012 macro support was removed
You can automate everyday task with
plugins
Install VS2012 sdk
Create a new plugin project
Suggestions
Use VS2010 macro recorder to understand API
to use
Try the SDK samples (http://tinyurl.com/VSSDKSamples)
MSDN: http://tinyurl.com/VSSDKMsdn

15. Grazie agli sponsor