Digital Maelstrom practices the Scrum Agile Methodology. This process is designed to effectively manage change during the process of business development. As with all projects, change happens – and it happens often. As the client, regular involvement in this process is necessary in order for there to be success. Typically, an individual represents your company and communicates with our team throughout the project. This company representative, called the Product Owner, helps us prioritize the importance of project goals so that progress is made efficiently and effectively.

Any idea for a capability or feature within the project is captured as a Story. At the beginning of the project, our team and the Project Owner will create and list out a group of stories to kick-start the Scrum process. This list of stories is known as the Product Backlog. Over time, the Product Backlog will change as new work is added, or as existing work is completed.

The project timeline is divided into two-week intervals known as Sprints. At the beginning of each Sprint, the Scrum Team (including the Product Owner) decides which Stories from the Product Backlog will be completed during the next Sprint. It’s important that both parties agree and commit to enough work to realistically fill the amount of possible hours of work in the Sprint. If work in a Sprint is completed faster, additional work may be pulled from the Product Backlog to speed up the project. If some Stories take longer to complete than originally estimated, the team may move some work items from the current Sprint back into the Product Backlog with the Product Owner’s approval.

At the end of the Sprint, all of the completed work is packaged together as a Deliverable and demonstrated to the Project Owner during the weekly meeting. The Product Owner will have the opportunity to offer feedback and suggestions while interacting with it. While this Deliverable may not yet be 100% functionally complete, it should be useable for the goals determined at the beginning of the Sprint, and it should deliver some predetermined aspect of business value. At this step of the process, client participation is critical in order to provide the Scrum Team with timely and relevant feedback about progress.