Hi and thank you for reading this blog post!
Today I’m thrilled to share with you how we come about our first day of a sprint. On this post, my dev team covers on working on the first user story, out of the 5 user stories we determined on this sprint, and organized the decomposed technical tasks based on dependencies and utilized the link feature of Proj4.me to notify the owner of the linked tasks.
Moving the To-do User Story to WIP
I started the meeting by moving the first user story, enabling the admin to disburse payment, from To-do column in the Kanban Board, to WIP – work in progress. The whole team shared a common understanding about this user story during our sprint planning and decided to organize and link the technical tasks on this user story. To do that, I navigated those technical tasks in Proj4.me using the subtask board feature where it enables the user of the platform to view it in a listed manner. The user can drag and drop the card(technical tasks) and can arrange those cards based on priorities and dependencies.
We also discussed on this user story the deadline to complete it based on the sum of the total estimated hours of its determined technical tasks. Good thing, Proj4.me provides that feature where it displays the total estimated hour
After figuring out the total estimated hours of this one, we then agreed to complete all its technical tasks 4 days after day 1 of the 2 week sprint which is by July 9, 2024.
We then coursed through each individual tasks and discuss together which tasks should be organized based on its dependencies. I figured to place the creating ‘the process flow’ task card as the first to be listed on top. This task is critical for the whole team to know how this user story’s flows , its technical specification such as the table of information to be used in the API and the UI designs which is going to be basis for the front-end development.
Ace, our system analyst, selected this task and agreed to complete it within 2 hours, the estimated hours he committed during our sprint planning session.
I then linked this task to the Design Disburse List Page UI. By doing so, the owner of this design UI task will be notified when the process flow task is already moved to the Done column in the Kanban Board. This informs the design ui tasks that the process flow and tehcnical specifications are complete and is available to be used as reference for designing the Disburse List Page.
We then proceed to link the Design Disburse Page List UI to its front-end development task, the Develop Disburse list page, which is owned by our front-end developer, Janm. By doing so, Jamn will be notified via Proj4.me email notification once I completed the UI task and move the task card to the Done Column of the Kanban bard.
We then proceed to link the Design Disburse Page List UI to its front-end development task, the Develop Disburse list page, which is owned by our front-end developer, Janm. By doing so, Jamn will be notified via Proj4.me email notification once I completed the UI task and move the task card to the Done Column of the Kanban bard.
After a careful checking on the necessary task cards that needs to be in the WIP, we then checked our other team members who did not happened to have their tasks not included in this user story. One of which was our back-end developer who shared that he will be preparing the data tables and the ERD structure prior to his task schedule to have a head start and avoid cramming.
To close
This first day of Sprint 17 was critical for aligning the team. By carefully organizing the task cards based on dependencies and utilizing the link features to connect related tasks, we established a clear workflow. This approach ensures that our team can work synchronously and effectively. The use of Proj4.me has proven invaluable in managing these dependencies and keeping everyone informed and on track. As we move forward, the foundation we’ve laid today will help us meet our sprint goals and deliver quality results on time.
Thank you for following our journey, and I look forward to sharing more updates on our progress.
Stay tuned!
Sincerly,
Marvin E. Navarro