• Save
Visual Studio 2012 Tools for Team Work - From Visual Studio 2012 Launch in Egypt
Upcoming SlideShare
Loading in...5
×
 

Visual Studio 2012 Tools for Team Work - From Visual Studio 2012 Launch in Egypt

on

  • 912 views

 

Statistics

Views

Total Views
912
Views on SlideShare
912
Embed Views
0

Actions

Likes
0
Downloads
0
Comments
0

0 Embeds 0

No embeds

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment
  • Point out the highlighted impediment: Conflicting Priorities.
  • Instructor Note:This slide introduces the first of many “Loss of focus” Barriers that are removed or minimized with Visual Studio 2012.There are many different areas in software development that can cause a loss of focus. One of the worst is context switching. Moving from one difficult problem to another, then back to the original problem, wastes time, slows development, causes frustration, and results in lost productivity. Developers want focus. And they want to work on high priority tasks until they are complete. In Visual Studio 2012, the Team Explorer has been redesigned to help keep developers in the zone, and removes unnecessary details until they are required. Especially critical for maintaining focus and minimizing the pain of context switching is the newly added “My Work” feature.
  • Instructor Note:Do demo.
  • Point out the highlighted impediment: Conflicting Priorities.
  • Instructor Note: Developers don’t always work with backlog prioritization, but they are all impacted by it. Use a story from your own past to link the churn in requirements to pain felt by you or your team.Rapidly changing requirements, or shifts in priority, can result in confusion, partially complete work, context switching, and a whole lot of dissatisfaction, both from the developer and the customer.Visual Studio 2012 provides easy to use, graphical backlog and task management tools to make work visible, and ensure clear prioritization. Backlog management tools ensure that requirements are prioritized, and any changes to stakeholder priorities are immediately available to the entire team. At the developer level, a new task board visually displays current team efforts, priorities and status. These tools, common in agile development practices, are non-dogmatic and allow you to adopt agile at your own pace, or simply improve your current methodology.
  • Instructor Note:Do demo.
  • Point out the highlighted impediment: Loss of Focus.
  • Instructor Note:This slide introduces the first of many “Loss of focus” Barriers that are removed or minimized with Visual Studio 2012.There are many different areas in software development that can cause a loss of focus. One of the worst is context switching. Moving from one difficult problem to another, then back to the original problem, wastes time, slows development, causes frustration, and results in lost productivity. Developers want focus. And they want to work on high priority tasks until they are complete. In Visual Studio 2012, the Team Explorer has been redesigned to help keep developers in the zone, and removes unnecessary details until they are required. Especially critical for maintaining focus and minimizing the pain of context switching is the newly added “My Work” feature.
  • Instructor Note:It’s a little bit of a stretch to drop this into Loss of Focus, but it’s the only impediment that relates, even if weakly. Go with the Loss of Focus that results when you have to use external tools to do a code review, or the frustration from the built in diff/merge tools in earlier versions of Visual Studio.Another thing that can cause loss of focus is slow validation of complex code changes. One of the most powerful techniques for improving code quality is a solid code review process, yet few teams regularly use code reviews. Those that do often don’t complete code reviews rapidly, leaving new code to be written on top of buggy code that could have been identified early with a simple code review. Visual Studio 2012 introduces an integrated code review process that creates a work queue for the reviewer, tracks comments at the overall, file and line levels, is fully traceable, and supports email notifications.Another welcome improvement is a new code comparison, or diff/merge, tool that is baked into the new version. It merges a powerful differencing engine with intelligent merge capabilities that result in a tool that’s a pleasure to use. It even allows for rollback and baseless merges to occur directly from the user interface!
  • Instructor Note:Do demo.

Visual Studio 2012 Tools for Team Work - From Visual Studio 2012 Launch in Egypt Visual Studio 2012 Tools for Team Work - From Visual Studio 2012 Launch in Egypt Presentation Transcript

  • Tools forTeamworkAyman El-HattabSharePoint MVP
  • About Me www.AymanElHattab.com fb.com/AymanElHattab Twitter.com/AymanElHattab Eg.linkedin.com/in/ayman elhattab
  • Barriers to Continuous Value Delivery REQUIREMENTS Misunderstood requirements Can’t get actionable feedback Conflicting priorities New learnings Production incidents Loss of focus Integrating heterogeneous development teams Quality after thought: Unmet user dev and test hand-offs expectations Disparate management tools Operations readiness WORKING SOFTWARE requirements are not met
  • ProblemSolutionSolution
  • Demo:Building the RightSoftware
  • Barriers to Continuous Value Delivery REQUIREMENTS Misunderstood requirements Can’t get actionable feedback Conflicting priorities New learnings Production incidents Loss of focus Integrating heterogeneous development teams Quality after thought: Unmet user dev and test hand-offs expectations Disparate management tools Operations readiness WORKING SOFTWARE requirements are not met
  • ProblemSolution
  • Demo:Backlogs & TaskBoard
  • Barriers to Continuous Value Delivery REQUIREMENTS Misunderstood requirements Can’t get actionable feedback Conflicting priorities New learnings Production incidents Loss of focus Integrating heterogeneous development teams Quality after thought: Unmet user dev and test hand-offs expectations Disparate management tools Operations readiness WORKING SOFTWARE requirements are not met
  • ProblemSolutionSolution
  • ProblemSolutionSolution
  • Demo:Team Explorer &My Work
  • MEA ALM Community www.meaalmcommunity.com www.handsonvisualstudio.com
  • MEA ALM Community tfs2012visualguide.codeplex.co youtube.com/msmeaalmcommu m nity
  • © 2012 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on thepart of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.