Hi and thank you for visiting my Blog.
Today I’m excited to share the recent updates of our Dealogikal Web 2.0 development. My dev team were able to close out our first Hardening sprint last June 11 and successfully able to fix some major and minor bugs.
Closing out our First Hardening Sprint
We held an internal review to check and verify the identified bugs together. We however, still encountered a few ones but were able to fix it right away while holding the review.
Gladly, the team decided to resume the next development and gathered together to conduct our sprint planning and identify our sprint goal for the next sprint, Sprint 16.
Sprint Process Revision
Before we got into the sprint planning, I hold a quick adhoc meeting with them and shared a new adaptation to our sprint process. The purpose of the new process focused more on team collaboration and task transperency.
Before, our sprint process was to have each dev selects their own feature they will single-handedly develop, decompose the technical tasks of that selected item and provide the working hour estimate. Whilst this approach works just about right to incrementally get where we are right now with our development of the app, I thought perhaps there is still a way to increase our team velocity, dynamics and especially, chemistry. And that is where I figured to have them work together by consolidating their effort into a single user story enough to cover at least half of the sprint.
In this way, they will collaboratively all work together. Decomposing the technical tasks, assigning the identified tasks to fellow team members, providing estimated work effort and lastly, document this information into our project management software for task transparency and fostering schedule adherence.
Having that said, the team then decided to have a dry run to this new process and it took us almost half of the day to complete at least two user stories using the new adaptation! lol. In the end, we closed out the adhoc session with a clear and shared understanding of the new process and agreed to implement it to the upcoming sprints.
What’s next
After our productive dry run session, the dev team decided to embark on our next sprint development. All together, we decided to proceed the development of the Payment and Processing section and to start developing the new user type of the application, the administrator.
Thank you for reading this blog post. I will keep you posted to our sprint planning session on the next post.
Cheers!