Alm In Vs2010


Published on

Published in: Business
  • Be the first to comment

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide
  • In WikiPediaApplication lifecycle management (ALM) is the marriage of business management to software engineering made possible by tools that facilitate and integrate requirements management, architecture, coding, testing, tracking, and release management.[1]
  • REFERENCE: Pic is from[AN]ALM is about how we develop software as a whole from gathering requirements to shipping and maintaining software and everything in between[AN]We can walk here by talking about SDLC and then show ALM as it begins from request then planning then SDLC and managing SDLC then maintaining and finally the retirement of the project/product (no more work nor maintaining) and at last ALM has oversight on all of this ALM is more about managing the final product and all that goes into building itIt is broader than SDLCSDLC is about the core activitiesALM is the core activities with everything around them, it can include marketing, selling and the feedback loop from the customer.SDLC is more focused on what we do to get the product developedALM is focused on measuring the activities and managing how they relate together, it even intersect with SDLC but is not a clear cut concept
  • This slide is available as a comparison if you want to compare/contrast with the 2010 slide.It’s also nice to be able to tell the VSTS 2008 story before diving into what’s new in 2010.[Taken from Brian Keller Presentation in Teched Brazil]
  • This and the next 3 slides - REFERENCE Brian Harry’s Presentation in Teched
  • TraceabilityWhat happens when everyone leaves the company? Where does the project go?
  • Lab ManagementTeam Test Essentials[Taken from Brian Keller Presentation in Teched Brazil]CMMi L3 + TraceabilityProject history + estimate accuracyWhat happens when everyone leaves the company? Where does the project go?
  • REFERENCE Brian Harry’s Presentation in Teched
  • REFERENCE Brian Harry’s Presentation in Teched
  • REFERENCE Brian Harry’s Presentation in Teched
  • Alm In Vs2010

    1. 1. Application Lifecycle management with TFS<br />By Ahmed Nasr<br />Mohamed R. Samy<br />1<br />
    2. 2. Agenda<br />Application life cycle management definitions <br />ALM vs. SDLC<br />VSTS support for ALM<br />Planning in TFS (DEMO)<br />Work Item Hierarchy<br />Architecture (Demo)<br />Testing (Demo)<br />Q & A<br />2<br />
    3. 3. ALM Definitions<br />ALM is the management of the lifecycle of the application  (Mohamed R. Samy)<br />(ALM) addresses all phases of the creation of a new system from inception to retirement  (Ahmed Nasr)<br />ALM is there to help us achieve project governance (What is governance? )<br />
    4. 4. ALM vs. SDLC<br />Big words…..<br />SDLC as a subset of ALM<br />Managing the software dev. process vs. the application lifecycle<br />
    5. 5. Visual studio Team System 2008<br />5<br />
    6. 6. Visual Studio Team System 2010<br />6<br />
    7. 7. Demo <br />Planning with TFS 2010<br />
    8. 8. 8<br />TrackingProgress<br />
    9. 9. 9<br />TrackingProgress<br />Detailed sprint progress is tracked on the project portal<br />The burndown shows the team on track…<br />And almost half of the tasks remain open<br />But the team hasn’t closed any of the three stories…<br />
    10. 10. 10<br />TrackingProgress<br />The Scrummaster opens an issue to track the problem the portal has identified<br />
    11. 11. 11<br />TrackingProgress<br />The issue is opened and tracked in TFS<br />
    12. 12. 12<br />Work Item Hierarchy (Links)<br />Network<br />Directed Network<br />Dependency<br />Tree<br />
    13. 13. 13<br />Traceability for MSF Agile 5.0<br />User Story<br />Tests/Tested By<br />Parent/Child<br />Related<br />Test<br />Bug<br />Task<br />Change Sets<br />Code Coverage<br />Change Sets<br />Code<br />
    14. 14. 14<br />Traceability for MSF CMMI 5.0<br />Change Request<br />Affects/ Affected By<br />User Story<br />Requirement<br />Tests/Tested By<br />Parent/Child<br />Related<br />Predecessor/<br />Successor<br />Test<br />Bug<br />Task<br />Change Sets<br />Code Coverage<br />Change Sets<br />Code<br />
    15. 15. ALM in VSTS 2010<br />Traceability<br />15<br /><ul><li>Top-to-Bottom Traceability
    16. 16. Requirements Traceability
    17. 17. Parent/Child Relationships
    18. 18. Rollup and Drilldown
    19. 19. Agile Planning
    20. 20. Built-in product backlog mgmt
    21. 21. Built-in iteration planning
    22. 22. Easily customizable
    23. 23. Great Project Integration
    24. 24. Full dependency linking
    25. 25. Full round-tripping w/ TFS</li></li></ul><li>16<br />Release<br />Cost of Bugs<br />Test<br />Development<br />Software Phase<br />
    26. 26. 17<br />Tester Segmentation<br />70% of testing happens here<br />majority of test tools target here<br />Black Box Testing<br />White Box Testing<br />API Testing<br />
    27. 27. 18<br />What usually happens when a tester<br /> finds a bug?<br />Graphic by Jeff Atwood (<br />
    28. 28. Testing Demo<br />19<br />
    29. 29. Q& A<br />