tech·nic·al·ly agile

Adventures in Scrum: Lesson 2 - For the record

Explore key lessons from our first Scrum Sprint at SSW, uncovering the importance of clear communication and alignment in Agile practices. Join the journey!

Published on
2 minute read
Image
https://nkdagility.com/resources/ycDsUu_-hNR

At SSW we have always done Agile. Recently we have started doing Scrum and we have nearly completed our first Sprint ever using Scrum. As you probably guessed from my previous post, it looks like it is going to be a “Failed Sprint”, but the Scrum Team (This includes the ScrumMaster and the Product Owner) has learned a huge amount about working in the Scrum Framework.

Update 16th March 2010


We have been running with a “Proxy Product Owner” for the last two weeks, but a simple mistake occurred either during the “Product Planning Meeting” or the “Sprint Planning Meeting” that could have prevented this Sprint from failing. We has a heated discussion on the vision of someone not in the room which ended with the assertion that the Product Owner would be quizzed again on their vision. This did not happen and we ran with the “Proxy Product Owner’s vision for two weeks.

Product Owner vision: Update Component A of Product A to Silverlight

Proxy Product Owner vision: Update Product A to Silverlight

Do you see the problem?

If the people who tell you what to do don’t agree with the people who evaluate what you are doing, you’re stuffed. – Kent Beck 

Worse than that, as we had a lot of junior members of the Scrum Team and we are just feeling our way around how Scrum will work at SSW I missed implementing a fundamental rule.

That’s right, it was me. It does not matter that I did not know about this rule, its on the site and I should have read it. Would a police officer let you off if you did not know that a red light meant stop? I think not…

But, what is this amazing rule I hear you shout..

Its simple, as per our rule I should have sent the following email:

“ Dear Proxy Product Owner,

For the record, I disagree that the Product Owner wants us to ‘Update Product A to Silverlight’ as I still think that he wants us to ‘Update Component A of Product A to Silverlight’ and not the entire application.

Regards

Martin”
- ‘For the record’ - Rules to being Software Consultants - Dealing with Clients 

This email should have been copied to the entire Scrum Team, which would have included the Product Owner, who would have nipped this misunderstanding in the bud and we would have had one less impediment.

Technorati Tags: SSW    Scrum    Silverlight 

Software Development Agile Project Management People and Process Scrum Team Software Developers Agile Frameworks Scrum Product Development Agile Planning Agile Product Management Product Delivery

Related blog posts

No related videos found.

Connect with Martin Hinshelwood

If you've made it this far, it's worth connecting with our principal consultant and coach, Martin Hinshelwood, for a 30-minute 'ask me anything' call.

Our Happy Clients​

We partner with businesses across diverse industries, including finance, insurance, healthcare, pharmaceuticals, technology, engineering, transportation, hospitality, entertainment, legal, government, and military sectors.​

Genus Breeding Ltd Logo
Hubtel Ghana Logo
Boxit Document Solutions Logo
Schlumberger Logo
Flowmaster (a Mentor Graphics Company) Logo
Epic Games Logo
Slicedbread Logo
Boeing Logo
Deliotte Logo
Akaditi Logo
Xceptor - Process and Data Automation Logo
Cognizant Microsoft Business Group (MBG) Logo
Lockheed Martin Logo
Higher Education Statistics Agency Logo

CR2

MacDonald Humfrey (Automation) Ltd. Logo
Trayport Logo
Emerson Process Management Logo
Washington Department of Enterprise Services Logo
Washington Department of Transport Logo
Nottingham County Council Logo
Department of Work and Pensions (UK) Logo
Ghana Police Service Logo
Royal Air Force Logo
Lean SA Logo
Lockheed Martin Logo
MacDonald Humfrey (Automation) Ltd. Logo
Flowmaster (a Mentor Graphics Company) Logo
Kongsberg Maritime Logo
New Signature Logo