Bringing together traditional QA and Agile development with Software Lifecycle Integration
-
Upload
jeff-downs -
Category
Software
-
view
80 -
download
0
description
Transcript of Bringing together traditional QA and Agile development with Software Lifecycle Integration
@jdowns26
Bringing together traditional QAand Agile development with
Software Lifecycle Integration
How did I get here?
TestLinkAdministration
TestAutomation HP QC
Administration
ToolIntegration Software
LifecycleIntegration
#SLI
Software is eating the world -Marc Andreessen in
Wall Street Journal
#SLI
In 2001, Borders agreed to hand over its online business to Amazon under the theory that online book sales were non-strategic and unimportant.
Software, a Key Business Process
#SLI
10 million lines of code
Software, a Key Business Process
#SLI
100,000 hours of testing
Project
ManagersDevelopers
BizAnalysts
Testers
Ops
#SLI
feedback loops
#SLI
People, processes and tools
Testing Center of Excellence
#SLI
cadence chaos!
#SLI
no end-to-end tool suite!
#SLI
other people’s silos
The #1 problem
Lack of cross lifecycle transparency
Complex integration process
Redundant features
Magnitude of the effort
Overall cost of the tools
38.6%
64.6%
32.1%
53.2%
63.2%
N = 280 Source = Forrester
“Which of the following would you consider as major roadblocks of ALM solutions?”
As the complexity of our tool stack and development demands grow, getting tools and data integrated is now a major initiative to avoid complete gridlock.
Tasktop Customer
#SLI
Agile creates the need to break down the barriers between disciplines. But software delivery tools add to the barriers. The time is right for organizations to start thinking about connecting tools more strategically to enable the practice of software delivery to flow.
Ken SchwaberFounder ofScrum.org
#SLI
It's not that the brakes don't work, it's the traceability of the software.
General Manager of 787 program
#SLI
#SLI
What’s your integration strategy?
#SLI
#SLI
#SLI
#SLI
#SLI
#SLI
Data confusion and chaos
Traceability problems
Manual processes
Communications failing
Maintenance pains
Siloed thinking
The pain of ALM
#SLI
Imagine an integrated fabric
that allows information to flow freely and in real-time
across the stakeholders,
tool silos
and vendor boundaries.
#SLI
Software Lifecycle Integration (SLI)
is a discipline focused on a
connected software delivery lifecycle.
#SLI
Insight
Goals of SLI
#SLI
Traceability
Flow
Automation
Choice
A New Architecture Vendor neutral
Large cross-section of ALM vendors
CollaborativeReal-time communication flow
Scalable1000s of users, dozens connections
InvisibleNot a new system of engagement
#SLI
SLI Architect
Strategic integration decisions
Respected across disciplines
A New Role
#SLI
Understanding the PatternsSLI Pattern Applies to Diagrams
Defect Unification • Agile development• Waterfall development• Separate Dev & QA Teams & tools
Requirements Traceability • Agile development• Traditional Requirements• Traditional QA
Supply Chain Connection • Traditional Requirements• Agile dev sourcing• Outsourced QA
PMO - Development • Traditional or Agile development• Organizations with PMO separate
from Dev
Help Desk Incident Escalation • DevOps• Agile or Traditional
development• Support organization separate
from the development teams
Dev QA
BAAgile Dev
QA
Agile
PM
Dev
Test
BA
PMO Dev
Ops
Dev
QA
#SLI
Building the Case
#SLI
Research study from IDC states the cost of not finding information is $3,300 per employee per year.http://ejitime.com/materials/IDC%20on%20The%20High%20Cost%20Of%20Not%20Finding%20Information.pdf
Identify Integrations
Obtain Real Financial Numbers
Factor in Soft Benefits
Building the Case
#SLI
20 minutes per day6 developers20 days per sprint= 5 staff days per sprint
Defect Unification
Better ReportingIdentifying trends previously missed
What should SLI look like?
Por
tfolio
Mgt
Agile Proj Mgt
Requirements
Development
Test
Ope
ratio
ns
#SLI
Connecting the world of software delivery
© Tasktop 2013
@[email protected]://www.linkedin.com/in/jeffreysdowns/tasktop.com/SLI