Shift Happens: Do You Have the Right Teams to Manage Work by Product?

Do new ways of working have you wondering how to structure your IT teams? As more organizations start managing work by product, some long-standing roles may become less important -- and others will become mission critical. In this talk, you’ll learn which roles are at risk and three new roles to consider for your IT organization. You’ll also learn a useful tool that helps you hire for these new roles -- by starting with your own people.

Transcript

1. @dominicad Shift Happens: Do You Have the Right Teams for Managing Work by Product? . Dominica DeGrandis Principal Flow Advisor
2. @dominicad Dominica DeGrandis @dominicad Principal Flow Advisor @ Tasktop Technologies Author of Making Work Visible: Exposing Time Theft to Optimize Work & Flow
3. © 2019 Tasktop 55% GARTNER CIO SURVEY 2019 of IT organizations are moving from project to product Source: CIO.com, Making the shift to product-based IT, January 2019
4. @dominicad What does Project to Product mean? • Product team job is to create business value. Diff than op8miza8on of scope, budget, schedule of projects. • Product teams have cross func8onal groups organized around a long term product lifecycle, not split up. • Profit center thinking (not cost center thinking). Invest in teams that bld, deliver, maintain biz value. Amazon Bestseller
5. @dominicad Good reasons for the shift: 1. Fewer dependencies 2. Making outcomes that matter visible
6. @dominicad Managing by product reduces dependencies • Projects teams form & disband - knowledge remains w/ diff team. • Product teams have more longevity, stability, and knowledge lives with same team.
7. @dominicad Teams Project Product Project 1 Project 2 Project 3 Product 1 Product 2 Product 3 People are brought to work Work is brought to People “Every dependency increases risk of starting or finishing late by 50%.” ~ Troy Magennis Interchangeable resources Knowledge workers
8. @dominicad © 2019 Tasktop Technologies Incorporated. Managing work by product fixates measures on business outcomes
9. @dominicad Provokes convs Visibility Project Product Making Value Visible Making Opinions Visible why watermelon
10. @dominicad Jobs Change Source: Future of jobs survey, World Economic Forum
11. @dominicad https://insights.stackoverflow.com/survey/2019 The Rise of the Full Stack Engineer DevOps - you build it you run it. That means you need full stack engineers, right?
12. @dominicad https://itrevolution.com/book/full-stack-teams-not-engineers/ DevOps is about enabling different teams to communicate and work better together, not eliminating the need for cross-team communication by merging teams or making one person responsible for everything.
13. © 2019 Tasktop PMO to VMO “To transition from scope based outcomes to value based outcomes, it makes sense that the PMO transition to effectively help optimize business outcomes at a program level.” ~ Kristen Biddulph Program Management Office to Value Management Office Shift gears to product thinking at the program level. Making Work Product-Centric: https://www.youtube.com/watch?v=02Pgyy-HOHQ
14. @dominicad Emerging Roles Value Stream Architect Value Stream Product Lead Product Journey Owner “Who should be on the team?”
15. @dominicad Value Stream Architect – focused on architecting the software value stream itself • Architect software value streams to accelerate flow of biz value. • Provide business-level visibility into the flow of value delivered. (PM dream) • Ensure built-in feedback occurs across value stream. • Identify data-driven CI improvement experiments
16. @dominicad Value Stream Architect An op&mizer – Studies bo3lenecks. Knowledgeable in the Theory of Constraints An influencer - They add work items to product backlogs and will need support across the organiza&on to drive change across each part of the value stream: Part consultant - consult with product mgrs/owners to drive higher level decisions about workflow tooling. ↕
17. @dominicad Platform Products Internal Customer Value Stream Network Developers & Specialists Business Products External Customer Project to Product: Architecture There cannot be a more important thing for an engineer than to work on the systems that drive our productivity -- Satya Nadela
18. @dominicad Product Journey Champion • IT business-level owner of the project to product transition • Works with executives and managers across IT and lines of business to adopt Project to Product mindset to optimize technology investments • Do Systems Thinking to scale lessons learned and patterns • Coach value stream architects, Agile & DevOps practitioners, PMO to adopt product thinking. • Dedicated coach and champion to move enterprise forward.
19. “You have a process. Are you in control of it or is it in control of you?” “Treat your delivery pipeline like a product.” ~ Carmen DeArdo
20. @dominicad Product Value Stream Lead • Intimate knowledge of the product and customers • Set objectives and measure success • Ensure staffing and skill levels • Emphasis on team happiness
21. @dominicad PVS Lead Product Manager Operational cultivation of culture of innovation and technical integrity Significant people management duties Generally no feature design Primary Flow Metrics: Flow Distribution & Flow Efficiency Prioritization, prioritization, prioritization Generally no people management duties Feature Design Primary Flow Metrics: Flow Time, Flow Load & Flow Velocity Why build this product & what outcome will it produce?” Staff team, set objectives & measure outcomes
22. Skills Matrix: Do you have the right team? [self-rate] Skill / Knowledge Sunita Cindy Srini Chris Zoe Steve Describe the desired business results for the value stream 2 1 0 1 3 2 Identify the product value stream’s customers & pain points 0 1 3 1 3 2 Locate the work process and workflow within and across tools from from intake to delivery 3 2 0 1 2 1 Find artifacts in the toolset that can be identified as revenue generation and revenue protection, 2 2 1 0 1 0 Map out the artifact states, and recognize active work states vs. waiting states 1 0 2 1 1 0 Locate where the PVS’s work items are in the various tools used by the product value stream 2 2 1 1 2 0 Identify dependencies on teams/practitioners upstream and downstream of their own functional area 2 1 0 0 1 2 Design experiments that improve efficiency and velocity, and be willing to present/share results with others 3 2 0 1 3 2 2 can be a challenge as people end up naming the orgs customers rather than the customers their PVS serves.
23. © 2019 Tasktop Debt work • Refactor so3ware component • Self-service perf tes<ng • Vendor package upgrades • Training team members • Internal team improvements • Adopt new tools to automate & manage work Investments to improve flow or pay down future issues Improvement of Daily Work
24. @dominicad The Five Ideals The First Ideal: Locality and Simplicity The Second Ideal: Focus, Flow, and Joy The Third Ideal: Improvement of Daily Work The Fourth Ideal: Psychological Safety The Fifth Ideal: Focus on our Customer Enable improvement
25. © 2019 Tasktop Skills matrix: Making Gaps Visible Avoid a2ri4on Help people shi: gears Discover product-centric knowledge/skill gaps Level-up knowledge to support new WoW.
26. @dominicad Takeaways • Product Management & Profit Centers are the future model for success • New emerging roles offer opportunity for career growth • Reinvent & elevate your knowledge
27. Email: dominica@SendYourSlides.com Subject: flow To receive: • copy of this presentation deck • Skills Matrix: Do you have the right team? • Full Stack Teams, Not Engineers • Flow 101 workshop info • Value Stream Canvas exercise • Tasktop tool integration video on ServiceNow & Jira • excerpts of Making Work Visible • Forrester report on Value Stream Mgmt