We follow the core Agile practices, conduct regular ceremonies and maintain all the artifacts. We have also evolved this with our own learning to make better use of Agile objectives- rapid and customer-centric development. this is illustrated against each of ceremonies that we conduct, below
Sprint planning meeting- We split this into ‘the Requirement Elicitations Meeting’, ‘design meetings’ and ‘the design review meetings’
This has been done to ensure coming delivery is absolute as per requirements, and there is no requirement goof-ups or design goof-ups.
Daily Scrum- All roles people daily participate in the Daily Scrum meetings
Sprint review meeting – we review the work that was completed and the scheduled work that was not completed, and present the completed work to the stakeholders
Sprint retrospective- we meet and regularly discuss after the sprint
What went well during the sprint? What did not go well? What could be improved for better productivity in the next sprint?
Artifacts Managed in Jira
We manage Product Backlog, Sprint Backlogs and Product Increments, all
the artifacts in an ‘optimised jira’ environment for anytime and anywhere review.
We also make selective use of waterfall process typically in new innovative product or major market differentiator feature, as also illustrated in our this article. Our experience suggests that a proper due diligence is needed for such product/features that waterfall allows room for.