big box company big box company software development lifecycle assessment: findings and...

19
Big Box Company Big Box Company Software Development Lifecycle Assessment: Findings and Recommendations June 15, 2010 Big Box Company

Upload: rosaline-welch

Post on 13-Dec-2015

223 views

Category:

Documents


3 download

TRANSCRIPT

Big Box Company

Big Box Company Software Development Lifecycle Assessment:

Findings and RecommendationsJune 15, 2010

Big Box Company

IBM AND BIG BOX COMPANY CONFIDENTIAL – FOR INTERNAL USE ONLYJune 15, 2010 Page 2

Big Box Company Contents

• Big Box Company Assessment Focus• Approach• Survey vs. Interview Results• What’s Working Well• Representative Challenges• Challenges: Identifying Gaps• Options: Effort vs. Value• Potential Inhibitors to Adoption• Next Steps

IBM AND BIG BOX COMPANY CONFIDENTIAL – FOR INTERNAL USE ONLYJune 15, 2010 Page 3

Big Box Company Assessment Focus

• Identify opportunities to help Big Box Company balance speed to market with quality

• Understand where Big Box Company performs relative to modern software development practices

• Identify opportunities for improvements in SDLC and establish an actionable roadmap

IBM AND BIG BOX COMPANY CONFIDENTIAL – FOR INTERNAL USE ONLYJune 15, 2010 Page 4

Big Box Company Approach

The IBM Assessment offers a structured approach to help teams measure and iteratively improve the business process of software delivery using:

– Surveys– Interviews– Selected Artifact Review– Findings and

Recommendations– Roadmap

Empower teams to measure, manage and incrementally improve their software delivery capability.

Elicit and set business value objectives

Determine the practicefocus areas

Accelerate and monitor practice adoption

Review and communicate business results

Phase1

Phase2

Phase3

Phase4

Go back to Phase 2

Confirm results deliveredand start next project

IBM AND BIG BOX COMPANY CONFIDENTIAL – FOR INTERNAL USE ONLYJune 15, 2010 Page 5

Big Box Company Background• Thank you!

– … for your openness & participation– … for the time you spent with us

• Over the past weeks we have – Surveyed 51 individuals with 29 responses– Interviewed 34 stakeholders - 3 have multiple roles - 9 also in survey

– Gathered CIO and executive perspectives– Reviewed representative artifacts and templates provided by Big Box Company

IBM AND BIG BOX COMPANY CONFIDENTIAL – FOR INTERNAL USE ONLYJune 15, 2010 Page 6

Big Box Company Core SDLC Practices

*

* *

* = Focus Areas

Practices used for the assessment

IBM AND BIG BOX COMPANY CONFIDENTIAL – FOR INTERNAL USE ONLYJune 15, 2010 Page 7

Big Box Company Typical Large Company Profile

IBM AND BIG BOX COMPANY CONFIDENTIAL – FOR INTERNAL USE ONLYJune 15, 2010 Page 8

Big Box Company Big Box Company’s Self-Assessment

BBC current view

What IBM typically sees

BBC’s future

IBM AND BIG BOX COMPANY CONFIDENTIAL – FOR INTERNAL USE ONLYJune 15, 2010 Page 9

Big Box Company IBM Findings BBC’s assessed state

What IBM typically sees

Effective practices

IBM AND BIG BOX COMPANY CONFIDENTIAL – FOR INTERNAL USE ONLYJune 15, 2010 Page 10

Big Box Company What’s Working Well

• Current process provides valuable checkpoints• Organizational focus on testing• Pockets of good practices for requirements definition,

architecture, quality and supporting disciplines• Commitment to follow the SDLC• Early prototyping supports requirements visualization• Beginning to enable data governance

IBM AND BIG BOX COMPANY CONFIDENTIAL – FOR INTERNAL USE ONLYJune 15, 2010 Page 11

Big Box Company Representative Challenges

1. Timing, Accountability and Collaboration between Business and IT needs to be optimized

2. Requirements Definitions techniques are applied inconsistently

3. Inflexible application of SDLC and Gating process

4. Access and identification of reusable content is limited

5. Manually intensive software development process

6. Requirements lack enough detail for test

7. Developer test is incomplete

8. Test Cases are not consistently traced

9. Builds are manual and inconsistent

