Plan better sprints
One of the most common traits you will find in successful companies is regular product updates. A trait that requires the discipline of proper planning. In this article, we will be covering how we improved sprint planning and meet targets at Juvoxa by introducing RFCs in the process.
What is an RFC?
An RFC, short for Request for Comment, is a document designed to help team members propose a solution to a problem and get feedback on that proposal. An RFC is used to drive clarity and consensus.
Problems
Not having an RFC in the planning process results in the developers thinking of a solution in their mind, giving a rough estimate and start coding. More often than not, during the implementation, unknowns start to uncover and they result in the deployment getting pushed. Estimations also take a hit because something that was expected to take X hours ends up taking >>X hours. Sometimes, even after the solution was implemented, the developers have to redo the work because of stakeholder expectation mismatch as the requirements were not properly understood. Since nothing is written, it also becomes difficult to refer to critical decision points.
How does it help?
Including an RFC in the process forces the developers to type the problem and the solution. When you write, you get more clarity and more edge cases start to unfold, handling which starts to improve the solution. Writing also improves the critical thinking of a person. Having a detailed RFC ensures that the authors have understood the problem well and the peer review process ensures that there is consensus amongst the team on the solution proposed.
This also indirectly results in proper task estimations as the developers would have greater clarity and understanding.
How it fits in?
At Juvoxa, we first create a PRD (Product Requirements Document) that gives a high-level overview of the problem and the expected user experience. Designs are then created for the same. After which, the backend and the frontend team create the RFCs. The RFCs then go through the review process and once they are approved, tickets/issues are created with estimations and actual coding starts. (*tell us in the comments if you would want us to write an article on the full process as well)
Template
You can find the RFC template embedded below. If it does not load, click here.
Feel free to use the template as needed. Do share in the comments how you adapted the template to your need and integrated it into your company’s processes.
Feel free to use the template as needed. Do share in the comments how you adapted the template to your need and integrated it into your company’s processes.
Think you can help us improve the planning process? Come join us! Juvoxa is hiring. Send an email to hr@juvoxa.com.
