Your SlideShare is downloading. ×
IBM Innovate 2013Why You Need an ALM Data Model:Increasing Visibility and Transparency toEnable Business AgilityDave WestC...
2Agenda Why do we need an ALM Data Model?• What is wrong with ALM ?• The business value of the model The future is conne...
ALM driven by management3Wikipedia
4ALM has not been that successful, with 30-70% of softwareprojects failing…DevOpsTestersDevelopersProjectManagersBusinessA...
5We have optimizedthe silos enough
6Which has led to ALM confusionNot a pretty sight Lack of ALM architecture Data confusion and chaos Governance problems...
7It’s not that the brakes don’t work,it’s the traceability of the software.Pat Shanahan,GM, 787 Project
And it will only get worse…Software supply chainsbecoming ecosystemsShorter iterationsBuild/measure/learnProcessEcosystemT...
 What we can learn– Process affects model– App lives longer than project– Need for manufacturing view– Support part of th...
Fidelity – Need for Standard ALM Data Model?• Single vendor ALM tool stack is not realistic• Best of breed means multiple ...
Fidelity – Need for Standard ALM Data Model!! We are manufacturers of applications and systems– We should capture and ana...
In The FutureProcess / FlowActivitiesReporting / AnalyticsDetailed cross project and productanalysis including historic in...
What we needConsistent terminology, definedrelationships and structureThe Model Data warehouseSingle normalized warehouse ...
 Consistent definition of theartifacts A clear understanding of theirrelationships Description of the key statetransiti...
 Org Structures Portfolios Products Applications, Releases IT Assets Programs, Projects Financials Resources Meas...
Enabling the infrastructureThe BusInfrastructure that connectsthe data that runs the process Support for integration to m...
Example Data ModelArtifactLifecycle Asset(value)Executable Build SpecSource CodeRqrmntDefinitionProductSocial Task(work)Wo...
Broad view..SourceCodeTest RequirementSpecificationsBuildspec Etc…OperationEventsObservationsExecutionsTestResultsDefectWo...
19Scenarios Help Add DetailDaily work in a development teamTeam status reportingRelease software to productionProject ...
Example: Day to Day WorkStoryDefectTaskChangeSetBuildTest PlanTestEnvironmentTestResultDeployedon TestBuilt onBuildsfromBu...
Example: PlanningStorySprintReleaseEpicsThemes /Businessobjectives Backlog(s)TeamProjectIs made upofBroken upintoDrivescre...
22Fidelity - Tactical ALM Objectives Standardize on a manageable number of ALM Tool Stacks– Proposition: Here is what you...
Recommendations Treat ALM as a key business process–Ownership–Value–Architecture Create a data model–Share model with te...
Become part of the working group24We have a cross vendor organization workinggroup on defining an industry ALM data modela...
25
26Daily Apple TV giveaway Complete your session surveys online each day at a conference kiosk or onyour Innovate 2013 Por...
27© Copyright IBM Corporation 2013. All rights reserved. The informationcontained in these materials is provided for infor...
Upcoming SlideShare
Loading in...5
×

IBM Innovate 2013, Dave West: Why You Need an ALM Data Model: Increasing Visibility and Transparency to Enable Business Agility

327

Published on

*** See more on: http://tasktop.com/resources/videos ***
For many organizations, the promise of ALM has been undermined by disconnected tools, process, organizations and practices. But as organizations pivot business models and deliver faster, the need for ALM is much greater. Increased visibility and flow are the corner stones to increased business Agility. But for many organizations, adopting Agile at the team level has left enterprise ALM in a worse state than before, with teams adopting tools, practices and even process models for their own needs. So how do organizations increase the visibility of software delivery whilst software is being delivered by a diverse set of project teams, all following slightly different methods and using a variety of tools?
In this talk, Dave West, Chief Product Officer at Tasktop Technologies, and Tim Mulligan, ALM Architect at Fidelity Investments, discuss the value of introducing an ALM Data Model and how it can provide a common currency for visibility, collaboration and flow for large complex organizations. They describe what an ALM data model looks like and how it can form the backbone for any federated ALM strategy. The talk draws on practical experience by Fidelity of starting this endeavor and industry experience by Tasktop, who have worked with many organizations connecting information from disconnected tools. The talk will cover:
1. Why your organization needs an ALM data model.
2. What an ALM data model looks like.
3. How the ALM data model increases the value of CLM data.
4. Example implementation plan for an ALM data model.
Business Challenges
Want: increased visibility, transparency and governance with a heterogeneous, multi sourced development organization. Need: to increase control without forcing people to adopt one tool. Have: external suppliers developing software using a variety of practices and tools.
Business Benefits
A clear understanding of what ALM is, what the terminology is and how tools support this model. This enables an organization to build a data warehouse, integration strategy and technology / tools roadmap.

