How Microsoft ALM Tools Can Improve Your Bottom Line


Published on

Improved efficiencies, enhanced productivity, reduction of wasted time and effort, and improved team collaboration. Each of these benefits that result from adopting a successful ALM strategy will all help your bottom line. Come find out how at this free webinar!

  • Be the first to comment

How Microsoft ALM Tools Can Improve Your Bottom Line

  1. 1. How Microsofts ALM ToolsCan Improve Your Bottom Line Imaginet Resources Corp. Imaginet and ALM – Efficiently Build Better Software
  2. 2. Agenda Application Lifecycle and ALM ALM Opportunities The Bottom Line Conclusion
  3. 3. Is ALM the same as SDLC?What is a “Software Development Lifecycle?”But an application lives before an after the development efforts…And what about the term “cycle”? Ideas Projects Require- Design Code Test Deploy ments Operate Retire
  4. 4. And What is Application Lifecycle Management?References:-
  5. 5. Application Lifecycle Management includes…• Tools and practices working together• Standards across teams and disciplines• Support for best practices in all disciplines• A consolidated repository for all disciplines• Automated data collection to that repository• Visibility into all of your application development teams and projects• The ability to support heterogeneous technologies• Streamlined communications between roles
  6. 6. Agenda Application Lifecycle and ALM ALM Opportunities The Bottom Line Conclusion
  7. 7. ALM and the Bottom Line• Does application development impact your bottom line?• Can ALM improve your application development? Your bottom line?• What is your process? Do you have any opportunities to improve your process?• ALM supports the continuous improvement of your tools, processes and your bottom line.
  8. 8. Scenario #1: Multiple Systems of Record• Quality assurance and development track requirements in different systems• QA maintains a requirements list in one tool for test traceability• Dev maintains a separate list for implementation• Problems: – Redundant data entry wastes time – Time spent trying to keep different systems in sync as requirements evolve – Potential data entry errors cause different groups to interpret requirements differently – Excessive licensing, training and maintenance required to maintain multiple systems – Disparate systems of record cause distrust and angst between groups
  9. 9. Scenario #2: Status Reporting• Executive management or your PMO requires consistent status reporting between teams• Team members must dedicate time gathering, collating and formatting data from multiple systems• Problems: – Significant manual effort required to generate reports – Error prone; may render erroneous results – Different groups using different tools force-fit their data into the standard reports (resulting in bad data) – Decision makers use misleading or erroneous reports to make (potentially bad) business decisions
  10. 10. Scenario 3: Misunderstood Requirements• Requirements do not adequately describe the business needs• Developers interpret requirements as written• Resulting code does not meet actual needs• Problem: – Delivered code does not meet actual needs, leading to inadequate software and rework – Inadequate software does not meet the business needs and may actually be detrimental, costing the business – Software rework costs time and money – Time spent fixing existing code reduces time available to meet new business needs – Misunderstood requirements are not frequently found quickly, meaning they are embedded deeply in the code and more difficult to repair
  11. 11. Scenario #4: Lost Work• Developers update code and accidentally overwrite each other‟s updates• Hardware failures, illness or vacations make needed changes from a developer unavailable• New code which is incorrect replaces functional code and the original code is lost• Developers supporting multiple environments or releases accidentally confuse the separate code bases and overwrite valid code for that environment or release• Problems: – Lost work needs to be recreated, costing time and effort – Lost work may not be caught causing problems in production code – Incorrect code can cause a whole team to work on and build upon the wrong codebase, further hampering team productivity
  12. 12. Scenario #4: Bad Code Committed to Version Control• Developer modifies code but the resulting cod doesn‟t compile, doesn‟t pass tests, or otherwise „breaks‟ the existing code base.• Modified code does not follow standards or best practices expected by the team as a whole.• Problems: – Bad code reduces productivity for the rest of the team; other developers pull down the bad code and are unproductive while they try to fix their own environment – Difficult to ensure code is maintainable; more likely to build systems that have high technical debt increasing ongoing costs
  13. 13. Scenario #5: It works on my box• Problems are found in production or test environments• Developers have minimal information to understand or reproduce the issues• Developers are unable to reproduce the problems in the development environment• Problems: – Problems are ignored or closed and reopened causing excess churn and frustration – Excessive time is spent by development, test, and/or operations trying to troubleshoot the problem – Production systems are unavailable or otherwise blocked due to the problem while troubleshooting occurs
  14. 14. Scenario #6: Quality as an Afterthought• Quality is considered something that the testers are in charge of rather than an integral part of development• Time constraints force the team to take shortcuts that hurt quality• Customers are considered a viable form of quality assurance• Code bases have large technical debt making them hard to maintain• Problems: – Lack of quality throughout the software lifecycle leads to buggy, unmaintainable code – Bugs are far more difficult and expensive to fix as they move farther into the lifecycle – Code which is already difficult to maintain tends to easily breed more bugs as it evolves
  15. 15. Scenario #7: Broken Deployments• Build/compilation processes are frequently manual• Deployment processes are manual and require one or more people to copy files, run scripts, configure systems and perform installations• Deployments frequently need “all hands on deck” to ensure a successful deployment• Deployments typically take longer than it seems should be needed• Deployment-related problems are typically found after the deployment is complete• Problems: – Time wasted fighting with the deployment processes – Excessive system down time due to long deploy cycles – Late nights and long hours
  16. 16. Scenario #8: Haphazard Vendor Management• Remote vendor development team develops software based on your requirements• Development is done „black box‟ with minimal visibility into the vendor environment and status• Problems: – Project overruns – Poor vendor relationships. (Change request h*ll) – Poor quality – No visibility into status, quality or status; impossible to manage risks
  17. 17. Scenario #9: Inconsistent Processes• Different team members handle development in different ways: different coding styles, testing practices, tracking methods, documentation, etc.• Team members have different terminology to describe the same thing (e.g., what does “done” mean)• Problems: – Impossible to understand what the organization as a whole is doing – Difficult to maintain each others code – Tends to increase technical debt and decrease quality
  18. 18. Scenario #10: Ill-fitting or Obsolete Processes• Development process require certain artifacts, reports or other efforts• Effort expended on these processes don‟t seem to add value but the continue because “we have always done it this way”• There aren‟t sufficient feedback mechanisms to support changing processes• Problems: – Excess time spent on processes that don‟t add value – Reduced time is available to support process that do add value – Team Frustration from doing „make work‟ activities
  19. 19. Scenario #11: Failed Projects• Organization prioritizes and funds a software development project• For a variety of reasons, after months of development effort it is determined that the project is a failure• Project is cancelled and work ceases• Problems: – Failed projects are very costly – Time spent by team not delivering value – Bad for morale
  20. 20. Other Opportunities What are your“Opportunities”?
  21. 21. Calculating the Costs• Is ignoring these opportunities costing you?• Scenario #3: Misunderstood requirements (Example) – Assumptions (Simple case) • Two developers working on a specific requirement • Two weeks total duration for that requirement • An additional eight weeks is performed on related requirements • Developers salary + benefits is $100K annually (each) • After discovery, 70% of the work is salvageable – Costs • (2 people X 10 weeks X (100-70%)) = 6 weeks lost • 6 weeks @ 100K = 100K X 6 / 52 = $11,500 (per requirement) – Additional Costs • Approximately 6 weeks slipped schedule
  22. 22. Another Example• Scenario #10: Ill-fitting or Obsolete Processes – Assumptions • Average team member salary + benefits is $100K annually • Team members spend an average of six hours each week performing tasks that don‟t add value • An additional two hours per week is lost due to benefits not gained from doing practices that do add value • Team contains 10 members – Costs • 10 team members X (6 + 2 hours/week) / (40 hours/week) X $100K = $200,000 wasted per team annually – Additional Costs • Team member frustration
  23. 23. Final Example• Scenario #11: Failed Projects (Example) – Assumptions • Project contains 10 team members across all disciplines • Average team member salary + benefits is $100K annually • Team expends six months before project is cancelled – Costs • 10 team members X 100K X (6 months / 12 months) = $500K – Other Costs • Original needs not met This is the sort of thing that causes people to get fired and can even close companies!
  24. 24. What is lack of ALM costing you?• Do see any of these scenarios in your environment?• Are there other inefficiencies and barriers in your application development?• Do you know what your current practices and tools cost you in lost time? In customer dissatisfaction? In money? In stress? In turn-over?
  25. 25. Agenda Application Lifecycle and ALM ALM Opportunities The Bottom Line Conclusion
  26. 26. Microsoft‟s ALM Solution
  27. 27. Visual Studio 2012 TFSOffice TEAM FOUNDATION SERVER
  28. 28. ALM Practices and Microsoft Tools ALM Practices• Common vocabulary • Capacity Management • Test Environment• Consolidated & Consistent • Integrated Team Management Information • Quality Mindset • Performance Testing• Backlog Management • Requirements driven • Automated Deployment• Storyboarding • Transparency • Automated Testing• Team Mindset • Stakeholder Feedback • Continuous Delivery• Requirements feedback • Daily meetings • Continuous Feedback• Iterative Development • Current information • Continuous Improvement• Agile Planning • Quality Assurance • Dev/Ops Coordination• Automated Builds • Rich communications ALM ToolsTeam Foundation Server Visual Studio 2012 Microsoft Test Manager• Backlog Management • Integrated ALM • Requirements Suites• Capacity Management • Architecture tools • Manual Testing• Kanban Board • My Work • Exploratory Testing• Agile Taskboard • Suspend/Resume • Rich Defect Tracking• Integrated Reporting • Unit Testing • Lab Management• Work Item Tracking • Fakes • Test Impact Analysis• Team Foundation Build • Coded UI Testing• Alerts • Load Testing Feedback Client• Dashboards • Code Metrics • Code Clone Analysis System Center 2012PowerPoint Storyboarding • IntelliTrace
  29. 29. Agenda Application Lifecycle and ALM ALM Opportunities The Bottom Line Conclusion
  30. 30. Summary• ALM is the use of tools and practices to help you effectively manage your application lifecycles.• Ineffective and under-managed application lifecycles expose numerous „opportunities‟• Adopting ALM best practices and tools can help you capitalize on these „opportunities‟• Microsoft has amongst the best tools for managing your application lifecycle• Investments in your ALM practices and tooling can pay off and positively affect your bottom line
  31. 31. Questions?
  32. 32. Want to know more...?
  33. 33. Imaginet‟s New Blog Keeps You In The KnowStay up to speed on the latest news from Imaginet, Microsoft,Visual Studio, and the entire software development world.
  34. 34. More Webcasts on ALM / TFS / Visual Studio 2012Upcoming ALM Workshops & Webcasts: • Getting Started With Coded UI testing: Building Your First Automated Test • February 28 (1:00-2:30pm CT) • Lean, Kanban, and TFS • March 7 (1:00-2:30pm CT) • March 21 (1:00-2:30pm CT) • Using Lean and Kanban to Revolutionize Your Organization • March 11 (1:00-2:00pm CT) • The newest of the new with Visual Studio and TFS 2012 • March 14 (1:00-2:30pm CT) • March 28 (1:00-2:30pm CT)
  35. 35. For attendees of today‟s session that fill out the survey FREE Imaginet On Demand Web Training Subscription OfferComplete our Post-Webcast survey, and receive 1free Imaginet On Demand web trainingsubscription, good for 1 person for 1 month!! Thesurvey will be emailed to you immediately after thiswebcast is over.What is Imaginet On Demand? Imaginet is proud to announce our newestweb-based training program called Imaginet On Demand, your source for thebest Application Lifecycle Management (ALM) training on the internet.Imaginet On Demand is a subscription-based training program centric to theVisual Studio ALM tools, including Visual Studio, Team Foundation Server(TFS), Microsoft Test Manager, and Microsoft Visual Studio Lab Management.Learn the new tools of Visual Studio at your pace, from wherever you want.Its that simple!
  36. 36. Free Services from Imaginet & MicrosoftThere are a number of different Microsoft Programs that youmight be able to leverage to get some free services fromImaginet:• Deployment Planning Services (DPS) – You can trade in your Microsoft Software Assurance credits to receive some free TFS/ALM Deployment Planning Services days with Imaginet• Partner Services Credit (PSC) – Have you or are you about to spend money with Microsoft on Visual Studio 2012 products? If so, Microsoft may kick in some funding to help you successfully adopt.• Virtual Technical Specialist (VTS) hours –You may be eligible to receive some free remote consulting/training hours with Imaginet through the Microsoft Virtual Technical Specialist program. For more information, email
  37. 37. ALM Planning & Implementation ServicesALM Planning Testing• ALM Assessment & Envisioning Workshops • Manual Testing with Test Manager Quick (3 or 5 days) Start (5 days)• VS & TFS Migration Planning Workshop (5 • Visual Studio Testing Tools Quick Start (10 days) days)• TFS Deployment Planning* (5 days) • Visual Studio Automated Testing Quick Start• Visual SourceSafe to TFS Migration (5 days) Planning* (3 Days) • Visual Studio Load Testing Quick Start (5 or• Visual Studio Quality Tools Deployment 10 Days) Planning* (5 days) BuildsUpgrade • Automated Build & Release Management• TFS 2010 Adoption Quick Start (5 or 10 Quick Start (5 days) days) • Automated Build Center of Excellence (CoE)• TFS 2012 Adoption Quick Start (5 or 10 days) Database• TFS 2010 Upgrade Quick Start (10 days) • Visual Studio Database Tools Quick Start• TFS 2012 Upgrade Quick Start (10 days) (10 days)Remote Support Integrations• Remote Support for TFS & Visual Studio • Team Foundation Server (TFS) & Project Server Integration Quick Start (10 days)Lab • TFS & Quality Center Integration/Migration• Visual Studio Lab Management Quick Start Quick Start (10 days) (10 days)
  38. 38. Need Help with YOUR Application Lifecycle Management? Imaginet’s ALM Assessment & Envisioning Workshop • Assess the current state of maturity of software development at your company • Develop a plan and roadmap for improving software development practices • At the completion of the ALM Workshop, your organization will have a better understanding of not only where you are today, but the steps you can take to improve your software development, management, configuration, and quality practices to meet your goals. Interested? Just email us at
  39. 39. Top Gun Academy Training Classes• Other Imaginet Training Classes – ALM • Microsoft Visual Studio & TFS 2012 – Skills Upgrade (2 days) • Overview Training with Microsoft Visual Studio 2012 ALM Tools (4 days) • Overview Training with Microsoft Visual Studio 2010 ALM Tools (4 days) • Testers Training with Microsoft Visual Studio 2012 ALM Tools (4 days) • Testers Training with Microsoft Visual Studio 2010 ALM Tools (4 days) • Developers Training with Microsoft Visual Studio 2012 ALM Tools (4 days) • Developers Training with Microsoft Visual Studio 2010 ALM Tools (4 days) • Imaginet On Demand Online Web Training – Scrum/Kanban • Professional Scrum Foundations (PSF) (2 days) • Professional Scrum Master (PSM) (2 days) • Professional Scrum Developer (PSD) (5 days) • Professional Scrum Master (PSM) Using Microsoft ALM (3 days) • Accredited Core Kanban Using Microsoft ALM (3 days) To register or for more information, please visit our website here: or contact us:
  40. 40. Upcoming Class – Tester Training with VS 2012 Testers Training Using Visual Studio 2012 ALM Tools (4 Days Class)This four-day instructor-led course provides students with theknowledge and skills to use the latest testing tools provided by VisualStudio 2012 to support a variety of different testing needs (manualand automated).Date: March 11-15, 2013Location: Dallas (Irving, TX)Price: $2375/student Registration link will be included in our follow-up email later today!
  41. 41. For questions or more information, please contact us at: or (972)607-4830 Remember to add to your favorite reader!
  42. 42.