Project Management

The Reluctant Agilist

by
2018 Digital PM Summit | 2018 North American Global Scrum Gathering | 3PVantage | Abby Fretz | Adam Weisbart | Agile | agile | Agile 2013 | agile 2014 | agile 2015 | Agile 2017 | Agile 2018 | Agile Alliance | Agile and AI | Agile Centre | Agile Certification | Agile Coach | Agile Coaching | agile coaching | Agile Estimation | Agile for Humans | Agile Layoffs | Agile Leadership | Agile Metrics | Agile Planning | Agile PM | Agile PMO | Agile Practice | Agile Project Management | Agile Retrospectives | Agile Teams | Agile Transformation | agile transformation | Agile Transition | Agile Uprising | Agile Virtual Summit | agile2014 | agile2015 | agile42 | AgileUprising | Agilist | Agilistocrats | Agility Scales | AI and Agile | Alistair Cockburn | Amitai Schleier | Applied Frameworks | Atlassian | autism | Bas Vodde | Becky Hartman | Behavioral Change | BigVIsible | BigVisible | Bob Tarne | book review | Braden Cundiff | Brandon Brown | Brett Harned | Brian Bozzuto | Bureau of Digital | Business Agility | business agility | CAL | Cara Turner | Carol McEwan | carson pierce | Center for Non-Violent Communication | Certification | Certified Agile Leadership | Certified Scrum Master | Certified Scrum Product Owner | Certified Scrum Trainer | ChatGPT | Cheif Product Owner | Chet Hendrickson | Chris Li | Chris Sims | Christine Converse | Christopher Avery | Coaching | Collaboration | collaboration | Collaboration Equation | commitment | conflict management | Connection | conteneo | Craig Larman | cross functional teams | Crosswind | CrosswindPM | CSM | CSP | CSPO | CST | Culture | DA | DAD | Dan Eberle | Daniel Gullo | Dave Prior | Dave West | David Anderson | David Bernstein | David Bland | David J Anderson | Dean Leffingwell | Declan Whelan | Definition of Done | Dennis Stevens | Derek Huether | derek huether | Design | Design Thinking | Dhaval Panchal | Diana Larsen | diana larsen | Digital Agency | Digital PM Summit | Digital Transformation | digitalpm | Disciplined Agile Delivery | Distributed Teams | Don Kim | DPM | dpm | dpm2013 | Drunken PM | drunken PM | drunken pm | Drunken PM Radio | drunken pm radio | DrunkenPM | drunkenPM | drunkenpm | DrunkenPM Radio | drunkenPM Radio | drunkenpm radio | drunkenpmradio | drunkepm | eduscrum | Elsevier | emotional intelligence | empathy | Enterprise Agile | Eric Tucker | Essential Scrum | Esther Derby | esther derby | Evolve Agility | Excella | Five Lenses of Humane Management | Fixing Your Scrum | Flow | Flow Metrics | Focused Objective | focused objective | Forecasting | Gangplank | George Schlitz | Gil Broza | Global Scrum Gathering | Grandview Prep | Howard Sublett | Improv | Improv Effect | Individuals and Interactions | Jason Tanner | Jean Tabaka | Jeff Howey | Jeff Patton | Jeff Sutherland | Jesse Fewell | Jessie Shternshus | Jim Benson | jim benson | Jira | Johanna Rothman | johanna rothman | John Miller | john miller | Jukka Lindstrom | Jurgen Appelo | Jutta Eckstein | Kanban | kanban | Kanban Pad | kanbanfor1 | Karim Harbott | Ken Rubin | Kenny Rubin | Kim Brainard | Knorr-Bremse | lacey | Language | Large Scale Scrum | Larry Maccherone | Laura Powers | LAVM | LeadingAgile | Lean | lean | Lean Agile Intelligence | Lean Agile Visual Management | Lean Coffee | Lean Kanban North America | LeanKit | LESS | LeSS | LeSS 2018 | Linda Rising | Lithespeed | Live Online | lkna | Louder Than Ten | luke hohmann | lyssa adkins | Management | Managing for Happiness | Maria Matarelli | Mark Kilby | Mark Lines | Marshall Rosenberg | Melissa Boggs | Metrics | metrics | Michael Grill | Michael Sahota | Michele Sliger | Mike Cottmeyer | Mike Vizdos | Modern Management Methods | Modus Cooperandi | modus cooperandi | Modus Institute | Natalie Warnert | Negotiation | Nic Sementa | Non-violent communication | North American Global Scrum Gathering | NVC | Obeya | Olaf Lewitz | Øredev | Øredev 2013 | organizational agility | Organizational Change | overcommitment | Pairing | Patrice Colancecco Embry | Paul Hammond | Personal Agility | Personal Kanban | personal kanban | personal productivity | personal project management | Peter Green | Peter Saddington | PMBOK | PMI | PMI Fellow | PMI-ACP | PMO | PMP | podcast | portfolio management | Precoil | Product Backlog | Product Development | Product Goal | Product Management | Product Owner | Product Ownership | Productivity | productivity | Project Management | project management | Project Management Institute | Project Manager | ProKanban | Rachel Gertz | Rally | Release Planning | Reluctant Agilist | reluctant agilist | Remote Teams | Renata Lerch | Responsibility Process | retrospective | Richard Cheng | Roman Pichler | Ron Jeffries | Ross Beurmann | Ryan Ripley | SAFE | Safety | Sallyann Freudenberg | Sanjiv Augustine | Sarah Klarich | Scaled Agile Framework | Scaling Agile | scaling agile | Scaling Scrum | Scott Ambler | Scrum | scrum | Scrum Alliance | Scrum at Scale | Scrum Certification | Scrum Gathering | Scrum Gathering 2018 | Scrum Guide | Scrum in Schools | Scrum Master | Scrum.org | ScrumMaster | self organizing teams | SGNYC20 | SGPHX | SGPHX 2015 | Shane Hastie | social engineering | Software Development | SolutionsIQ | SoundNotes | SparkPlug Agility | Sparkplug Agility | Sprint Goal | Sprint Planning | sprint planning | Story Points | Sustained Agility | Systems Thinking | TDD | Temenos | Testing Business Ideas | The Improv Effect | The Reluctant Agilist | Things | Tom Perry | Tony Johnson | Transformation | Trauma | Tricia Broderick | Troy Lightfoot | Troy Magennis | troy magennis | Trust | Untapped Agility | User Stories | value | Value Stream Mapping | Virtual Training | Vivek Angiras | Volunteering | waste | Waterfall | Weisbart | What We Say Matters | why limit wip | WIP | women in agile | Woody Zuill | XP | Zach Stone | show all posts