Published in: Technology
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
327
On Slideshare
0
From Embeds
0
Number of Embeds
2
Actions
Shares
0
Downloads
0
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide

Transcript of "IBM Innovate 2013, Dave West: Why You Need an ALM Data Model: Increasing Visibility and Transparency to Enable Business Agility"

  1. 1. IBM Innovate 2013Why You Need an ALM Data Model:Increasing Visibility and Transparency toEnable Business AgilityDave WestChief Product Officer, Tasktopdave.west@tasktop.comLM-2090© 2013 IBM CorporationTim MulliganALM Architect Fidelity Investmentstimothy.mulligan@fmr.com
  2. 2. 2Agenda Why do we need an ALM Data Model?• What is wrong with ALM ?• The business value of the model The future is connected, traceable,historic and reported• Introducing the ALM data model How do you get there?
  3. 3. ALM driven by management3Wikipedia
  4. 4. 4ALM has not been that successful, with 30-70% of softwareprojects failing…DevOpsTestersDevelopersProjectManagersBusinessAnalystsSilo tool focus has resulted in alack of focus on the end-to-endbusiness process.
  5. 5. 5We have optimizedthe silos enough
  6. 6. 6Which has led to ALM confusionNot a pretty sight Lack of ALM architecture Data confusion and chaos Governance problems Traceability problems Maintenance pains Manual processes Communications failing Siloed thinkingMakes reporting, analytics andALM really difficult…
  7. 7. 7It’s not that the brakes don’t work,it’s the traceability of the software.Pat Shanahan,GM, 787 Project
  8. 8. And it will only get worse…Software supply chainsbecoming ecosystemsShorter iterationsBuild/measure/learnProcessEcosystemTechnologyAPI Economy provides fabric connectingsystems of recordToolsDevelopers and teams selecting toolsthat make them productive
  9. 9.  What we can learn– Process affects model– App lives longer than project– Need for manufacturing view– Support part of the model– Variants are complex andimportantPLM have done this before
  10. 10. Fidelity – Need for Standard ALM Data Model?• Single vendor ALM tool stack is not realistic• Best of breed means multiple ALM tool vendors• Open Source ALM tools cannot be denied/ignored• Rapid introduction, change, evolution• Technologies require multiple ALM tool stacks• Java versus .NET (square peg in round hole)• Each vendor does what they think best• Point to point ALM tool integrations …• Provide traceability and synchronization• Can be costly and fragile• Do not address „full picture„ view of ALM10
  11. 11. Fidelity – Need for Standard ALM Data Model!! We are manufacturers of applications and systems– We should capture and analyze data related to our manufacturing process– We should expect our suppliers to adhere to standards in the machinery we purchase fromthem– How have we gone this long without an industry standard SDLC/ALM Data Model?– It has literally become the “Wild West” out there Management should focus on facts/data/metrics - not controlling perception We want a full picture of the application lifecycle–Portfolios / Product Lines / Products / Applications / IT Assets–Programs / Projects / Maintenance–Resources–Financials–Measurements / Metrics / Analytics11
  12. 12. In The FutureProcess / FlowActivitiesReporting / AnalyticsDetailed cross project and productanalysis including historic informationand analyticsWork moves seamlessly between silosallowing collaboration, and governancePractitioners are supported in doingtheir work with practices they selectedand use
  13. 13. What we needConsistent terminology, definedrelationships and structureThe Model Data warehouseSingle normalized warehouse of datafor cross project / product reportingThe BusInfrastructure that connectsthe data that runs theprocess
  14. 14.  Consistent definition of theartifacts A clear understanding of theirrelationships Description of the key statetransitions of each artifact Details of the reports required Mappings to the locationsDefining the modelConsistent terminology, definedrelationships and structureThe Model
  15. 15.  Org Structures Portfolios Products Applications, Releases IT Assets Programs, Projects Financials Resources MeasurementsDescribing the Data WarehouseData warehouseSingle normalized warehouse ofdata for cross project / productreporting
  16. 16. Enabling the infrastructureThe BusInfrastructure that connectsthe data that runs the process Support for integration to multiple toolend points from different vendors Can support 1000s of users andprojects across organizational, projectand company boundaries Works in real time to enable real timereporting and analytics Supports open standards such as TRSand OSLC and vendor formats Does not require any changes to toolsand is invisible to teams
  17. 17. Example Data ModelArtifactLifecycle Asset(value)Executable Build SpecSource CodeRqrmntDefinitionProductSocial Task(work)Work ItemIssueDefectPlan ItemEpicUser StoryRqrmnt IncidentProjectcontext
  18. 18. Broad view..SourceCodeTest RequirementSpecificationsBuildspec Etc…OperationEventsObservationsExecutionsTestResultsDefectWork that needs to be doneTaskEtc…StoryChangeRequestEtc…Test Plans ReleasesIterationsCollections
  19. 19. 19Scenarios Help Add DetailDaily work in a development teamTeam status reportingRelease software to productionProject planningTest development and planningDefect planning and developmentEtc…
  20. 20. Example: Day to Day WorkStoryDefectTaskChangeSetBuildTest PlanTestEnvironmentTestResultDeployedon TestBuilt onBuildsfromBuildPlanExecutesonCreatesIs executedonFailed orpassedIs a type of..AnalysisPolicyEvaluateagainstSourceCodeComprisesObservationsAnalysisPlanActs onActs onTechDebt
  21. 21. Example: PlanningStorySprintReleaseEpicsThemes /Businessobjectives Backlog(s)TeamProjectIs made upofBroken upintoDrivescreation ofAppBroken upinto & areleaseincludesmany Lots of different planning models
  22. 22. 22Fidelity - Tactical ALM Objectives Standardize on a manageable number of ALM Tool Stacks– Proposition: Here is what you get if you use the standard/preferred tools (value add) Work with Tasktop to drive industry toward standard ALM Data Model Develop an ALM Data Warehouse– A governed repository of application lifecycle data– To serve as a singular point for all data necessary to report/analyze the lifecycle of applicationsthroughout the enterprise– Initial purpose will be Metrics & Analytics Utilize ALM tool vendor supplied APIs whenever possible to extract desired data Figure out how to store our “primary keys” within each ALM tool Develop role-based dashboards–Upper Mgmt, Portfolio Mgr, Program Mgr, Project Mgr, Resource Mgr
  23. 23. Recommendations Treat ALM as a key business process–Ownership–Value–Architecture Create a data model–Share model with teams and partners–Use model to drive conformance–Take advantage of model for reporting and analytics Introduce technology to make it happen–Think about how data moves around the model–Employ technology to make it happen–Make ALM a reality in your organization23
  24. 24. Become part of the working group24We have a cross vendor organization workinggroup on defining an industry ALM data modeland best practicesEmail – dave.west@tasktop.com to join
  25. 25. 25
  26. 26. 26Daily Apple TV giveaway Complete your session surveys online each day at a conference kiosk or onyour Innovate 2013 Portal! Each day that you complete all of that day‟s session surveys, your name willbe entered to win the daily Apple TV! On Wednesday be sure to complete your full conference evaluation to receiveyour free conference t-shirt!
  27. 27. 27© Copyright IBM Corporation 2013. All rights reserved. The informationcontained in these materials is provided for informational purposes only, and isprovided AS IS without warranty of any kind, express or implied. IBM shall not beresponsible for any damages arising out of the use of, or otherwise related to,these materials. Nothing contained in these materials is intended to, nor shallhave the effect of, creating any warranties or representations from IBM or itssuppliers or licensors, or altering the terms and conditions of the applicable licenseagreement governing the use of IBM software. References in these materials toIBM products, programs, or services do not imply that they will be available in allcountries in which IBM operates. Product release dates and/or capabilitiesreferenced in these materials may change at any time at IBM‟s sole discretionbased on market opportunities or other factors, and are not intended to be acommitment to future product or feature availability in any way. IBM, the IBM logo,Rational, the Rational logo, Telelogic, the Telelogic logo, and other IBM productsand services are trademarks of the International Business Machines Corporation,in the United States, other countries or both. Other company, product, or servicenames may be trademarks or service marks of others.

×