Back-End Development

What is Agile Project Management?

Agile refers to an iterative, incremental method of managing the design and build activities of engineering, information technology and other business areas that aim to provide new product or service development in a highly flexible and interactive manner.



Agile is centred on four values: communication with parties, focus on delivering a working application, collaborate more with clients, and last be open to changes instead of freezing the scope of the work.


It is a variant of iterative life cycle where deliverables are submitted in stages. The main difference between agile and iterative development is that agile methods complete small portions of the deliverables in each delivery cycle (iteration) while iterative methods evolve the entire set of deliverables over time, completing them near the end of the project. Both iterative and agile methods were developed as a reaction to various obstacles that developed in more sequential forms of project organization. For example, as technology projects grow in complexity, end users tend to have difficulty defining the long term requirements without being able to view progressive prototypes. Projects that develop in iterations can constantly gather feedback to help refine those requirements. The end result is a product or project that best meets current customer needs and is delivered with minimal costs, waste, and time, enabling companies to achieve bottom line gains earlier than via traditional approaches.


Learn More About Agile

The Codesyne Process

2 Week Test Driven Sprint Cycles

Monitored by the project manager with daily scrum meetings. The development team using Jira, are assigned production tasks from the sprint ‘To Do’ list and tag the task as ‘In Progress’. Upon completion the developer will reassign the task as ‘In Review’ where it will be vetted and approved by a minimum, single intermediate and senior developer, to be moved into the ‘Done’ column and merged into the project. Ready for deployment into the final product.

Internal Sprint Evaluation & Planning

Prior or end of each sprint, the development team meets to review completed deliverables and analyze incomplete tasks, to be either pushed to the next sprint or put in the backlog, followed by a sprint retrospective for future learnings. Once closed, tasks that were projected will be adjusted based on the previous sprint and assigned story points of complexity to gage time required. Once agreed upon the future projected sprints are adjusted and the new sprint officially begins for production.

Client Sprint Review & Backlog Grooming

After an internal planning session, the client’s dedicated Codesyne representative will meet with them to review the completed sprint deliverables, demo features, deployed to the final product and next sprint objectives. Then review the revised future sprint forecast and adjust task backlog, to balance project cost and time to which the scope of work, project schedule and fee schedule exhibits within the contract agreement would be updated and signed off if required.

Soft Launch Stress Test & Debugging

When a version of the product is ready for release a soft launch window is mapped out, which includes, internal stress testing and debugging, and selecting a limited number of trusted users to supply real feedback and monitoring their actions to eliminate remaining errors towards the live launch date. Upon full version roll-out a reactive 30 day monitoring period begins in case any unusual errors are discovered and resolved to ensure delivery satisfaction of the product at which point the client assumes full responsibility.