About this Blog

RSS

Recent Posts

Deliver Better Results with Gil Broza

Is this the Darkest Agile Timeline? with George Schlitz

Fixing Your Quarterly Planning with Nigel Baker

Advice for a Wayward Scrum Master with Jeff Howey

Is Agile Delivering The Business Outcomes You Are Looking For? with Jessica Wolfe

Categories

&Human,   reluctantagilist,  Agile Practice Guide,  Dave Prior,  Johanna Rothman,  LeadingAgile,  PMI,  reluctant agilist, 20 Hour, 2017 Digital PM Summit, 2018 Digital PM Summit, 2018 Digital Pm Summit, 2018 North American Global Scrum Gathering, 2018 Scrum Gathering, 2019 NAGS, 2019 North American Global Scrum Gathering, 2019 Scrum Gathering, 3PVantage, 4-Hour Body, 4-Hour Chef, 4-Hour Work Week, 5S, 6 Enablers of Business Agility, 7 Rules for Positive Productive Change, A Life of Productivity, a-team, Aakash Srinivasan, Aaron Irizarry, Abby Fretz, Active Listening, Adam Weisbart, Adaptivity, Adaptivity Group, ADDIE, Adding Work to Sprints, Adrenalline Junkies, Adrian Howard, Agency, AgencyAgile, Agile, Agile, agile, Agile 2013, agile 2014, agile 2015, Agile 2017, Agile 2018, Agile 2018 Keynote, AGile 2019, Agile 2019, Agile Adlibs, Agile Alliance, Agile and AI, Agile and Artificial Intelligence, Agile and Jazz, agile and lean program management, Agile and Waterfall, Agile and Waterfall Planning, Agile Antipatterns, Agile Assessment, Agile at Home, Agile Atlas, Agile Austin, Agile Baltimore, Agile Bear, Agile Business, agile caravanserai, Agile Centre, Agile Certificaiton, Agile Certification, Agile Classroom, Agile Coach, Agile Coaching, agile coaching, Agile Coaching Ethics Initiative, Agile Coaching Income Report, agile coaching institute, Agile Coaching Layoffs, Agile Cognitive Bias, Agile Conference, Agile Development and Design Techniques, Agile Digital Agency, Agile Enterprise, Agile Estimation, Agile Ethics, Agile Fluency, Agile for All, Agile for Humans, agile hardware, Agile Heretic, Agile in 3 Minutes, Agile in Digital, Agile in Education, agile in education, Agile in the Wild, Agile Layoffs, Agile Leadership, Agile Management, Agile Manifesto, agile marketing, agile marketing academy, Agile Metrics, Agile Mindset, Agile Mini Con, Agile Negotiation, Agile outside of Software, Agile Path FM, Agile Physics, Agile Planning, Agile PM, Agile PMO, agile portfolio management, Agile Practice, Agile Product Development, Agile Project Management, agile project management, Agile Project Manager, Agile Quantified, Agile Retrospectives, Agile Risk Management, Agile Roles, Agile Schools, agile schools, Agile Steve, Agile Teams, Agile Tracking, Agile Transformation, Agile Transformation, agile transformation, Agile Transformation Office, Agile Transformation Playbook, Agile Transition, Agile Tribes, Agile Uprising, Agile Velocity, Agile Virtual Summit, Agile-Lean-NYT, agile2014, agile2015, agile2015 agile 2015, agile42, Agile4All, AgileAI, AgileBrain, AgileClassroom, AgileCraft, AgilePathFM, AgileScout, AgileUprising, Agilist, Agilistocrats, Agilitrix, Agility Prime Solutions, Agility Scales, AgilityScales, AI Agile Guy, AI and Agile, AI and Scrum, Ainsley Nies, Al Goerner, Al Goernor, Al Shalloway, Alan Dayley, Alex Brown, Alistair Cockburn, Amitai Schleier, Analytics, Anderson Diniz Hummel, Anderson Hummel, Andreas Schliep, Andrew Leff, Andrew Stellman, Andy Jordan, Andy Repton, Angela Harms, Angie Stecovich, Anna Beatrice Scott, Anti-pattern, Antipattern, Antipattern. Agile, Anu Smalley, Applied Frameworks, Applying Metrics for Predictability, Archetype, Art of Coaching, art of war, Artificial Intelligence, Assumptions, Assumptions Mapping, Atif Rafiq, Atlassian, Atlassian Analytics, Atlassian Experience Canvas, Audreww Tara Sahota, autism, AVS, Backlog Refinement, baker, Bas Vodde, Becky Hartman, Bees, Behavioral Change, behavioral science, Bernie Maloney, Beyond Legacy Code, Beyond User Stories, Big Consulting, Big Visible, BigVIsible, BigVisible, Billy McLaughlin, bimodal, Bjorn Jensen, Black Lives Matter, Blackie, Blake Halvorson, Bland, blocked, blockedapp, blueprint, blueprint education, Bob Payne, Bob Sarni, Bob Tarne, book review, Boozy Scrum, Braden Cundiff, Brandon Brown, Brandon R. Brown, Brent Beer, Brett Harned, Bria Johnson, Brian Bozzuto, Broza, Build Your Own Scrum, Bureau of Digital, Business Agility, business agility, Business Agility Canvas, Business Model Canvas, Business Planning, Business Portfolio Management, business value estimation, Buzzword, CAL, Canton Coders, Capala Consulting, CapEx, Cara Turner, Career Development, Career Path, Cargotec, Carol Dweck, Carol McEwan, carson pierce, Cass Van Gelder, Catherine Louis, Celeste Giampetro, Center for Non-Violent Communication, Certification, Certified Agile Leadership, Certified Scrum Master, Certified Scrum Product Owner, Certified Scrum Product Owner Scrum, Certified Scrum Professional, Certified Scrum Trainer, Cesar Idrovo, Change, Change Fatigue, Change Management, Change Management, Change Managment, Changing Sprint Commitment, Charlie Rudd, Charlotte DiBartolomeo, Charter, Chat GPT, ChatGPT, Cheif Product Owner, Cheif Scrum Master, Chet Hendrickson, Chief Product Owner, Chief Scrum Master, Chief ScrumMaster, Chief SM, ChowNow, Chris Bailey, Chris Clarke, Chris Geary, Chris Li, chris matts, Chris Murman, Chris Sims, Chris Spagnuolo, Christina Bang, Christine Converse, Christine Li, Christine Neidhardt, Christopher Avery, christopher hadnagy, Client, Climate, cnvc, Coach's Clinic, Coaches Clinic, Coaching, coaching, Coaching Certification, CodeX, Collabnet, Collaboration, collaboration, Collaboration Equation, Collaborative Teamwork, Colleen Johnson, commitment, Communication, Communication Plan, Community, Comparative Agility, Comparing Teams, Conference, Conference Proposal, Conflict, conflict, conflict facilitation as a leadership skill, conflict management, Connecting, Connection, Conscious Communication, Consulting, conteneo, coppertone, Core Cycle of Agile Product Development, Counteracting The Systemic Oppression of Traditional Development Thinking, Couple of Coaches, Cozy Juicy Real, Craig Larman, Creative Courage Summit, Creativity Safety, cross functional teams, Cross Functionality, Cross-Functionality, CrossFunctionality, Crosswind, CrosswindPM, CSM, CSP, CSP Fast Pass, CSPO, CST, cst, Cultivating Transformation, Cultural Change, Culture, Customers, Cutlefish, Cycle Time, DA, DAD, Daily Scrum, Damon Poole, Dan Brown, Dan Eberle, daniel goleman, Daniel Gullo, Darkest Timeline, Darren Petersen, Daryl Kulak, data, Data-Driven Change, Dave Prior, Dave Prior, Dave prior, Dave West, David Anderson, David Bernstein, David Bland, David Hawks, David J Anderson, David Marquet, Dean Leffingwell, Dean Stevens, Decision Making, Declan Whelan, Decoupling Cadences, Definition of Done, Delivery, Delivery Better Results, Denise Jacobs, Dennis Stevens, Derek Heuther, Derek Huether, derek huether, Descaling Agile, Design, Design Thinking, Designing Together, Devin Hedge, DevSecOps, Dhaval Panchal, Diana Larsen, diana larsen, Digital Agency, Digital PM Summit, Digital Pm Summit, Digital PM Summit 2014, Digital Project Management, Digital Transformation, digitalpm, digitalpm dpm, Directing, Disciplined Agile, Disciplined Agile Certification, Disciplined Agile Delivery, Disciplined Agile Framework, Discover to Deliver, Discovery Curves, Distributed, Distributed Team, Distributed Teams, Distributed teams, Diversity, Dom Price, Don Gray, Don Kim, Don McGreal, DPM, dpm, DPM 2014, DPM 2017, DPM Philly, DPM Summit, DPM Summit 2017, DPM Summit 2018, dpm2013, Dr. Rick Brinkman, DragonForceSUCKS!, Drunken PM, drunken PM, drunken pm, Drunken PM Radio, Drunken PM radio, drunken PM Radio, drunken PM radio, drunken pm radio, drunken pm radio, DrunkenPM, DrunkenPm, drunkenPM, drunkenPm, drunkenpm, drunkenpm, DrunkenPM Radio, drunkenPM Radio, drunkenPM radio, drunkenpm radio, drunkenpmradio, drunkepm, ducks, Eastern Standard, eckstein, edu scrum, Education, eduscrum, Edward Kay, Eight Shapes, Elizabeth Harrin, Elizabeth Hendrickson, Elizabeth McClellan, Ellen Gottesdiener, Elsevier, Elusive Agile Enterprise, Emily Epstein, emotional intelligence, Emotional Science, empathy, employment, Empowerment, english heritage, Enterprise Agile, epic bedtime story, Eric Tucker, Erich Hahn, Erika Lenz, Essential Scrum, Esther Derby, esther derby, Estimating, Ethics, EVEF, Even Better Podcast, Evernote, Every Voice Engaged, Evolve Agility, EvolveAgility, Excella, excella, Excella Consulting, Executive Coaching, Experience, Experience Map, Experiments, Explore It!, extreme manufacturing, Extreme Programming, Facilitation, fading problems, Failing Sprints, Fearless Agility, FearlessAgility, field guide, Film Making, Film Production, First 20 Hours, First15, Fit for Purpose, Five Lenses, Five Lenses of Humane Management, Fixing Your Scrum, flavio steffens, FLEX, Flight Levels, FLIP, Flip, Flow, flow, Flow Metrics, Focused Objective, focused objective, FocusedObjective, Forbes, Forecasting, Formula Ink, FormulaInk, Frank Vega, Fred George, Frederick Taylor, freudenberg, Funding, Future of Agile, Games, Gangplank, Gary Gagliardi, gender bias, Gene Bounds, generation agile, Geoffrey Moore, Geographically Distributed Teams, George Floyd, George Schlitz, George Schlitz, Gil Broza, Giora Morein, girl scouts, Girls Guide to PM, girlscouts, Github, Glassel Ventures, Global Congress, Global Scrum Gathering, Global Scrum Gathering Austin, Grandview Prep, Greenhopper, growth mindset, Habit, HappyCog, Harvard Business Review, HBR, Head First Agile, Healing Container, Hearst Digital Media, Heart of Agile, High-Performing Team, Homeschooling, Hong Li, Hope Schools, Howard Sublett, HUGE, HUGE Inc, Human Resources PM, Human Side of Agile, Hummingbird Agility, Hybrid, hybrid, Hybrid Agile, Hyderabad, hyperfocus, I Think Therefore I Plan, Iain Fraser, ICAgile, Ice Breaker, Ideation Framework, Ignite, Igniteii, Ilker Demirel, Implementing Scrum, Improv, Improv Effect, ImprovEffect, Improving Scrum.org, improvisation, Increment of Work, independent consulting, Individuals and Interactions, InfoQ, infrastructure, Innovation, innovation games, Insighttimer, InspireMe!, Insurgent Agility, Insurgent Pictures, Intent Based Leadership, International Consortium for Agi, Introvert, intuition, IT Funding, IT Strategy, it's not all about me, IT-Agile, J.B. Rainsberger, Jabe Bloom, Jack Skeels, Jacquelyn Talpalar, James Gifford, James Grenning, James Tamm, Jardena London, Jargon, Jason LIttle, Jason Tanner, Jasper, Jean Tabaka, Jed and Sophia, Jed Lazar, Jeff Howey, Jeff Patton, Jeff Sutherland, jellybend, Jennifer Tharp, Jenny Greene, Jerry Weinberg, Jesse Fewell, Jessica Katz, Jessica Kerr, Jessica Small, Jessica Wolfe, jessica wolfe, Jessie Shternshus, Jill Paul, Jim Benson, jim benson, Jim Elvridge, Jim Tamm, Jimi Fosdick, Jira, Jira Insights, JJ Sutherland, Joe Justice, Joe Vallone, Joel Norman, Johanna Rothman, johanna rothman, John Cutler, John D Cook, John Le Drew, John Miller, john miller, John Rudd, John Tanner, Jorgen Hesselberg, Josh Wexler, Journey to Enterprise Agility, Juan Banda, Judith Lasater, Judy Neher, Jukka Lindstrom, Jurgen Appelo, Justin Handler, Justin Koke, Jutta Eckstein, kamal manglani, Kanban, Kanban, kanban, Kanban Certification, Kanban Metrics, Kanban metrics, Kanban Pad, kanbanfor1, karen prior, Karim Harbott, Kate Sullivan, Katherine Kirk, Kelly Harris, Ken Rubin, Ken Schwaber, Kenny Rubin, kevin mitnick, Keynote, Kid Cedek, Kim Brainard, Knorr-Bremse, Krista Pierce, Kyle Macey, L. David Marquet, lacey, LAI, Lance Hammond, Language, Language is a virus, Large Scale Scrum, Larissa Scordato, Larman, Larry Maccherone, Larsen, Lasater, Laura Powers, LAVM, Layoffs, Lead Without Blame, Leadership, Leadership, Leadership Gift, Leadership Gift Program, Leadership is Language, Leadership Mindset, Leading Change, LeadingAgile, Lean, lean, Lean Agile Intelligence, Lean Agile Visual Management, Lean Coffee, Lean Kanban North America, Lean Kanban University, lean metrics, Lean Startup, Lean Systems Engineering, Lean-Agile, Lean-Agile Visual Management, LeanAgile Intelligence, LeanCoffee Meetings, Leanintuit, LeanKit, Lee Lis, Leffingwell, lego game, LESS, LeSS, LeSS 2018, Lessons Learned, Lia James, lie to me, Lifestyle Design, Liftoff, Linda Rising, Lisa Hershman, Listening, Lithespeed, Live Online, lkna, Lothar Schubert, Louder Than Ten, louder than ten, Lounder>10, LSE, Luis Garcia, Luke Hohman, luke hohmann, Lullabot, Lyssa Adkins, lyssa adkins, Macromanagers, Magennis, Major League Baseball, Malena Jacobsen, Manage Others, Manage your Organization, Manage Yourself, Management, Managing for Happiness, Managing Multiple Projects, Managing the Unmanagable, Managing Up, Manny Gonzalez, Manoj Vadakkan, Marc Johnson, marcello scacchetti, Maria Matarelli, Mario Melo, Mark Crowe, Mark Hodgdon, mark inside, MARK KILBY, Mark Kilby, Mark Lines, Mark Price Perry, Marketing and Sales, marketing user stories, Marshall Rosenberg, marshamallow challenge, Marty Bradley, Mary Kaufmann, Mastodon Consulting, matt barcomb, Matt Payton, MBOK, McGraw-Hill, Measuring Agile, Meditation, Meghan McInerny, Melissa Boggs, Melissa Watts, Mentoring, Merchi Reyes, MetalToad, Metrics, metrics, Metrics Cookbook, Michael de la Maza, Michael Grill, michael lewis, Michael Sahota, michael spayd, Michael Tardiff, Michael Tibbert, Michele Sliger, Michelle Dennis, Mickey W. Mantle, Mid Sprint Review, Mid-Sprint Review, MidSprint Review, Mika Trottier, Mike Anderson, Mike Caddell, Mike Cottmeyer, Mike Griffiths, Mike McCalla, Mike Monteiro, Mike Vizdos, Millenial, Minneapolis Scrum Gathering, mistakes, mitch lacey, MLB, MMM, Mob Programming, mob programming, Mobbing, Mode 0, Mode 1, Mode 2, Modern Management Methods, Modus, Modus Cooperandi, modus cooperandi, Modus Institute, Molood Ceccarelli, moneyball, Monte Carlo Analysis, Monte Carlo Simulation, motivational interviewing, Munich, MVP, NAGC, Nanette Brown, Natalie Warnert, Negotiation, neuro-diversity, Neurodiversity, Neuroinclusivity, neurolinguistic programming, New York Times, Nic Sementa, Nigel Baker, ninja, ninja baker priest, NLP, No, No Estimates, Non Violent Communication, non-fiction, non-fiction writing, Non-violent communication, Nonviolent Communication, noop, North American Global Scrum Gathering, Not a Cylon, NVC, O3 World, Oakbay, Oakbay Consulting, oakland a's, Obeya, Object-Oriented Data-Driven Change, off shore, Offshoring, Olaf Lewitz, Olav Maassen, OnAgile 2017, one shiny object, OnPay, Øredev, Øredev 2013, Organizational Agility, organizational agility, Organizational Change, Organizational Change, organizational change, Organizational Design, Outcome Based Planning, Overcomitment, overcommitment, Overplaying, PAC, Pairing, Pam Corbin, Parikshit Basrur, paris, Patrice Colancecco Embry, Patrice Embry, patrice embry, Paul Argiry, paul ekman, paul f. kelly, Paul Hammond, Pebble Post, Peopleware, Performance, persona, Personal Accountability, Personal Accountability Teams, Personal Agility, personal agility canvas, Personal Kanban, personal kanban, Personal Productivity, personal productivity, personal project management, Personas, Persuasion, Peter Beck, Peter Green, peter green, Peter Saddington, Peter Stevens, Philadelphia, Philamade, Philip Diab, Phoenix, PI Planning, pk, Planning, Planning Poker, play, PMBOK, PMI, PMI ACP, PMI Agile Practice Guide, PMI Board of Directors, PMI Fellow, PMI Global Congress, PMI-ACP, PMO, PMP, PMP vs Agile Project Manager, podcast, Poker Planning, Portfolio Management, portfolio management, Portfolios (PPM), Post Agile, Post-Agile, Post-SAFeism, Power of Focus, Power of No, Precoil, predictability, Presentation, Presenting, priest, Principles of Scientific Management, Prioritization, Prioritizing Work, Probabilistic Forecasting, Produce Backlog Item, Product, Product Agility, Product Alignment, Product Backlog, Product Backlog Refinement, Product Design, Product Development, Product Funding, Product Goal, Product Innovation, Product Management, product management, Product Manager, product manager, Product Outcomes, Product Owner, product owner, Product Ownership, Product Ownership Strategic Priority, Product Positioning, Product Roadmap, Productivity, productivity, Productivity Project, Professional Development, Professional Kanban Certification, Professional Scrum Master, Professional Scrum Product Owner, Program Management, Programs (PMO), Project CodeX, project empathy, Project Funding, Project Management, project management, Project Management for Humans, Project Management Institute, Project Management Rebels, Project Manager, project manager, Project Managment, project portfolio management, Project Review, project risk, ProjectManagement.com, Projet Chartering, ProKanban, Proxy Interviews, PSM, PSPO, PTSD, Public Speaking, QA Manager, Qcon, Quality, Quality of Life, Quarterly Planning, Questions, Rachel Gertz, rachel gertz, rachel howard, Radical Collaboration, Radtac, Rally, Rapid Testing Business Ideas, Ray Lewallen, Reaktor, real options, Rebecca Wirfs-Brock, Recess, Redefining the PMO, Redefining Your PMO, redkiteproject, REE, Reese Schmit, Release Planning, Reluctant Agililist, Reluctant Agilist, Reluctant Agilist, reluctant Agilist, reluctant agilist, Remote, Remote Facilitation, Remote Forever, Remote Forever Summit, Remote Learning, Remote Team, Remote Teams, remote teams, RemoteForever, Renaissance Enterprise, Renata Lerch, Resiliency, Resource Management, Responsibility Process, retrospective, retrospectives, review, Ricard Vargas, Richard Cheng, richard cheng, Rick Brinkman, Right Environment Exercises, Risk, Robert Sfeir, robin dreeke, Roman Pichler, Ron Jeffries, Ron Lichty, Ronica Roth, Rosenberg, Rosetta Agile, RosettaAgile, Ross Beurmann, rothman, Russell Healy, Ryan Ripley, SAFE, SAFe, SAFe Summit, Safety, Sal, Salary, Salary Negotiation, Sallyann Freudenberg, sallyanne freudenberg, Sam Barnes, San Tsubota, Sanjiv Augustine, Santa Pays it Forward, Sarah Goff-DuPont, Sarah Klarich, Sauce Labs, Savannah Rayat, Saying No, Scaled Agile Framework, Scaling, Scaling Agile, scaling agile, Scaling Scrum, scatter focus, scatterfocus, schmonz, Schmonz.com, School of Rock, Science of High Performing Teams, Scientific Management, Scott Ambler, Scott Bellware, Scott Dunn, Scott Sehlhorst, Scrum, Scrum, scrum, Scrum Agile Transformation, Scrum Alliance, Scrum and AI, Scrum Artifacts, Scrum at Scale, Scrum Certification, Scrum Certified Scrum Trainer, Scrum Educational Units, scrum field guide, Scrum Fieldbook, Scrum Gathering, scrum gathering, Scrum Gathering 2018, Scrum Gathering Dublin, scrum gathering paris 2013, Scrum Guide, Scrum in Education, Scrum in Realty, Scrum in Schools, Scrum Inc, Scrum Labs, Scrum Master, scrum master, Scrum Master Antipatterns, scrum metrics, Scrum Team, Scrum Trainer, Scrum vs. Kanban, Scrum.org, Scrum@Scale, ScrumAlliance, ScrumatScale, Scrummando, ScrumMaster, Scrummaster, ScrumMaster Scrum Master, self organizing teams, Servant Leader, servant leadership, SEUs, SGNYC20, SGPHX, SGPHX 2015, Shane Hastie, Shannon Carter, Shit bad Scrum Master's Say, Showing Up, Sinikka Waugh, SIQ, situational leadership, Six Enablers of Business Agility, Snehal Talati, Social Change, social engineering, Software Development, Software Testing, Solutions IQ, SolutionsIQ, SONSI, Sophia Lazar, Soulful Transformation, SoundNotes, Spark Plug Agility, SparkPlug Agility, Sparkplug Agility, Speaking, speedboat, Sprint, Sprint Backlog, Sprint Commitment, Sprint Forecast, Sprint Goal, Sprint Length, Sprint Planning, sprint planning, Sprint Review, Sprints and Milestones, Square, Staffing, Steffan Surdek, Stellman-Greene, stephen forte, Stephen Younge, Steve Elliott, Steve Holyer, Steve Winters, Steven Martin, steven slade, Stewart Copeland, stonehenge, Story Mapping, Story Points, Story Points Are Trash, Storylines, Strategic Funding, strategy, Strategyzer, stress, Sun Tzu, Supply Chain, Sustained Agility, Suzanna Haworth, Suze Haworth, Swarming, Systems Thinking, Tabaka, TAC, tactical, tactics, takedown, Tall Projects, TaskTop, tastycupcakes, Taylorism, TDD, Team Building, Team Charter, Team Performance, Team Size, Team Structure, Teams, teams in crisis, Technical Debt, Technical Health, Technical Lead, Technical Manager, Technical Program Manager, Technical Project Manager, Temenos, Template Zombies, Tera Caldwell Simon, Test Drive Development, Test Driven Development, Test Obsessed, Testing Assumptions, Testing Business Ideas, The Agile Path, the airplane game, The Art of War, the grifters, The Improv Effect, The Leadership Gift, The Productivity Project, The Red Kite Project, The Reluctant Agilist, The Ron, The Ticket That Exploded, Theory of Constraints, theStrayMuse Louder than Ten, Things, Think Louder, ThinkLouder, Throughput, Tim Ferriss, Tim Ferriss Experiment, Tim Lister, Tim Wise, TJay Gerber, To Be Agile, Todd Miller, Together To Gather, Tom Beurmann, Tom Mellor, Tom Perry, Tom Smallwood, tom wujec, Tonianne DeMaria, Tonianne DiMaria, Tony Johnson, Toyota, Tracking and Reporting, Training from the Back of the Room, Transformation, Transformation Blockers, Trauma, trauma, Travis Gertz, Trello, Tribes, Tricia Broderick, Troy and Abed In The Morning, Troy Lightfoot, Troy Magennis, troy magennis, Trust, TrustTemenos, Turn The Ship Around, Twitch, Tyler Grant, TynerBlain, Ukraine, Unicat, unmasking the social engineer, Untapped Agility, Upstream Work, Urs Reupke, User Stories, User Story Points, Utilization, value, Value Delivery, Value Delivery System, Value Management Office, Value Matrix, Value Stream Management, Value Stream Map, Value Stream Mapping, value stream mapping, Velocity, velocity, VersionOne, Virtual Training, Vision Statement, Visual Agile Lexicon, Visual Management, Vivek Angiras, Vizdos, VMO, Volunteer, Volunteering, Waltzing with Bears, waste, Waterfall, Weisbart, Wesibart, What We Say Matters, why limit wip, Wikispeed, William Burroughs, Wingman-SW, WIP, women in agile, Woody Zuill, Work Item Age, Worker Owned Coop, Worker Owned Cooperative, XP, XPRolo, yellowpencil, Your Clear Next Step, Yvonne Marcus, Zach Stone, zach stone, Zeldman, Zen-PM

