What’s missing in sprint planning?
Today wherever you go everyone is running to agile type SDLC rather than waterfall. I was part of agile scrum teams for the last three years. Every release in an agile world is called a sprint.
Each phase of a sprint is called a ceremony. One such ceremony is “sprint planning” where the whole agile team (i.e), the developers, the testers, the product managers, the scrum master, the business get together and scale the story. In simple layman’s terms we decide how much time, it would for the story to be ready for production.
Enough background, let me jump into sprint planning, there are various sites which offer a socket based web interface for sprint planning, but none of them was perfect. It could not pull in stories from JIRA / project management tool. It was difficult to use.
So I decided to write my own and open source it, so that you can fork/download it and deploy it for your own use within your company firewall.
The top things which I focused on building this tool is:
- Personalised — Show profile pics by integrating with your company’s employee database.
- Authorization — Provided a way for users to login using your company’s LAN.
- JIRA Integration — Pull in story description from JIRA / project management tool.
- Real time collaboration— Change story description, story points amidst planning, everyone gets the update real time without refreshing.
Planning poker tool is powered by Node, Express, Socket.IO and Materialize CSS.
Screenshots are provided below:
If you like this post, do clap.
Leave a response, if you have any comments. Reach out to me, if you have any suggestions to make this better!
Thanks for reading!
