Quality Enablement - Agile Practices with Quality Enablement
•
0 likes•1,757 views
This document discusses quality enablement and continuous testing practices for modern application development. It outlines how conventional QA involves late engagement, increased costs and cycle times. The proposed solution advocates for defining requirements, acceptance criteria, automated testing, and feedback throughout the development process. This enables continuous value delivery with testing at least every 30 days. Role-tailored tools are recommended to support requirements management, testing, feedback and reporting across the application lifecycle.
Report
Share
Quality Enablement - Agile Practices with Quality Enablement
- 1. Randy Pagels Developer Tools Technology Specialist
- 5. 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
- 13. • 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
- 15. • 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
- 17. Organizing Manual Tests Exploratory Testing Feedback Management
- 18. 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
- 20. Business value of quality enablement Attainment of business objectives Shortened value delivery cycle times User and stakeholder satisfaction Cost reduction
- 21. Application Lifecycle Continuous quality practices Role tailored tools Extensible Hybrid IT capable
- 22. 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
- 23. What’s new in VS 2013: msdn.microsoft.com/en-us/library/vstudio/bb386063(v=vs.120).aspx Visual Studio blog: blogs.msdn.com/b/visualstudio/ Visual Studio Toolbox on Channel 9: channel9.msdn.com/Shows/Visual-Studio-Toolbox