4. Complex Software is Everywhere!
Product Lines of Code
Typical Order Entry System 1,2 Million
F-22 Raptor 1,2 Million
Space Shuttle 2 Million
Microsoft Word 2 Million
F-35 Joint Strike Fighter 5,7 Million
Typical Airline Reservation System 6 Million
Mercedes Benz S Class 29 Million
5. The ability to use, develop, integrate and deliver
custom software is strategic for most organizations
However, unlike other strategic business processes,
there are often large gaps – which creates risk:
No consistent processes are being applied to the development and management of custom software.
Reporting on developer productivity, software quality and business value is missing.
Development processes and activities are not predictable and repeatable.
Complexity of software (and value opportunities) grow
without associated maturity and team capabilities
Business Runs On Software
6. How wella firm executes its
business strategies is tied to how
goodit is at creating and managing
custom applications!
DavidChappell
18. Value Delivery Impediments
No Progress Monitoring
Unmanageable Complexity
Lack of KPIs and Insight
Loss of Focus
Non-Repeatable Work
Business Requirements Grow Exponentially
Inconsistent (or no) Processes
Poor Communication Across Functional Silos
Unpredictable Results
Hidden Risks
Wasted Time and Effort
Scope Creep
21. “Conventional” QA
QA
Testing post
implementation. Mostly
manual with limited
automation.
UAT
UAT post
implementation
and systems
testing
Operations
readiness
verification
Pre-deployment
verification
Document requirements
as BRDs and
functional specs
Write code to
implement
requirements
27. Requirements don’t reflect customer intent
Rework, long delivery cycles and frustration.
Storyboarding Tool
Graphical mockups and visual prototypes in new PowerPoint add-on reduce
misunderstandings and clarify intent.
Feedback Manager
Stand-alone feedback tool allows stakeholders to provide comprehensive feedback
on any artifact, including storyboards, directly to development teams.
Problem
Solution
Solution
Misunderstood Requirements
29. Blocker: Quality is an Afterthought
Quality not built in from the start
Failure to meet user needs, rework, long delivery cycles and customer dissatisfaction.
Unit Testing
Extensible unit test framework targets specific needs or technologies to ensure code correctness.
Fakes and stubs framework
Powerful mocking framework to simplify unit testing and isolate logic.
Problem
Solution
Solution
31. Blocker: Unmet User Expectations
Delivered functionality fails to satisfy users
Failure to meet user needs, rework, long delivery cycles and customer dissatisfaction.
Problem
Solution
Exploratory Testing
Ad-hoc exploratory tests help uncover usability and consistency issues, and result
in actionable bugs and reusable test cases.
33. Blocker: Unmet Operations Readiness
Delivered code fails to perform as planned
Failure to meet IT maintenance needs, rework, long delivery cycles and customer dissatisfaction.
Web Testing
Lightweight web tests validate correct functionality and behavior, both in testing and production.
Load Testing
Powerful load test frameworks simulates thousands of simultaneous users
to ensure performance, stability and uptime.
Problem
Solution
Solution
34. Blocker: Can’t Get Actionable Feedback
Delayed feedback on code changes
Fixing critical bugs takes a long time, increases in context switching,
rework and long delivery cycles.
Continuous Integration
Build, deploy and test complex applications on every check-in to
quickly identify problematic code changes.
Lab Management
Self-service test lab provisioning speeds manual and automated build-deploy-test feedback cycles.
Problem
Solution
Solution
35. Sessions 03 and 06
Operations and Feedback
Test Specification and Execution
36. Limited Visibility into Quality States
Lack of visibility into overall quality
Slows fixes of bugs, increases context switching, rework and long delivery cycles.
Reporting
Out-of-the-box and ad-hoc reports track quality against requirements,
builds, releases and other artifacts.
Problem
Solution
38. Blocker: Operational Requirements Not Met
Production errors not caught quickly enough
Longer bug fix cycle times, customer dissatisfaction, and costly remediation.
Monitor in-production applications
Management pack templates make real time monitoring of production applications easy.
Problem
Solution
40. Disparate Management Tools
Isolated tools and workflows
Poor communication, longer production bug fix cycle times, and customer dissatisfaction.
Integrated Incident management tools
Common view of incidents to both Operations and Development.
Shared artifacts
Reuse development artifacts, such as tests, inside System Center to reduce
rework and discover production issues early.
Problem
Solution
Solution
41. Production Incidents Hard to Debug and Resolve
Production errors
Difficult to identify root cause, debug code and resolve defects.
Actionable diagnostics
IntelliTrace in production to speed debugging and code fix.
Translatable artifacts
System Center logs can be converted to IntelliTrace logs for developer use.
Problem
Solution
Solution
42. Slow Feedback Creates Waste
Slow feedback
Time lags between work and feedback result in wasted time, increased context switching, and rework.
Lab Management
Self service test lab provisioning speed build-deploy-test feedback cycle.
Problem
Solution
45. Save time and reduce risks
Integrated test tools
Advanced test tools
integrated
solution
Continuously deliver value
storyboard and user feedback
tools
Visual Studio 2012 Quality Enablement