The Reality of the Assessment Phase in a Consulting Engagement
So, as a Scrum Master, I often find myself grappling with an intriguing question - what does the assessment phase of a consulting engagement look like?"
Come along with me as we explore the facets of this initial consulting stage and why it might not be as rigid as we think. 🌟
Ditching the Traditional Assessment Phase? 🤔
When we step into the consulting realm, it seems almost imperative to have an assessment phase.
But here’s a thought - ideally, there isn’t an assessment phase, or not entirely that it’s asynchronous.
I firmly stand by the notion that a consultant should continually assess the needs of the business they’re working with. As we navigate the complex space where we know less upfront than we discover by doing, it becomes evident that much of what we conduct during an “assessment phase” might eventually turn out to be throwaway.
Engaging & Learning Continuously
It’s not uncommon to see customers preferring an assessment phase where we come in, assess their ongoing processes, and then decide whether to seek our help in facilitating identified issues.
However, I firmly believe there’s more value in just helping, getting started, engaging with teams, and learning the current state of the organisation through engagement. This hands-on approach brings a richness of insights and genuine understanding that may not be captured in a traditional assessment phase.
Striking the Right Balance
So, how Much is Enough? 🎯
As we contemplate the necessity of an assessment phase, a pivotal question emerges - “how much of an assessment do you need to do upfront?
And the golden rule here is to do just enough but not more.
It’s all about convincing the customer to collaborate with you and then fluidly transitioning to a stage where you can genuinely start assisting them, leaving the initial presumptions behind as they often turn irrelevant.
Dynamic Adaptations and Realisations
Reflecting upon my early years immersed in DevOps engagements in the US, I remember the emphasis on understanding and meeting the customer’s needs within a short timeframe, sometimes within a week.
This meant figuring out what the customer needs and delivering it within that window, with no room for extension. This journey taught me the necessity to continuously adapt to what’s going on once you hit the ground, embracing an agile mindset that keeps pace with evolving needs and dynamics. 🌟
Join the Wave of Agile and Scrum Learning
As we tread this path of discovery and growth, the world of Agile and Scrum beckons with promises of deeper understanding and skill enhancement.
Embark on this enriching journey through our tailored courses, where you can nurture a mindset of continuous adaptation and growth in the vibrant sphere of consulting engagements.
Smart Classifications
Each classification [Concepts, Categories, & Tags] was assigned using AI-powered semantic analysis and scored across relevance, depth, and alignment. Final decisions? Still human. Always traceable. Hover to see how it applies.
What to read next
Navigating Client Needs: How Agile Consultants Can Uncover True Value Beyond Initial Requests
Explores how agile consultants identify clients' real needs, avoid common pitfalls, and deliver lasting value by looking beyond initial …
5 critical Skills to master as an Agile Consultant? Part 1
Explores essential skills for Agile consultants, focusing on understanding client context, embracing uncertainty, learning from setbacks, …
Unlocking Agile Consulting: Transform Your Organisation with Diverse Strategies and Continuous Learning
Explains Agile consulting by highlighting diverse strategies, continuous learning, and practical ways to help organisations improve …
1 thing that sinks a consulting engagement before it starts gaining traction?
Overly detailed consulting contracts can hinder project success by limiting flexibility; focus on outcomes and value to adapt to changing …
Pragmatism crushes Dogma in the wild
Explores how practical use of Scrum fosters adaptability and resilience in teams, highlighting the value of flexibility over rigid rules in …
Detecting agile theatre with real delivery signals
Why Most Companies Operating Models Fail in Dynamic Markets
A concise comparison of Predictive and Adaptive Operating Models, explaining why traditional structures fail in dynamic markets and how …
Don’t Manage Dependencies, Remove Them
Explains why dependencies are a sign of poor system design and outlines steps to eliminate them by aligning teams, clarifying ownership, and …
The Estimation Trap: How Tracking Accuracy Undermines Trust, Flow, and Value in Software Delivery
Tracking estimation accuracy in software delivery leads to mistrust, fear, and distorted behaviours. Focus on customer value, flow, and …
Flow of Value vs Flow of Work – Misnomer or Useful Shorthand?
Compares “flow of value” and “flow of work” in Kanban, explaining why only validated outcomes count as value and stressing the need for …
Why Outsourcing DevOps Fails, and How Real Engineering Excellence Starts With Your Team
Avoid DevOps vendor lock-in, discover how true engineering excellence starts with partnership, not outsourcing. Ready to transform your …
Why Most Companies Operating Models Fail in Dynamic Markets
A concise comparison of Predictive and Adaptive Operating Models, explaining why traditional structures fail in dynamic markets and how …
Don’t Manage Dependencies, Remove Them
Explains why dependencies are a sign of poor system design and outlines steps to eliminate them by aligning teams, clarifying ownership, and …
The Estimation Trap: How Tracking Accuracy Undermines Trust, Flow, and Value in Software Delivery
Tracking estimation accuracy in software delivery leads to mistrust, fear, and distorted behaviours. Focus on customer value, flow, and …
Kendall Guide - A System of Work for AI Adoption
Flow of Value vs Flow of Work – Misnomer or Useful Shorthand?
Compares “flow of value” and “flow of work” in Kanban, explaining why only validated outcomes count as value and stressing the need for …
Estimating Better in an Overloaded System Is a Poor Man’s Strategy
High work in progress (WIP) causes delays and unpredictability; improving estimates won’t help. Limiting WIP and focusing on flow is key to …