Development Methodology
ShivCrew follows Agile Scrum Methodology to execute a project.
Scrum is an agile framework that guides teams to break complex products into small, functional pieces of work that can be coded and delivered in time boxed iterations, called “sprints”, no longer than one month and most commonly two weeks. ShivCrew engagement process is designed for feedback to ensure that the Client, as a key stakeholder, is constantly communicated on the different aspects. ShivCrew uses different Project Management Tool (PMT) to collaborate at different occasions depending upon the purpose. Similarly different communication tools/mediums are used to communicate such as Jira, Basecamp, Redmine, Zoom, Go to Meeting, Skype, WhatsApp, Emails, Phone Calls etc.
"Better to be consistently good than occasionally great".
The Process
We would like to present some of the insights of the process which we would be following to deliver your requirements, key points as listed below:
⦁ The iterations/Sprints will have a fixed duration of 3 Weeks.
⦁ As the very first step, the Scrum Master will review all of the requirements. This will involve detailed review of the specifications and will also need to communicate with Product Owner to develop an in depth understanding.
⦁ As a part of the First Sprint, the team will prepare a complete plan of the whole project defining all of the deliverables of all of the Sprints. The team will seek approval from the Product Owner and client for the same.
⦁ Upon approval, the approved Sprint Wise delivery plan will be executed. The Product Owner will be contacted periodically to review the deliverables of all of the Sprint and share comments/approvals.
⦁ Every Sprint will be of 2 Weeks. ShivCrew will expect to receive payments of any of the Sprints before starting with it.
⦁ Any comments received from the Product Owner regarding any of the Sprint may or may not be executed immediately. However, the implementation of comments received from Product Owner may cause changes in the Sprint Specifications and Delivery schedule.
⦁ Once receiving the final approval for completion of the project, we would expect to receive a final sign-off for the whole project.
⦁ After the official final delivery, we’ll extend post completion support to the client (on agreed term) ensuring that it works equally or in better capacity in comparison to the demonstrations provided. Though in this term only bugs (malfunctions) may be fixed and any changes in system including change in font, size etc. may undergo via project specifications change management.
Role Owners – Key Responsibilities
Scrum Meetings
Meetings are very important to achieve results in Scrum Process. The Team, Scrum Master as well as the Product Owner will participate in these meetings to ensure the results on an ongoing/consistent basis. These meetings have different objective and frequency. For more information, please find some of the objectives of these meetings below:
