Moving to New Processes to Collaborate With You to Deliver Product Enhancements That Matter

Moving to New Processes to Collaborate
With You to Deliver Product Enhancements
That Matter
Peter McCullough
Mainframe
CA Technologies
Senior Advisor, Product Management
MFX38E
#CAWorld

2 © 2015 CA. ALL RIGHTS RESERVED.@CAWORLD #CAWORLD
For Informational Purposes Only
Terms of this Presentation
© 2015 CA. All rights reserved. All trademarks referenced herein belong to their respective companies. The presentation provided at CA
World 2015 is intended for information purposes only and does not form any type of warranty. Some of the specific slides with customer
references relate to customer's specific use and experience of CA products and solutions so actual results may vary.
Certain information in this presentation may outline CA’s general product direction. This presentation shall not serve to (i) affect the rights
and/or obligations of CA or its licensees under any existing or future license agreement or services agreement relating to any CA software
product; or (ii) amend any product documentation or specifications for any CA software product. This presentation is based on current
information and resource allocations as of November 18, 2015, and is subject to change or withdrawal by CA at any time without notice. The
development, release and timing of any features or functionality described in this presentation remain at CA’s sole discretion.
Notwithstanding anything in this presentation to the contrary, upon the general availability of any future CA product release referenced in
this presentation, CA may make such release available to new licensees in the form of a regularly scheduled major product release. Such
release may be made available to licensees of the product who are active subscribers to CA maintenance and support, on a when and if-
available basis. The information in this presentation is not deemed to be incorporated into any contract.

Abstract
Learn about how the CA Endevor® Software
Change Manager product team enhanced their
development process to incorporate the
Ideation, Agile, and Incremental Delivery
methodologies to create and deliver the right
product features at the right time. Learn how
you can get connected with these new
processes!
Peter
McCullough
CA Technologies
Senior Advisor,
Product Management

Agenda
THE CHALLENGE, GOALS & OBSTACLES
MOVING TO NEW METHODOLOGIES
GET INVOLVED!
GLOBAL USER COMMUNITY IDEATION
ENDEVOR AGILE SCRUM PROCESSES
INCREMENTAL RELEASES
1
2
3
4
5
6

The Challenge
§ Due to the razor-sharp competitive environment, business
needs won’t wait / can’t wait
§ Vendor/application product enhancements required to meet
those business needs must be delivered fast
Publish product enhancements that matter while they still matter…

Goals to Meet the Challenge
§ The product team delivers product enhancements that:
– Meet customer’s business requirements
– Are delivered on a timely basis
– Are defect-free
– Can be installed with minimal disruption
“Deliver features that matter when it counts”

Obstacles We Faced
Our old methodologies
Lacks Flexibility
Requirements
• DARs
Development
• Specs (months)
• “Lights-out” coding
(months–years)
• QA (months)
Publication

Obstacle #1
§ Customers submit enhancement requests that are visible only
to them and CA
– Lack of visibility made enhancement’s overall value difficult to measure
§ Requests almost always seemed worthwhile and were given
the status of “future” and placed in the “to-do” bucket
§ Due to slow feature-delivery process (stay tuned), the
enhancement requests typically aged on a growing to-do list
CA DAR process

Obstacle #2
§ Waterfall development methodology (specs, code, unit test,
document, QA, Beta, publish) had two major shortcomings for
Endevor:
– The feature specifications were completed far before the feature is
delivered and will likely be outdated
§ feature value diminished
– Features were often “over-engineered”
§ development took too long and feature delivery delayed
Waterfall development methodology can’t keep up with changing requirements

Obstacle #2
§ Waterfall methodology results:
– Customers disappointed when features found to not meet their
requirements
– Engineers frustrated that their enhancements weren’t quickly adopted
– Everyone loses –
§ insufficient feature value
§ features delivered too late
§ development time not well spent
Waterfall development methodology can’t keep up with changing requirements

Obstacle #3
§ As coding and unit-testing of new features completed,
features held aside until all new release features had been
completed
§ QA tasks performed when last new feature completed
– Every question and defect required added engineering research which
delayed the process
§ Beta sites validated the new release after all QA issues fixed
– Typically few defects found -amount & quality of testing performed by
beta sites unknown
– Too late to incorporate customer feedback
Release publication process – “Waterfall delivery”

Flexible System
Ideation
• Global user
communities
Agile Scrum
• Scrum team
• Sprints
• Epics & Stories
Incremental
Release
The New Approach
Moving to new methodologies

Solution #1 - Global User Community Ideation Process
§ Global User Community Ideation component enables anyone
to submit an product enhancement idea
– Community members can comment and vote (up or down) on posted
Ideation items
– Popular ideas stand out – many positive votes and comments
– One-off ideas also stand out – no votes or comments
– Ideas are refined – broad community input clearly identifies overall
business requirements
– Product team members regularly review update Idea status, request
clarification, etc.
Gathering customer requirements

Solution #2 – Implementation of Agile Scrum
§ Agile Scrum methodology
– “People over process” (do what makes sense)
– The “team” is self-organizing and determines howto best do their
work (rather than managers pushing down)
– The “customer” is involved along the way to ensure the team is on the
right track and can tell us when the feature is ready to publish
– There is a scrum master that facilitates the team’s needs
– There is a product owner that is the voice of the customer (when the
customer is not present), responsible for the “what”
– There is a product manager that is responsible for the “why”
Development process centered on customer validation

Agile Scrum Development Methodology
§ Terms
– Scrum team
– Backlogs (product, release,
sprint)
– Scrum Master
– Product Owner
– Stories, Epics
– Points
– Story Grooming
– Sprint
§ Meetings
– Release Planning
– Story Grooming
– Sprint Planning
– Stand-up
– End-of-Sprint Review
– Sprint Retrospective
– Release Retrospective

§ The process
– A team of people work together on a “story” to deliver product
enhancements that provide a specific value to a specific user (admin,
developer, IT auditor)
– When the story is complete, team demonstrates the enhancement to
the customers and solicit comments
– Comments may be:
§ You missed the boat – start over
§ Looking good – but more work required
§ Looking good, MVP reached, I may make more requests later…
Agile Scrum helps to ensure functionality meets customers’ expectations

§ Process overview (cont.)
– The cycle restarts:
– The team takes in new stories from the backlog
– Complete and demonstrate the stories to the end user
This process continues until all planned enhancements (and subsequent
changes due to user feedback) have been deemed as complete by the
user.
§ No surprises, features only delivered when deemed ready
Agile Scrum helps to ensure functionality meets customers’ expectations

§ Scrum team roles
– Scrum master – facilitator / problem solver
– Product Owner – is the customer’s voice to the engineering team
§ Develops a deep knowledge of the customer
§ Sets priorities, sets direction
– Team members – people responsible for all phases – coding, testing,
documentation
– Agile Manager – “people manager”
– UX Designer – works directly with customers and scrum team to ensure
user experience is intuitive, useful and usable
Agile Scrum team

§ Epics & Stories
– A Story is a unit of work that can be completed during a Sprint period
– A story has an end-user (persona), request, value
“As a developer, I need Endevor to allow embedded spaces in Element names so
that I can manage my USS data files with Endevor.”
– An Epic is a large enhancement request that describes the “big picture”
and is usually broken down into smaller stories
“As an IT Auditor, I need Endevor to record all Element action activity in z/OS SMF so
that I can track all application changes at my site.”
Epics & Stories

§ A backlog is a prioritized list of Epics and Stories
– Product backlog – Epics/Stories not assigned to a Release
§ Updated when new enhancement requests are accepted
– Release backlog - Epics/Stories not assigned to a Sprint
§ Updated during Release planning – Epics/Stories taken from Product
backlog
– Sprint backlog - stories assigned to the Sprint
§ Updated during Sprint planning – Stories taken from Release backlog
Backlogs

– Story-grooming (continuous process)
§ “Ready” criteria – what needs to be known before work can begin
§ “Done” criteria – process items that must be completed before closure
§ “Acceptance” criteria – “User value” that must exist before (story value)
§ Story effort-sizing (in relative “points”) 1,2,3,5,8,13,21,etc.
– Release-planning (once per release)
– Sprint-planning (for each Sprint)
§ Team availability, velocity (story completion speed measured in Story points)
§ Stories and their point-size
Critical Agile meetings

– Daily “Stand-up” meetings
§ 15 minute daily meeting
§ Each team member reports: “what they did yesterday, what they’ll do
today” and if they have any roadblocks
§ “Parking lot”
– End-of-Sprint review
§ Demo to validation partners (customers)
– Sprint Retrospective - what went right, what can be improved, and how
– Release Retrospective
Critical Agile meetings

Solution #3 – Incremental Release Methodology
§ Incremental releases provide the means to deliver features
to customers sooner
§ Consistent with Agile methodology –
– Based on validation partners’ recommendation a feature is published
only when it is deemed ready – unlike before, a feature is not held until
all features have been completed
§ This process enables customers to derive value from the new
feature immediately
Publication & Delivery

Incremental Release Methodology
§ Incremental Releases: traditional releases - just backwards
– Same end result – GA-complete release in 18-24 months
– Different path – Incremental deliveries
§ Incremental “0” – foundation / base release
– same functions as latest GA-complete release
– V18.0.00 = V17.0.04
§ Incremental delivery 1 – n (V18.0.01, V18.0.02, V18.0.03, V18.0.04, etc.)
– Each published when validation partners declare feature(s) has “MVP”
– Published as PTFs (pre-req prior Incremental delivery PTF, pre-req published
service maintenance)
How the process works…

Incremental Release Methodology
§ Incremental Releases: traditional releases - just backwards
– GA–Complete reached when Charter, Release Plan goals met
§ When a release is designated as “GA-Complete”
– End-of-Service notification issued for current “GA-Complete” release
§ Usually 12-18 months
How the process works…

Incremental Releases (Deliveries)
MVP! (Minimum Viable Product)
V16
V17
V18
Maintenance-only
Maintenance-only
New features and maintenance
New features and maintenance
End of V16
development:
GA-Complete
New agile
feature
(GA-ready))
New agile
feature
(GA-ready)
End of V17
development
GA-Complete
End of Service
Notification
V16

Influencing Our Roadmap
Winning With CA
Agile Development
§ Submit your ideas on
communities.ca.com
§ Vote & comment on ideas
that are important to you
§ Endevor Global User
Community
– Endevor product news
– Customer-to-customer
information sharing
– Ideation forum –(submit,
vote, comment on
enhancement ideas)
Take the opportunity to influence our product development.
Help ensure that we deliver is what you need and want.
CA Communities Ideation
§ UX & Agile Development
Validation Partnership
program
– Usability Studies
– Release Planning
– Story Validation
– End-of-Sprint
demonstrations
§ Incremental Releases
§ How to register:
https://validate.ca.com
Customer Validation

Recommended Sessions
SESSION # TITLE DATE/TIME
MFT56S Continuous Delivery Case Study with Verizon 11/19/2015 @ 12:15PM
MFX34S
Advanced CA Endevor® Software Change Manager
Processor Coding Techniques: Practical Techniques to
Streamline and Simplify your Processors
11/19/2015 @ 3PM
DO4T152S
Technology Primer: Exploit New Levels of Insight,
Orchestration and Governance for Complex Application
Releases, End-to-End, with a New Continuous Delivery
Solution
11/18/2015 @ 1PM

Q & A

Moving to New Processes to Collaborate With You to Deliver Product Enhancements That Matter

Recommended

Recommended

More Related Content

What's hot

What's hot (20)

Similar to Moving to New Processes to Collaborate With You to Deliver Product Enhancements That Matter

Similar to Moving to New Processes to Collaborate With You to Deliver Product Enhancements That Matter (20)

More from CA Technologies

More from CA Technologies (20)

Recently uploaded

Recently uploaded (20)

Moving to New Processes to Collaborate With You to Deliver Product Enhancements That Matter