1 / 63

Using Visual Studio 2010 Application Lifecycle Management to Differentiate and Grow Your Business

SD02. Ro Kolakowski Company Partner 6 th Street Consulting MPN partner since 2006 SharePoint. Using Visual Studio 2010 Application Lifecycle Management to Differentiate and Grow Your Business. Matt Nunn Sr. Product Manager Microsoft Corporation. Lisa Slim

lotta
Download Presentation

Using Visual Studio 2010 Application Lifecycle Management to Differentiate and Grow Your Business

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. SD02 Ro Kolakowski Company Partner 6th Street Consulting MPN partner since 2006 SharePoint Using Visual Studio 2010 Application Lifecycle Management to Differentiate and Grow Your Business Matt Nunn Sr. Product Manager Microsoft Corporation Lisa Slim Microsoft Alliance Business Manager Hewlett-Packard MPN partner since 1989 HP Enterprise Business

  2. “The best way to predict your future is to create it.” - Abraham Lincoln

  3. The Art of The Possible

  4. The First Mover Advantage First firm in an industry implements innovation The Art of The Possible Second firm in the industry implements innovation Competitive Advantage Third firm in the industry implements innovation Time

  5. The First Mover Advantage First firm in an industry implements innovation Transformative IT The Art of The Possible Second firm in the industry implements innovation This is where you change the world Competitive Advantage Third firm in the industry implements innovation Time

  6. Value Differentiation = Competitive Advantage • New Ways of Conducting Business • Faster, more Streamlined Organizations • Reduced Cost, Increased Return • Improved Customer Service, Higher Satisfaction

  7. Risk Differentiation = Custom Software • Complex or Unique! • Hasn’t Been Done Before • Or is too complex to Buy • Do you know Exactly What you Need?

  8. Agenda • De-risking Software Development • Start at the Beginning (or is it the end?) • Brown Field v Green Field • Delivering Quality Results • When Am I Ready To Ship? • The Future of Microsoft ALM • Call To Action

  9. De Risking Software Development What are Your Biggest Risks in Developing Software “Working with Existing Code?” “Management Oversight/Undersight?” Working with Existing Code? Estimation or Scheduling? “Constant Change?” “Knowing when to ship” Lack of Documentation? Poor Quality? “Poor Quality” “Process Problems” “Lack of Documentation” Management Oversight/Undersight? Constant Change? “Estimation/Scheduling” Process Problems? Knowing When to Ship?

  10. Poll What Type of Partner are You? ISV? SI? ALM?

  11. Start At the Beginning Choosing your Process, Estimating and Planning

  12. “Insanity: doing the same thing over and over again and expecting different results.” - Albert Einstein

  13. The Rise Of Agile

  14. By 2012, agile development methods will be utilized in80% of all software development projects. 80% (Gartner Predicts 2010: Agile and Cloud Impact Application Development Directions, Gartner, Dec 2009)

  15. Agile processes have rapidly joined the mainstream of development approaches… …It’s time for software development professionals to stop sitting on the fence where Agile is concerned…  “…The benefits are well worth the effort” (Agile Development: Mainstream Adoption Has Changed Agility, Forrester, Feb 2010)

  16. Continuous Improvement • Agile Techniques allow you to Continuously Improve • But… you must listen and adjust • Use TFS Data • Track sprints to understand what is working and what isn’t • Adjust your team process • Amplify the good, Remove the bad

  17. Planning and Estimation • Use Historical Data from TFS • Accurately Estimate Future Team Performance • Utilize Agile Techniques • like Planning Poker to get a team consensus • Balance team estimate with historical trends • Portfolio Integration • Understand the Broader Scope • Prioritize work appropriately for the good of the whole business

  18. Demo Project Server Integration Brian Randell MCW Technologies

  19. Brown Field v Green Field Architectural Discovery and Documentation

  20. Understanding Your Systems • Most work is Brown Field • So if its not yours or even if it has just been a while, how do you get started? • 2 Key Scenarios • Understanding existing infrastructure • Where did the specs go? • Architectural Discovery • Onboarding new team members • Self Generated Diagrams

  21. demo Gaining Enlightenement Brian Randell MCW Technologies

  22. Living Documentation • When you find a Green Field!! • Avoid the issues of no documentation • UML Diagrams are stored alongside your project in TFS • Requirements/Users stories are work items • Traceable • Reportable • Use them to help those that come next to understand what was built

  23. Delivering Quality Results Quality is about the team but also about the team support

  24. Quality is Everyone’s Responsibility • Quality Starts with every team member • Business Analysts are responsible for Quality Requirements • Build the Right Thing • Developers are responsible for Producing Quality Code • Metrics • Code Coverage • Test First Development • F5 IntelliTrace™ • QA is responsible for Assuring Quality • Find Edge Cases

  25. Lock in Quality • Take steps to Protect Qualityearly on • Check Points • Validation • Visual Studio and TFS Can Help • Layer Diagram Validation • Code Metrics • Gated Check-ins • No more broken builds!! • Versioning in an App World

  26. When Bugs Slip Through • Streamline Dev-QA Interaction • Reduce waste in communication between the Development and QA teams • Eliminate the No-Repro scenario with rich actionable bugs

  27. Load Testing • Load Testing is vital to ensure a quality experience for All Users • Creating Load Tests is a specialized role • Normally in QA • Running Load tests can be done by everyone • Performance and Load issues are Quality Issues • Developers should run load tests regularly to check their code • Make running Load Tests a part of your developers responsibility • Visual Studio Ultimate introduces unlimited load testing for all users • Making it easier to include them as part of your standard test infrastructure

  28. Virtual Labs • Test environments can be hard and expensive to maintain • And, Test Environments are not just for QA • Virtualization Reduces the Need for Expensive Hardware Infrastructure • Lab Management makes it easy to manage all your Virtualized Lab Environments • Visual Studio Ultimate and Test Professional provide access for all to Lab Management

  29. demo Lab Management Brian Randell MCW Technologies

  30. When am I Ready to Ship When are we Done…

  31. When am I Ready to Ship? Getting to “Done Done” • Customer and Internal Reports Let you view and share progress • Track work to completion • Understand what cuts to make depending upon the needs of the project • Combined Data gives accurate information to base decisions on

  32. Quality Dashboard Are the tests covering the code on builds? Are build failures blocking progress? Do the “fixes” actually fix the bugs? Are we making progress on running test plans? How quickly are we fixing bugs? How fast is code changing?

  33. The Future of Microsoft ALM

  34. Our Vision, To Improve the productivity and predictability of software construction for teams of all sizes

  35. Visual Studio vNext ALM – Continuous Feedback Developer <-> Stakeholder Development <-> Operations

  36. What Matters – Creating Value Product Backlog OPERATE DEVELOP Requirements MisunderstoodRequirements ConflictingPriorities Sprint Monitor LosingFocus Ops Backlog Working Software

  37. Product Backlog OPERATE DEVELOP Requirements Managing the Backlog Sprint Monitor Ops Backlog Working Software Working Software

  38. Product Backlog OPERATE DEVELOP Requirements Managing the Backlog Lightweight Requirements Sprint Monitor Ops Backlog Working Software Working Software

  39. Product Backlog OPERATE DEVELOP Requirements Lightweight Requirements Sprint Monitor Sprint Planning & Tasks Ops Backlog Working Software Working Software

  40. Product Backlog OPERATE DEVELOP Requirements Sprint Monitor Sprint Planning & Tasks Getting Feedback Ops Backlog Working Software Working Software

  41. What Matters – Creating Value Product Backlog OPERATE DEVELOP Requirements Managing the Backlog Lightweight Requirements Sprint Monitor Sprint Planning & Tasks Getting Feedback Ops Backlog Working Software Working Software

  42. What Matters – Creating Value Product Backlog OPERATE DEVELOP Requirements Idea to working software Incident to Resolution Can’t Get ActionableFeedback Can’t Identify Root Cause Can’t Reproduce Production Incident Sprint Monitor Ops Backlog Working Software

  43. demo Integrated Operations Brian Randell MCW Technologies

  44. What Matters – Creating Value Product Backlog OPERATE DEVELOP Requirements Can’t Get ActionableFeedback Idea to working software Incident to Resolution Can’t Identify Root Cause Can’t Reproduce Production Incident Quickly Triage Incident Actionable Feedback Sprint Monitor Connected Team Ops Backlog Ops Backlog Working Software

  45. Our Guiding Principles for ALM Collaboration Actionable feedback Respect your work styles Transparent agile processes

  46. To The Cloud

More Related