First day of development

We have started developing a new tool for pest control. We showed our web developers the list of work we need to complete, which we have written as user stories. This is a way of keeping the customer at the centre of our work when setting out requirements. An example of a user story would be:

“As a resident needing help with pests,

I need to be able to book an appointment at a time that suits me,

so I can get rid of the rat that eats all the Doritos.”

The team then divided into pairs to build different sections of work addressing these user stories. We tried to build an initial form for customers to request help with pests, to book an appointment and to be able to pay.

the-team-divided-into-pairs
The team divided into pairs.

We encountered stumbling blocks, of course, but we were expecting that on day one of development. Some documentation wasn’t clear, and some connectivity didn’t quite work between databases. On Agile projects like ours, there is a role called scrum master who supports the product manager and development team by taking any problems away and finding solutions. Gary Duckworth is our scrum master and is doing an amazing job. I think he must be hiding some sort of time travelling ability. There is no other explanation for how problems get solved so quickly!

The combination of experienced software developers and excellent scrum-mastery has meant we also had some success. There was an upbeat air to the room and a lot of clever technical conversation going on around me.

v-happy-with-our-first-day-building-results
Admiring our results at the end of a very promising first day.