10.Architecture Governance stops at Gate 2

IBM AND BIG BOX COMPANY CONFIDENTIAL – FOR INTERNAL USE ONLYJune 15, 2010 Page 12

Big Box Company Challenges: Identifying Gaps

1) Timing, Accountability and Collaboration between Business and IT needs to be optimized

• Inconsistent implementation

2) Requirements Definitions techniques are applied inconsistently

• Wide variation in usage

IBM AND BIG BOX COMPANY CONFIDENTIAL – FOR INTERNAL USE ONLYJune 15, 2010 Page 13

Big Box Company

4) Access and identification of reusable content is limited

• Project-centric focus

3) Inflexible application of SDLC and Gating process

• Impacts ability to respond to change

Challenges: Identifying Gaps

IBM AND BIG BOX COMPANY CONFIDENTIAL – FOR INTERNAL USE ONLYJune 15, 2010 Page 14

Big Box Company

6) Requirements lack enough detail for test

• Additional work rather then using current artifacts

5) Manually intensive software development process

• Limited automation and integration

Challenges: Identifying Gaps

IBM AND BIG BOX COMPANY CONFIDENTIAL – FOR INTERNAL USE ONLYJune 15, 2010 Page 15

Big Box Company

8) Test Cases are not consistently traced

• Not all test cases traced to original requirements

7) Developer test is incomplete• Limited implementation of test

frameworks and build integration

Challenges: Identifying Gaps

IBM AND BIG BOX COMPANY CONFIDENTIAL – FOR INTERNAL USE ONLYJune 15, 2010 Page 16

Big Box Company

9) Builds are manual and inconsistent• Very early adoption with build scripts

10) Architecture Governance stops at Gate 2

• Focused on infrastructure and not verified during implementation

Repeatable

Challenges: Identifying Gaps

IBM AND BIG BOX COMPANY CONFIDENTIAL – FOR INTERNAL USE ONLYJune 15, 2010 Page 17

Big Box Company Options: Effort vs. Value

Effort to Implement

Pot

entia

l Bus

ines

s V

alue

Engage Business

Resources Early

Requirements Management & CommonTraceability

Involve all in development of detailed design

and requirements

Establish hardware testing suites

Develop automated

testing suites

EnhanceArchitectural Governance

Design Modeling

Automate Builds

Developer Unit Testing

Enhance SDLC

Tailoring

BusinessProcess Modeling

Use Case

Consistency

Pilot incremental and iterative delivery (1)

Arch Self-Audits

Enterprise AssetMgmt (2)

Shared Vision

Notes:(1) includes right-timing requirements(2) includes shared view of requirements

Lo

w t

o M

ediu

mM

ediu

m

to

Ver

y

Hig

h

EnhanceGovernance

EnhanceEnterprise

ArchitectureEnhanceMetrics

Enhance SDLC

Training

addresses other challenges

addresses top challenges

IBM AND BIG BOX COMPANY CONFIDENTIAL – FOR INTERNAL USE ONLYJune 15, 2010 Page 18

Big Box Company Potential Inhibitors to Adoption

Inhibitor Mitigation Strategy

Difficulty accepting alternative forms of documentation and development and/or agile practices

Training and knowledge transfer

Pilot projects with alternative development approaches

Perceived initial impact of recommendations on program and project time and cost

Ensure visible sponsorship

Performance goals related to adoption of modifications

Expect a learning curve

Business/IT Collaboration Move to shared business and IT ownership of solution

IBM AND BIG BOX COMPANY CONFIDENTIAL – FOR INTERNAL USE ONLYJune 15, 2010 Page 19

Big Box Company Next Steps….

CommunicateRoadmap

Roadmap Workshop

Finalize Roadmap

Executive Summary

Prioritize options inRoadmap workshopVP’s, Core TeamIBM On-site

March 31st

IBM to Deliver Draft Roadmap

April 6th

Provide feedback To IBM on RoadmapSponsors & Core TeamConference Call

April 10th

Deliver RoadmapVP’s, Core TeamIBM On-site

April 16th

Formal Review of Draft RoadmapSponsors & Core TeamConference call

April 8th

Present ExecutiveReview PresentationSponsorsIBM On-site

April 20th Present Roadmap& Next StepsVP’s, Participants,Core Team, Directors

Late April

DeliverableKey: