• Share
  • Email
  • Embed
  • Like
  • Save
  • Private Content
Value Delivery in Practice
 

Value Delivery in Practice

on

  • 1,848 views

The practices of defining success in quantifiable business terms and then managing and measuring throughout execution are essential to business success yet still the exception in our industry.

The practices of defining success in quantifiable business terms and then managing and measuring throughout execution are essential to business success yet still the exception in our industry.

Statistics

Views

Total Views
1,848
Views on SlideShare
1,848
Embed Views
0

Actions

Likes
0
Downloads
19
Comments
0

0 Embeds 0

No embeds

Accessibility

Categories

Upload Details

Uploaded via as Adobe PDF

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment
  • Setup: Open Bus. Objectives Deck, Open PT to project, Open usertesting.com to results pageI was originally going to present my talk “Value over Velocity: From Feature Building to Value Delivery” that I’ll be giving at the upcoming Agile2010 and Lean Kanban 2010 conferencesBut then two weeks ago it suddenly occurred to me that most all of you already know the Gilb’s methods and that I might bore you with material you already knowSo instead I decided to talk about how we’re applying these methods on real projects and in my company Dominion DigitalI’m very much a practitioner and not much of a theorist – perhaps this is the American in me (from Puritan Gift)But first a bit about myself…
  • My InfoMy Family:Regan, Indie, CashMy hometown: Richmond, VA (60 miles up the James River from Jamestown – the first English settlement in America and the capital of Virginia)
  • I primarily work in two roles within Dominion Digital a 50 person regional process and technology consulting companyI’m a leader in our Technology Solutions practice – formerly Architect but primarily today Engagement Management
  • I lead our ITPI practice – primarily around Agile Adoption including Agile Engineering practices for web-based products and services companiesToday I’ll discuss how we’re using Value Delivery with both types of engagements
  • Today’s working definition
  • A more practical definitionOur approach leverages the best practices of both methods
  • Value Focused – More than just working software and on-time, on-budgetQuantified Business Objectives – Focus on the end results first, not how to get thereQuantified Product Qualities – Not just ‘what’ but ‘how well’Planguage – A common way to define objectives and qualitiesImpact Estimation – In concept, but not in practice
  • Roles & Responsibilities – Product Owner, ScrumMaster, TeamIterative Delivery – Using 1 and 2 week delivery cyclesProduct Backlog – Prioritized set of things ‘to do’User Stories – Estimate-able elementary level of requirements “As a , I would like to so I can ”Release & Sprint Planning – Schedule of delivery of User Stories over timeRetrospectives – Frequent reflection on what’s working well and what’s notStand-Up Meetings – Daily team synchronizations
  • We’re primarily using Value Delivery as a means to implement Technology Solutions projectsThis includes: Web-based eCommerce and self-service solutions and collaborative platformsWe primarily work with products and services companies, Fortune 500 and progressive mid-caps in Financial Services and (increasingly) Healthcare
  • Before we could convince our clients of the approach, we first had to convince ourselvesThis has been a journey starting in 2005 when I was first introduced to Evo (after using XP since 2000)
  • I was lucky that our CEO had a background in software engineering and a progressive ideas on delivering valueStory: When Chris was a teenager growing up in Ireland he got a job working with ??. He asked if he could come in on the weekends and play with their computer and within a few weeks had written software to automate a previously tedious manual process saving the company time and money. It quickly got his bosses attention and ever since he’s enjoyed connecting technology results with business value
  • Our organization has a fairly simple Operating modelMarketing – We market our services to organizations primarily in Central VirginiaSales – During the sales process we understand not just “what” needs to be done but “why” and “how well”Delivery – In Delivery we connect our solutions with the desired business results for our clientsThis is supported by Management including myself and Jimmy as members of the leadership team helping our company grow and evolve
  • Here’s our current 2010 goals (last reviewed in May)They (including our results) are shared with the entire company every quarter at all-employee meetings
  • One of the principle ways we market our company and our services is through our mission and core valuesWe don’t compete on price, we compete on value
  • In the sales process one of the principle things we try to establish are:1. What are the desired business results (not just the features)2. What is the budget & schedule3. Is this opportunity a good mutual fit that can produce a “win-win”At times this can be difficult, especially for clients who already ‘know what they want us to build’. In fact, this is probably our biggest challenge…
  • Clients many times already have a deadline and desired scope, they just want us to ‘build it’ quickly
  • When I’m the engagement manager, I will run the Inception kick-off meetingWe use the Kickoff meeting to validate, with executive stakeholders and all project members:Our understanding of what we’re being asked to doOur understanding of the critical business objectives and product qualities (draft versions of each)The meeting helps ensure everyone from the executive sponsor to the developers are focused on the right problem and we have agreement on what’s most importantI will often ask “if we can identify other solutions to” If they agree, this sets the precedent that we can build what they’re asking for but are free to explore alternative solutions as well
  • Let’s look at a real deliverable from a client project I’m leading right nowAction: Open up Deliverable deck - explain to group what they are about to seeAction: Open up usertesting.com to review page
  • Action: Open up PT to project, explain how backlog, stories and release planning work
  • Quickly quantify objectives and qualities and track down baselines for each (within 3-4 weeks for 3-4 month release)Desire to get to Scope / Schedule / Cost figures early enough to get SoW reviewed and signed without gapEnsure client understands roles and their responsibilities throughout project
  • We use Scrum pretty much by-the-book during Delivery
  • Its easy to lose focus on Objectives once into deliveryIf baselines aren’t captured before delivery starts, we’ll move on anyway (and it can be hard to circle back around after delivery starts)Value is Delivered when the Release is in production, not each Sprint (sometimes 2-4 months)
  • Low success rate in making this Value Delivery process stick after we have finished the engagementLack of priorityinto running down actual results afterwards (both us and clients)
  • Often times when I’m working with a new client, their current software development process is so broken the idea of quantifying business objectives and product qualities is nice but not critically important to them right now. They’re just trying to ship something soon.So I pursue two strategies and at different times alternate between the two
  • First focus on “Bottom Up”: 1. Getting team to deliver software in iterative cycles with cross-functional teams 2. Getting a backlog of stories developed and laying out a release plan 3. Introducing Agile Engineering practices (CI, automated testing, refactoring, TDD)Once we’ve started to make some progress on this, transition to focus on: 1. Product Qualities – Closer to team and product owner and within their control 2. Business Objectives – Tying their work back to the broader business problem and desired resultsTell story of HRP’s adoption

Value Delivery in Practice Value Delivery in Practice Presentation Transcript

  • Value Delivery in Practice
  • Ryan Shriver | Managing Consultant | rshriver@ddig.com | theagileengineer.com | twitter: ryanshriver
  • Value Delivery in Technology Solutions
  • Value Delivery in IT Performance Improvement
  • Value is Delivered in the form of progress towards stakeholder’s objectives
  • Value Delivery = Evo + Scrum
  • From Evo: Value Focused | Quantified Business Objectives | Quantified Product Qualities | Planguage | Impact Estimation*
  • From Scrum: Roles & Responsibilities | Iterative Delivery | Product Backlog | User Stories | Release & Sprint Planning | Retrospectives | Stand-Up Meetings
  • Over half our Business and Technology consultants are Certified Scrum Masters and trained in Evo methods Our Training
  • Value Delivery in Technology Solutions
  • Convincing Ourselves Introduced to Introduced First used Defined Standardized Trained Evo at Agile Evo to our Evo with Value approach and organization Business CEO, started Scrum on Delivery as market to in Evo Conference migration to client project our approach clients methods Scrum 2005 2006 2007 2008 2009 2010
  • "In an industry where so many are challenged to build the solution right, not to mention building the right solution, Value Delivery has been tantamount to Dominion Digital's success on both fronts. The practices of defining success in quantifiable business terms and then managing and measuring throughout execution are essential to business success yet still the exception in our industry. – Chris Little, Founder and CEO, Dominion Digital
  • Our Operating Model Marketin Sales Delivery Inception g Implementation Transition Management
  • Value Delivery in Management High Level Goals Sub Goals Improve employee Develop future leaders satisfaction and motivation Better communicate career Improve revenue growth tracks and promotion process Ensure challenging project Improve delivery opportunities Improve collaboration (both Improve profitability at office and on client sites) All goals are quantified with Scales, Meters, Targets, Constraints and Baselines They are reviewed and refined quarterly by the leadership team
  • Mission and Core Values By developing healthy relationships, we establish sustainable success for the people we care most about: our clients, our employees, and our community. We are on a mission to: -Raise the industry standards for professional services consulting -Deliver high-impact business value to our clients -Remain a great place to work for our associates -Continue to serve the best interests of our community -Remain true to our core values of service, value, passion, excellence, teamwork, and respect service & value - We always act in the best interest of our clients, as measured by client satisfaction and value created passion & excellence - We do our best in every situation and set the standards for excellence in our industry teamwork & respect - We embrace individual initiative and team collaboration, such that in mutual partnership with our clients and in our communities, we are all stronger and more successful. Value Delivery in Marketing – from our web site www.dominiondigital.com/company/mission_vision.aspx
  • Value Delivery in Sales
  • Challenges in Sales – Just Do It!
  • Value Delivery in Inception
  • Inception Deliverables: Business Objectives & Product Qualities
  • Inception Deliverables: Product Backlog, User Stories & Release Plan
  • Challenges in Inception – Quickly quantify success
  • Value Delivery in Delivery
  • Challenges in Delivery - Losing Focus on Ends
  • Challenges in Transition – Making it Stick
  • Value Delivery in IT Performance Improvement
  • Value Delivery when things are broken
  • Pursuing Bottom Up & Top Down Strategies
  • Thank you Recent Papers & Presentations: Upcoming Presentations: Hyper Productive Agile Agile 2010 (Orlando, FL) Measurable Business Value - Value over Velocity Product Qualities Approach, Agile Style - Non-Functional Requirements, Agile Style Lean Kanban 2010 (Antwerp, Belgium) - Value over Velocity