Your SlideShare is downloading. ×
Quality Enablement -  Agile Practices with Quality Enablement
Upcoming SlideShare
Loading in...5

Thanks for flagging this SlideShare!

Oops! An error has occurred.


Saving this for later?

Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime - even offline.

Text the download link to your phone

Standard text messaging rates apply

Quality Enablement - Agile Practices with Quality Enablement


Published on

Published in: Technology

  • Be the first to comment

  • Be the first to like this

No Downloads
Total Views
On Slideshare
From Embeds
Number of Embeds
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

No notes for slide


  • 1. Randy Pagels Developer Tools Technology Specialist
  • 2. Building Modern Apps Quality Enablement Agile Planning Developer Operations
  • 3. Conventional QA Solution managers Developers Document requirements as BRDs and functional specs Define BACKLOG Ideation Write code to implement requirements Develop Construct Idea to Working Software QA Connect RELEASE UAT Testing Post –implementation Testers Mostly manual with limited automation. Operate Users Operate Working software to Business outcomes Operations readiness verification UAT post implementation & systems testing Operations Pre-deployment verification Late engagement of stakeholder functions | Late detection of unmet requirements | Increased cycle times | Increased costs
  • 4. Define Operate Construct Develop Connect Operate Release
  • 5. Define Operate Construct Develop Connect Operate Release
  • 6. Define Operate Construct Develop Connect Operate Release
  • 7. Define Operate Construct Connect Operate Release Develop Shared test artifacts
  • 8. Define Operate Construct Develop Connect Operate Release
  • 9. Define Operate Construct Develop Connect Operate Release
  • 10. Quality Enablement Architecture
  • 11. • Actionable feedback • Exploratory testing • Requirements management • Acceptance criteria definition • Developer testing • Build automation • Actionable Role tailored tools diagnostics Build engines Lab infrastructure • Production monitoring • Integrated incident management Test recorders and runners Quality metrics and reporting
  • 12. The Microsoft Solution
  • 13. • Office • Feedback client Requirements management • Office,SharePoint • Project • Browser apps Project planning & management Team development services • VS IDE • Eclipse • Xplatform tools Microsoft Test Manager Microsoft System Center Source code management Test lab management Testing services Build and deployment automation Git Lab infrastructure Test recorders and runners Build engines • • Office SharePoint Reporting and Business Intelligence
  • 14. Requirements Acceptance criteria Code Tests Feedback Releases Learning
  • 15. Organizing Manual Tests Exploratory Testing Feedback Management
  • 16. Business challenges Solutions Business value UI regression test needs grow over time Record and automate UI tests Test more functionality in less time Manual UI testing impacts the delivery cycle times Automated UI tests are brittle, time-consuming to maintain Robustly instrument UI tests to reduce maintenance overhead Associate UI tests with a scheduled build Reduce or eliminate repetitive manual testing Reduce cycle time when delivering new features
  • 17. Business value of quality enablement Attainment of business objectives Shortened value delivery cycle times User and stakeholder satisfaction Cost reduction
  • 18. Application Lifecycle Continuous quality practices Role tailored tools Extensible Hybrid IT capable
  • 19. Testing through Quality Enablement Continuous quality for continuous value delivery Short and iterative delivery cycles Traceability throughout the full lifecycle Role tailored tools Business value of Quality Enablement With these continuous quality practices, coupled with tools that are tailored for each role we are able to more easily and effectively achieve continuous value delivery at least every 30 days
  • 20. What’s new in VS 2013: Visual Studio blog: Visual Studio Toolbox on Channel 9: