Are you working in a SCRUM team? Do you feel like you need more information and clarity in what’s expected?
When it comes to SCRUM, there are already a number of ceremonies we attend to ensure we are delivering according to our plans.
To add more collaboration and transparency with your teams, you might consider introducing other sessions as an ‘optional to attend’.
1. Sketching Sessions
In these sessions you are inviting your team to contribute towards the design of one of your features for example, a mobile application login page.
Here you are providing an overview of what you need and then asking your attendees to team up into groups and explore different ways of designing a login page.
When you form your groups, you are armed with post-its, sharpies and paper for you to plan your design.
After a set amount of time, your group will be asked to announce your idea to the others in the room and then at the end of the session, the team get to vote for their favorite and the majority rules.
The point of this session is to extract new ideas from your team and work towards implementing these ideas and putting them to the test.
2. Consumer Research Feedback (CRF)
This session, in my opinion is an important one, but you need to be selective about who you invite to it. I’ve found that on many occasions, we should leave the developers alone to get on with their sprint tasks.
If part of your project incorporates user research, then it is really important that we do something with the feedback we get back from the consumer.
I’ve found in some instances that this has fallen by the wayside and businesses have failed to take on board feedback despite hiring researchers to go out and do the ground work.
Our end-users are potentially the make or break of our product, so we should be paying a lot of attention to their responses to a product or service we are testing with them.
A CRF session is something that is not widely considered as an Agile ceremony, but I do hope that companies can see the value in such sessions.
3. Analysis Workshops
Analysis workshops can be setup to assist key business stakeholders get on the same page and I find these workshops incredibly useful. In general, the session would need a Product Owner, a UX/UI person and a Business Analyst or SME.
The objective would be to review priority backlog items. For each user story you ensure that all scenarios from a business perspective have been considered and either accepted or rejected for delivery prior to reaching backlog refinement with the rest of the team.
This is a variation of the 3 Amigos but for the business side where we discuss the product owners priorities and clarify requirements and iron out any issues prior to them reaching the other 3 Amigos.
So there we have it, a few more ways of working that can help increase collaborative ways of working.