ALM@Work - Typical developer day

359 views

Published on

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

Published in: Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
359
On SlideShare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
2
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

ALM@Work - Typical developer day

  1. 1. Typical developer day Ricci Gian Maria http://blogs.ugidotnet.org/rgm http://www.codewrecks.com alkampfer@nablasoft.com @alkampfer …
  2. 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. 3. New Team explorerTask based • My Work • Pending Changes • Work Items • ...Make developers concentrate on «what todo»More coincise and «browse-like» useMore functionality (Es. search WI)
  4. 4. My WorkNew First Level menu of Team ExplorerVisualize the task that are associated to theuser • In progress work • Suspended Work • Available Work Items • Code Reviews
  5. 5. An intro to planningEach 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 typePlanning is a vital part of a developers life,to avoid “what should I do next” syndrome
  6. 6. Available Work ItemsIt is the easiest way to visualize a list of taskavailable to current userIs a simple shortcut to a series of defaultqueryYou can personalize a query and save intoMy Query to change the logic behindIs the starting point of your work
  7. 7. In Progress WorkSummarize 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 ofwork” Mitigate “context switch” Manage interruptions
  8. 8. Interruption of worksCaused usually by “more priority task to doin the middle of the current task” Hotfix bug in production Hotfix bug in dev because the team is blocked Broken build Change of priorityThis is usually associated to a cost for“context switching”Welcome “suspend work” in VS2012
  9. 9. Code review and feedbackAsk for work review by other member of theteam Not familiar with the project / area Code is complex ex. Heavy multithreading Unsure of somethingFeedback by the users New feedback tool Integrated in TFS
  10. 10. Use Branch to organize code linesA single line of code is dangerousBranch can save your time Branch for production code Branch for long and complex feature to addAvoid “fear of the merge”
  11. 11. Use Branch to organize code lines
  12. 12. Intellitrace ™Known as historical debuggerIntroduced in VS2010With VS2012 is available to use inproduction PowerShell based integration Simple to use by IT team Seamless start-stop trace on production server
  13. 13. Preemptive integrationInstrument assembly to automatically send“incident” on exceptionIntegrated on TFS-Visual Studio Incident collector provide the bridge with TFS Generates Work Items on incident Dedicated section of Team ExplorerGreatly reduced time-to-supportMakes user happier
  14. 14. Extend VS with pluginIn VS2012 macro support was removedYou can automate everyday task withplugins Install VS2012 sdk Create a new plugin projectSuggestions Use VS2010 macro recorder to understand API to use Try the SDK samples (http://tinyurl.com/VSSDKSamples) MSDN: http://tinyurl.com/VSSDKMsdn
  15. 15. Grazie agli sponsor

×