It’s a regular question googled in relation to the adaption of scrum methodology, and still people are confused whether to implement it in their projects.
All of us know in software companies that scrum is the most significant agile methodology for handling software projects. In spite of its well-known advantages (flexibility, quick feedbacks, adaptability and better communication), we might be uncertain whether to use this framework or follow a traditional way for the development.
Scrum is a framework that can have a transforming power. Before adopting the methodology one should be sure when it’s best to use scrum and how to make the best utilisation out of this methodology.
Scrum is a lightweight agile process framework used primarily for managing software development. To know more about CSM Certification, you can visit the StarAgile site.
FRAMEWORK
Here are the scrum components:
- Roles: Team, Product owner, Scrum Master and Team
- Events: Sprint planning meeting, Release planning, Daily scrum meeting,
Review meeting and Sprint retrospective - Articrafts: Product backlog, Sprint backlog
Scrum Principles are transparency, Inspection and Adaption.
When Scrum can be followed
- Where the initial product is released and the changes or further improvement is required on the product.
- The requirement is changed in fast pace.
- Iterative release.
- Design and execution is innovative and experimental.
Nowadays many other companies other than software and product development companies follow scrum methodology to achieve success in their projects. Key for success in the project is not just following scrum process, it is to modify the framework of scrum to suit the project need and execute it efficiently. Few authors have published books which provide a structured framework of scrum to implement in non-software projects. So it requires either an experienced team, or outside advisors.
SCRUM METHODOLOGY
Scrum processes are cyclical, repeating every few weeks. Product owners provide requirements (short story points). Development and QA team implements the story points in a sprint backlog of 2-4 weeks in length. Daily scrum meeting conducted to update the work progress. Scrum master acts as close cooperation across all roles and functions.
During the sprint, team members work with the help of product owners to refine and clarify requirements, to ensure proper implementation. Final requirements are defined by test cases created by the QA team and are used to validate each description to confirm that it is complete. Narrated descriptions are implemented on a priority basis and executed in the same order.
The Pros
- Effective use of time and money.
- Works well with fast-moving development projects.
- Big projects are divided into small manageable sprints.
- Not much deviation for implementation of process.
- Regular feedback received at the delivery of each sprint and adjustments implemented before next sprint.
- The next sprint can be planned after the current sprint.
- Maximum business value can be achieved.
The Cons
- It leads to scope creep, due to lack of definite end-date.
- Adopting in large teams is challenging.
- Successful only with experienced team members.
- Iteration has huge impact on the project.
- Quality is hard until the team undergoes aggressive testing process.
HOW TO APPLY SCRUM TO OTHER PROJECTS
Earlier we reviewed the scrum principle, methodology, framework, pros and cons. Now we shall implement and analyse the scrum methodology in a manufacturing company use case.
Consider a T-shirt manufacturing company adopts scrum methodology.
Company wants to improve existing T-shirt: design and colour. Manager (Product owner) will provide the requirements as short stories to the team regarding the design required on T-shirt and cloth quality. Design (Development) team and quality (QA) team will analyse the stories and implements details into short points as the different designs required for different colour of T-shirt (sprint backlog) and will implement in span of 2-4 weeks duration.
Daily scrum meeting are held to update the progress on the design planning and working. Manager manages the work across the cross- functional team such as design, colour correction team, quality check and manufacturing team. With the story points initial T-shirt is manufactured (sprint). Based on the initial T-shirt team provides the feedback for the improvisation. Feedback can be from internal team members or external customer feedback. Based on the feedback, the adjusted design requirements are manufactured in a sample batch. Once the team is satisfied with the sample, the final T-shirt is manufactured.
The above example explains the use of scrum methodology for T-shirt manufacturing company. Here the scrum is useful in providing the required output. Sample T-shirts help to avoid the correction in large productions. Scrum methodology helps to implement the creative ideas and the feedback given are incorporated in next production. This helps to overcome minor corrections in production. Unlike the waterfall method, scrum helps in visualising the actual product before the final production and allows further customization prior to final production. The fast pace of the work process is well suited for the fast change of technology.
This method is suitable for improvisation of existing T-shirt but not for manufacturing of T-shirt in its initial design phase.
CONCLUSION
If you are working in the creative industry such as communications, design, manufacturing, marketing or sales department or program managers in government organisation scrum methodology can make your work process easier. It helps them to satisfy the needs of the customer, adapting the changes and working faster. This methodology improves cooperation and communication among team members.
