Thoughts on Agile & Scrum

Agile– I prefer to look at Agile as a methodology that is used mainly for project or product management purposes. From my understanding, Agile is a methodology that is based on iterative and continuous developments. In other words, Agile is a process by which a team can manage a project by breaking it into several steps and teams. The advantage of using this process is that it makes the project easier to manage and control. I do not think Agile is restricted to only software development. It is a project management tool with different methodology that are and can be used in different industries as well.

The process involves the customers as well as the team members at each iteration of the process. It begins with the customer describing the kind of product they need and the team members working collaboratively in achieving the tasks and keeping a close check after each cycle interval. Breaking the cycle into different intervals makes it easier to analyze and overlook the process and is easier to find any discrepancies, if there are any during the process rather than at the end. The teams are divided with every team and their members focused on their specific roles rather than the entire project, thus making it not overwhelming.

Scrum– As explained very clearly in our article https://www.cprime.com/resources/what-is-agile-what-is-scrum/, Scrum is a subset of Agile. Being a part of the Agile methodology, Scrum basically provides the steps for using the framework effectively divided into collaborative teams. It defines the roles of the teams and divided the workload for effective results. Scrum describes a set of time, artifacts, and roles that work together to help teams structure and manage their work. The scrum makes the process simpler, gives you more control of the project, enables quick deliverables and room to improve, along with quick and less time driven changes or developments.

There are 3 main roles in the Scrum process; ScrumMaster, Product owner and Team. The ScrumMaster is the one in charge of running the process and making sure everything goes smoothly. The Product Owner buffers the Team from feature and bug-fix requests that come from many sources, and is the single point of contact for all questions about product requirements. The Team is a self-organizing and cross-functional group of people who do the hands-on work of developing and testing the product

For my own project for this class, I believe I can implement some aspects of Scrum rather than Agile because I am a one person team and breaking my project and following the steps of Scrum could to some extent be more beneficial for me.