Working process
The scrum framework itself is simple. The rules, artifacts, events, and roles are easy to understand. Its semi-prescriptive approach actually helps remove the ambiguities in the development process, while giving sufficient space for companies to introduce their individual flavor to it.
In this step, the large items and functional details are transformed into epics and user stories. The user stories are transformed from large items and are smaller which can be put in the product backlog. The epics can also be included in the product backlog but cannot be included in the sprint backlog without converting it to a user story.
A typical user story example is as an admin I want to add, modify, and delete the tasks for the users in the website.
The following required fields in the user stories are necessary.
- The user stories significance
- The initial estimate made during the meeting
- Demo of how to make the user stories into tasks
Sprint planning and creating backlog
The sprint duration is very important so that the user stories are as small as possible. The typical average sprint duration lasts about 2 weeks. If the sprint duration is small than the advantage is that more customer feedback can be received and most of the errors and bugs can be addressed earlier. If the sprint duration is long then it allows the developer to work thoroughly.
The next stage is to do the sprint backlog creation for which the scrum team must select the important user stories and make them into smaller tasks. They need to plan on how to get the task completed. Also, one important thing is to prioritize the necessary tasks. StarAgile conducts CSM certification online training for the professionals aspiring to become a certified scrum master.
The actual user stories are moved as small tasks in the sprint backlog where the actual work starts. This is where the realization of the software application for example the website development begins.
To begin with, a task board also called a Kanban board is made with a lot of cards is used. The cards specify the details about the tasks such as assignee, work details, due date or the time duration, etc. The task board consists of the following columns "Product backlog or the User stories", and the "To Do" lists, "Work In Progress" and then "Testing" and "Work Done" columns.
The cards can be moved from the left to right in the order of preference and based on the completion. The task board is explained thoroughly in the Scrum master certification training online at StarAgile institute.
The typical task board is shown in the diagram below,
Instead of a physical chart, you can have the digital chart prepared in the computer using the software such as Jira, Trello, Kanbanize, Monday, etc
In this step the scrum meetings are important as it is done to track the progress status and who is doing what status. The burndown chart is the output of this meeting as it provides the details about how many tasks are completed and if there any issues or problems in completing the tasks in the "Work In Progress" columns.
Testing and Product Demonstration
The tasks completed are to be realized as a working product with full life cycle testing. The testing cost can be minimized with the addition of QA or having fewer user stories, however, the first one is the best possible solution. Every sprint that is completed must be demonstrated to the customer for his acceptance and his viewpoint on the complete solution
Download Detailed Working Process File
Let's make a detailed plan for your technology project implement it immediately.
English 
Vietnamese