My first scoping session

I recently held my first scoping session.  On reflection, it went pretty well and was a decent start, where I gained much insight into the goals of the project, and also gave me some learnings that I can focus on for improvement in the future.

I'm partnering with Pivotal Labs to help with the transformation to an agile company and to learn about the Product Manager role.  The project I'm working on has had a  lot of great user research and analysis already conducted, with a prototype build to gather user feedback and help clarify what it truly needed to satisfy our goals.  This all occured outside of CompoZed (the transformation group within my company) so the people driving that effort are key stakeholders.

Positives

Decisive

XP Scoping sessions are decisive!   Starting with the goals and getting a shared understanding of what the project is aiming to deliver ensures a razor sharp focus.  For me this meant a discussion about the prototype and how it addressed several different problems, and then getting agreement on which one we would focus on for now.  The focus is very much on what we can do and how we can deliver real value - based on our understanding at this point in time of what is valuable.

Speed of progress

Scoping sessions are a great means of moving quickly, getting buy in from business stakeholders and technology, and reaching a common understanding.  They exude progress and positivity.

Engaging and Stimulating

Scoping sessions generate a lot of energy.  They build excitement.  My first words after the meeting ended were "This is a great project!"  Everyone in my location came away enthused and excited - primarily because we can see action and progress to address a real issue, and believe we will deliver quickly to address that issue.

Learnings

Involve all stakeholders

The scoping session didn't include all stakeholders.  Several different stakeholder areas were included, but not all.   This was due to scheduling restrictions and the time frames I've had to work within, and its far from ideal.  It will require additional work to engage other stakeholders, and there is the issue that they have not all discussed things together in one big group - so there is the risk of divergent understandings and priorities.  I'll have to manage this and mitigate it as I go.

Personas

I didn't flesh out all the personas - due to the compressed timeframe of the meeting.  Whilst the stakeholders present were familiar with the various impacted user groups, personas could have uncovered further goals or points that needed consideration.

Didn't capture assumptions and questions

This is a biggie.  I largely missed this, and it will require me to circle back to stakeholders to clarify and ensure we've a shared understanding of what assumptions there are.  I'll also need to seek answers from our stakeholders.

Risk List seems short

So the elephant in the room was our dependency upon legacy systems and the speed at which they can implement services we require to deliver our minimum viable product.   Beyond that, we seem to be light on risks.  This smells of inexperience to me!

Not very interactive

Scoping sessions often involve lots of scribbling on post its, cards, etc and engage everyone very interactively.  My scoping session was split across multiple locations with only an audio link up between them - not even video.  Whilst some in my location were capturing stuff on post its and cards, I didn't refer to them or engage in any prioritisation.

Summary

All in all, I know a lot more about the project, and I gained that insight faster than traditional company methods.  Plenty of scope for improvement in future scoping sessions (and I can refer to this list in the future to guide me on where I need to focus my efforts).