Agile Project Management


Agile Project Management

Delivering upon customer’s needs is more about customizing Agile principles to needs of each client.

Most of our projects are delivered using Agile methodologies. We are masters of using Agile in a pragmatic manner – making Agile work and deliver upon the needs and requirements of our diverse client base.

Our key approaches to Agile Development include:

Extreme Programming (XP)
Scrum
Lean Software Development(LSD)
Agile Project Management (APM)
Dynamic Systems Development Method (DSDM)
IT Division advantage
While an Agile methodology may offer certain advantages over more traditional waterfall methodologies, we recognizes that there is no ‘one size fits all’ Agile. Successful Agile implementations can be based on a range of different tools and processes. We work with you to identify and implement the practices that work best with your IT resources and that can deliver the greatest advantages to your business.

Our Approach
IT Division employs a dedicated Project Management Office (PMO) staffed with PMI certified (PMP®) / project managers and Certified Scrum Masters. The PMO reviews all projects to ensure they are managed in accordance to PMO charter. In addition, a project ROI will be created and project metrics will be established and measured throughout the life of the project. A Certified Scrum Master (CSM) will monitor all projects and conduct detailed phase reviews based upon customer defined requirements. The Scrum Master is responsible for the Scrum process, for implementing Scrum so that it fits within an organization’s culture and still delivers the expected benefits. Scrum project management process is an important part of Agile; that helps to extract usable products from complex problems. The core of Scrum is the iteration; which is driven with a list of requirements. At the start of iteration, the team reviews what is needed to complete the product. The team then selects what it can turn into an increment of potentially shippable functionality by the end of the iteration. At the end of the iteration, the team presents the functionality it built to the project stakeholders for adaption to the project. This cycle repeats until all requirement backlogs are complete.