Date

Interview with Don Kim on his Personal Kanban Practice

Don Kim is a project leader who with over 15 years of experience in program and project management. His work covers a wide range of industries, but his primary focus is in IT. Don is also an avid blogger who has posted a number of articles over the past few months about incorporating techniques from Scrum and Kanban into the management of his work at a personal level. When I learned he was using PK to manage his own work I asked Don if he would allow me to interview him to hear more about how his has been using Personal Kanban.

A link to the interview and notes on key points in the podcast are below. If you are interested in learning more about Don you can find him through his blog Project@tion (http://www.projectation.com/), or through his work on Projects At Work (http://www.projectsatwork.com/profile/donkim/) and ProjectManagement.com (http://www.projectmanagement.com/profile/donkim).

You can find the interview here: http://www.projectsatwork.com/content/podCasts/279293.cfm

The interview lasts for about 30 minutes. If you’d like to skip ahead to specific points, here are some of the key moments in the interview:

0:00 - Don explains his background and the focus of his writing for Project@tion, ProjectManagement.com and Projects at Work.

1:55  - Don's thoughts on the volume of work PMs are facing today and how it impacts their ability to get things done.

4:45 Don explains how his use of personal productivity tools has evolved and how it resulted in him reaching a point where he was spending more time creating lists of things to do than actually getting anything on those lists done.

7:30  - Don and I discuss the fact that limiting the work in progress doesn't actually alleviate the larger backlog of things that need to be done. We also talk about the psychological impact of maintaining a list of things that do not get done.

10:28 - Don explains how he uses Personal Kanban to limit his ability to do work and how it helps him stay focused on only the most critical things.

11:20 - Don's  shares his thoughts on tools for Personal Kanban and value long term planning.

13:20 - Don explains how he prioritizes his work based on goals for his goals for relationships.

15:29 - Don maintains a separation between work life and personal life. This helps help him stay focused on his goals for his personal life.

16:23 - Don's thoughts on the "reboot" of Kanban.

19:48 – Don explains how the  the "reboot" is impacting the use of Personal Kanban.

21:10 - Don explains how he responds to requests from people who would rather stick with a Gantt chart and traditional planning instead of moving towards a more transparent Agile approach.

25:05 - Don's advice for people who are struggling with managing their own personal project management.

28:57 – Where you can learn more about Don and the work he is doing.

Posted on: June 27, 2013 02:59 PM | Permalink | Comments (0)

Personal Kanban Week 9

 

Productivity Hangover

Ten minutes ago I was supposed to be writing this blog post. What I was doing instead was cleaning out the articles I have stored in Instapaper that have been in the queue for so long that they are no longer worth reading. This seemed really important at the time. And, I was actually-really supposed to be writing this blog post 30 minutes ago. But 30 minutes ago I was doing the stuff I meant to do 2 hours ago. And that is because 2 hours ago, I was still asleep because I stayed up until 3 AM trying to finish the things I had planned for the yesterday. This morning is all about the productivity hangover.

Yesterday, like most days, I planned too much into the day. There was no realistic way I’d be able to get it done given the fact that time is not quite as flexible as I’d like it to be and that I don’t have one of those boxes from Primer.

When a problem comes along... 

In working through this Personal Kanban project there is a question thing that has remained kind of an open issue for me the entire time. What about WIP? If you aren’t familiar with it, WIP stands for Work in Progress. In Kanban, the goal is to limit your work in progress in order to help maximize your throughput. Or, to put it more simply, you need to understand how much you can do at once before you start mucking things up. Once you understand that, you need to prevent yourself from taking on too much at once (and mucking things up). This also helps you understand how long it takes to get items through the system.

For the most part, the practitioners of Personal Kanban that I have spoken with have admitted that WIP is not something they pay much attention to. In speaking with them I did not dig too deeply on that topic at the time because it seemed to be non-critical. I was looking at WIP as a holdover from a more traditional approach to Kanban that had less relevance in Personal Kanban. Also, whether or not it is right or wrong, the items on my board are not sized in any way. Everything is the same, whether it is a writing a new Statement of Work, doing a load of laundry, finishing Clive Davis’s biography, or going through the legal steps of closing down a company. It is all just stuff I am trying to prioritize and do.

If you can dodge a wrench…

A few weeks ago I started working with an Agile Coach who was willing to take on the role of being my Personal Kanban Coach/Sherpa/Confessor. I am very fortunate that he was willing to take this on. The guy is brilliant and I have mad respect for him. I also can’t help but feel a bit bad for the guy. As far as being a coachee goes, I’m definitely having much with the room for optimization.

When I told him I told him I wasn’t really tracking my WIP I am pretty sure I heard him fall off his chair. The productivity guilt monster reared up and shamed me… so I recanted. I explained that I was tracking WIP …-ish. Which meant I had listed a number for WIP at the top of each of my columns and then I just wildly ignored that whenever the hell it seemed convenient…. Which was/is most of the time.

Putting the “fun” back in dysfunction

Shockingly, there are days when I can’t get everything done. Many times the reason is that I have other activities scheduled during time I would otherwise be working. I feel safe in the assumption that I am not alone in this. And yet for many of us, we somehow manage a level of delusion that permits us to plan to do work during the time we know we will be otherwise engaged. When this happens, we have these items, which we unrealistically planned, which cannot be completed on the schedule we put together. I have a master’s degree in project management and I’m deep with the Agile. I know how I am supposed to do this. I also know that how I am doing this is not healthy. I know it is not realistic. And yet it happens, over and over. I’m slowly becoming even more aware of how sharply fundamental an issue this is and how deeply and negatively it impacts my productivity. Because I do not have a clear and present awareness of my capacity and how to plan for that without exceeding it, I am always overfilling my bucket.  When I am teaching people in a work setting about how to keep from doing this, it’s easy to explain. I even have a calculator I’ve made for folks to use to help prevent them from overcommitting themselves each Sprint. But on an individual level am I really supposed to size every single thing I do and plan for doing just that and no more? That’s just not realistic.

And suddenly, just like that, I’m one of “those” students. The ones who like the ideas behind Agile, but who really need to spend some time at the Wall of Won’t.

(The teacher in me would now like to take the student in me out back now for a quick kneecapping… just for good measure.)

Sadly, I do not have a card for that on my board.

I hate when that happens.

Sherman! Time for a new Experiment!

I believe that understanding my capacity at a daily level, and planning to meet, but not exceed that capacity will allow me to complete more work each day. I believe that getting more items to a done state each day, and not leaving a lot of unfinished work on the board will have a positive impact on my ability to get work done that will further improve my productivity. I also believe that if I do not plan to do more than is possible in a day I will be better enabled to get the rest I need to be as productive as possible in future day. This is all common sense. It’s been proven over and over. We all have that voice in our heads telling us that we are special, that we can do more, that we are not bound by the normal laws of time and physics.

Yeah… not so much.

To experiment with this I am going to run two tests. First, I’m going to try the easy one … estimating ideal time for the items in my list and then also estimate my capacity. It will involve some overhead because I am going to have to do this every day, but I will try it for a week to see what happens.

The second part, which will be more challenging for me will be to try breaking my work up into pieces that are small enough to track progress on a daily basis. I’m going to run this for two weeks and then report on it.

Next week I’ll be back to the topic of software for Personal Kanban.

Posted on: April 30, 2013 11:53 AM | Permalink | Comments (1)

Individual Capacity Calculator

Note: The link to the file has been updated. It can be found here. (3-4/13)

(This is an update to my 10/28/12 post on How to Avoid Overcommitment DuringSprint Planning. )
 

For awhile now I have been using an excel spreadsheet I put together to work out the calculations I detailed in the post on avoiding overcommitment. I have also been sharing it with the students in my CSM classes. I recently updated it so that the times allocated for the different Scrum meetings is in sync with the current version of the Scrum Guide and I thought it would be a good idea to post here just in case it can be of help to anyone.
 

In case you missed the earlier post, the intention of this calculator is to help individual team members on a Scrum Team gain a better (more true) understanding of the amount of time the can realistically commit/forecast to be able to contribute to the work the team will do during a Sprint. I have found this to be very helpful for teams who are struggling with understanding their capacity.
 

An example of how this could be used in s Sprint Planning is...
 

1. Once a Scrum Team has forecasted the amount of Story Points it can expect to get through during a given Sprint based on average historical velocity.

2. And defined tasks for all the stories.

3. And estimated the ideal engineering hours required to complete each individual task.

4. And totalled up the collective ideal engineering hours required to complete all the work they are forecasting to complete in the Sprint.

5. Each team member can use this calculator to determine how much time he/she can expect to be able to contribute in the Sprint.

6. Once each team member has come up with his/her number, you would total those up to get the total amount of ideal engineering hours the Team expects to be able to working during the Sprint.

7. If the value resulting from Step 4 is greater than the value from Step 6, then you may need to reconsider the amount of work your team is forecasting to complete in the Sprint, or modify the scope (and tasks) for one of the stories.

8. If the value resulting from Step 4 is significantly less than the value resulting from Step 6, you may need to consider adding some additional stories/work into what is being forecasted for the Sprint.
 

* Some teams I have worked with have taken the additional step of applying this technique by work type within a Sprint, i.e. Development, QA, UX, etc.
 

Here is the file

 

 

This work is licensed under Dave Prior is licensed under a Creative Commons Attribution-NonCommercial-ShareAlike 3.0 Unported License.">Creative Commons Attribution-NonCommercial-ShareAlike 3.0 Unported License

Posted on: February 19, 2013 02:14 AM | Permalink | Comments (6)

How to Avoid Overcommitment During Sprint Planning

Awhile back I was working on an Agile coaching gig with Tom Smallwood. We were working with a team that moving to Scrum and was having a particularly difficult time meeting their commitments.  Stories were being estimated in Story Points using the Fibonacci sequence and they were breaking stories down into tasks that were then estimated in ideal engineering hours. Stories were (mostly) small enough to go from card on wall to potentially shippable in about 2 days. Tasks were kept to between 4 and 12 hours. Unfortunately, despite following the basic guidelines we were giving them, they were still WAY over committing each Sprint.

Tom was the first one to notice that even though they were all confident in their ability to get the work done at the end of a Sprint Planning meeting, what they were confident about was in fact, completely impossible. What was happening was that each person was assumed to have a capacity of 8 ideal engineering hours per day. Since we were working in two-week iterations, this meant each person was on the hook for 80 hours of productive working time in a Sprint. 

 

The way we addressed this initially was to ask them to plan for no more than 6 productive working hours per person each day. This helped, but it still wasn't cutting it. The problem was that each person had more that they were responsible for than just the project we were working on. (Yes, this is not ideal, but it was reality at the time.)

 

The solution we came up with was very simple and it is one I have used on every team I worked with since. It adds an extra step to the Sprint Planning ceremony, but it has been invaluable in helping teams understand their capacity and preventing over commitment. 

 

(Disclaimer - this involves using relative Story Point Estimation for Stories and Ideal Engineering Hours for Tasks. There are many who do things differently and have great success - which is awesome... what follows is just what I have found to work well for me and the teams I've worked with.)

 

What we added was a step in the 2nd half of Sprint Planning. After the team has taken the User Stories (estimated in Story Points) and broken them down into Tasks (estimated in Ideal Engineering Hours), we would go around the circle and ask each team member to estimate how many ideal engineering hours he/she could commit to being responsible for in the upcoming Sprint. One of the most critical parts of this is the idea that the commitment being made is not to the PO, but to the other members of the development/engineering team. So, if I tell my team I'm good for 35 hours, then my team can count on me to be responsible for 35 hours of task work. If I commit to that and do not contribute that amount of time, my team members will have to cover for the work I've not done. While this should go without saying, I have found it to be helpful to mention when starting this part of Sprint Planning. 

 

So, going around the circle, each team member has to be aware of how much time they can commit to contributing. This means they need to account for a lot of the things that get in their way.  

 

Here is how I normally coach people to think through this:

 

In a two-week iteration, you begin with 10 working days. However, I normally block out 1 day for Sprint Planning, 1 day for the Sprint Review and Sprint Retrospective, 1/4 day for the 8 remaining days during which the team will hold a 15 minute daily standup and 1/4 day for an Estimation/Story Meeting. While blocking out 1 whole day for Sprint Planning and 1 whole day for the Sprint Review and Sprint Retrospective meetings is more than the Scrum Guide calls for, I have found that it is more realistic to working under the assumption that the team will get little else done on those days. 

 

If the Sprint is 2 weeks long, we start with 10 working days. Once we block out the time mentioned above, we end up at 7.5 working days.

 

If we assume each person can be productive for a maximum of 6 hours per day, then:

 6 hours/day * 7.5 days = 45 

So, the absolute Maximum Possible Productive Hours (MPPH) for any individual in a two- week Sprint is 45 hours. 

 

We then ask each person to total up the amount of time they expect to lose during the upcoming Sprint to the following events that are not part of the Scrum Framework:

 

  • Standing Meetings  - recurring meetings held each week that will keep them from working on the project
  • Holiday/PTO - expected
  • Vacation/Sick time - expected or averaged
  • Medical/Dental/Other Personal Appointments - expected or averaged
  • Emergency Fixes* - average time lost per Sprint to emergencies which require them to temporarily abandon their work on the project
  • Misc. Additional Time - Any additional time they feel they should block out to address other issues, work or personal, which will inhibit their ability to contribute to the project during the Sprint

* Getting pulled away from a project to deal with emergencies that are not related to the project is a dysfunction that will impair the team's ability to realize the full benefits of Scrum. However, in several organizations I have worked with, it is a constant reality. When things break, and the money stops flowing, it's all hands on deck.

 

The total of the above is the Interruption Time (IT) that each team member must subtract from his or her   MPPH. The amount of time left is the Revised Maximum Possible Productive Hours (RMPH).

 

If the individual is only working on a single project, then the RMPH is the amount of time that individual should feel comfortable sharing with their team members as their Committable Productive Time (CPT). 

 

If the individual is split on multiple projects, then they should multiply the percentage of their time that is allocated to the project by the RMPH. They should then subtract an additional 10% from the result (for context switching) to get their Committable Productive Time (CPT).

 

Here is an example of the above...

 

Interruption Time:

  • 4 hours standing meetings
  • 8 hours PTO
  • 3 hours for dentist appointment
  • 5 hours average time lost to Emergency Fixes
  • 5 hours subtracted because I will just be returning from overseas and I expect the jet lag to have a negative impact on my productivity for a few days

Interruption Time (IT) = 25 hours

 

45 (MPPH)

- 25 (IT)

20 (RMPH) 

 

If I am split across 2 projects at 50% each...

 

20 (RMPH)

*50% allocation

10 hours

-10% (context switching)

9 hours of Committable Productive Time

 

In talking through this, it is very common to see jaws drop. However, if each person on the team is doing this, then the team will have a realistic understanding of its' work capacity in a given Sprint. While the idea of having to tell someone responsible for your performance review that in a two-week period that you can only be counted on for 9 hours of time may be scary, it is honest. If we are practicing Scrum and sticking with transparency (one of the 3 legs of Scrum), and we are being responsible to our fellow team members, this is the most responsible, transparent thing we can do. 

 

Once each team member has shared their CPT, they are totaled up and this is the Team's Committable Productive Time (TCPT). As long as the total number of estimated ideal task hours does not exceed the TCPT, then the team should feel comfortable making a commitment to the Product Owner for the Stories they will complete during the Sprint. If the number of estimated ideal task hours does exceed the TCPT, then the team may have to negotiate with the Product Owner to reduce the work being planned for the Sprint before they make a commitment. 

 

I have also seen teams break things down even further into number of hours for development, testing, etc., but what is above is typically as deep as I go with it.

 

It adds an extra step, but it helps the team members inspect and adapt their own workload and capacity. This will also better enable them to meet their commitment in a Sprint; IMHO, the benefits of this far exceed the few extra minutes it will take for a team to make sure they are not overcommitting. 

 

 

 

 

Posted on: October 28, 2012 01:28 AM | Permalink | Comments (4)
ADVERTISEMENTS
ADVERTISEMENT

Sponsors