SCRUM Methodology

ITFlux follows a SCRUM Methodology on delivering competent Software solutions that focus on being both workable and usable. 

The SCRUM Methodology is all about being able to collaborate and communicate while building functional software applications at the same time being flexible to the dynamic business and market realities.

We implement the core benefits of the SCRUM Methodology best practices: responsiveness to business priorities, productive teams and high quality software. We implement these techniques into the large project engagements as well as small pilot projects.  Our model includes

Project Envisioning Phase

The project starts up with Customer meetings where the ITFlux Stakeholder and the Customer get together and build up a product backlog. The product backlog is essentially a list of features sorted in order of descending priority. During this process, ITFlux and the Customer work together to establish a shared understanding of what the customer is trying to accomplish.

Once an initial product backlog has been created, ITFlux goes over each item in the backlog and provides an estimate. Since each item in the product backlog may expand into multiple stories when it's tackled as part of a sprint, these estimates will be tested against reality in the very first phase and changes can be made for the rest of the estimates.

The Customer works with ITFlux team to provide all necessary details of all features that were achieved so far, what is working and what feature needs to be carried along. Also communication protocols and project stakeholder involvement is defined during this phase.

Project Initial Sprint

This sprint is planned with the priorities set by Customer and what VELOCITY to comfortably launch the engagement. The engagement model is tested and estimates are validated during the SPRINT. The team prepares the general framework of development and tries to accomplish minimal feature addition. The development targets on complete shippable code that is tested against the acceptance criteria created part of the stories. The outcome of this SPRINT gives more predictable planning inputs for resources, scope and cost planning.

Project Sprint(s)

The series of SPRINTS planned after the initial one, creates a sustainable growth for the application using a well informed team. The barriers of communication are removed, knowledge assimilation is accelerated and skill sets are improved for the project team. The prioritized features for the SPRINT are assigned part of the planning session. The Project backlog is created with more detailed stories and acceptance criteria. The estimates are made for each stories and more accurate VELOCITY is assigned to achieve the Customer goals. The project is monitored continuously and integrated build is reviewed with Customer. Daily meeting of the team and weekly or build wise status update with Customer is ensured to keep track of the progress.