top of page

Project and Program Management

Traditional Project Management


Knowledge Areas

  • Project Integration

  • Project Scope

  • Schedule Management

  • Cost and Budget Management

  • Quality Management

  • Resources Management

  • Communication Management

  • Risk Management

  • Procurement Management

  • Stakeholders Management 


  • Dashboards

  • Gantt Charts

  • Project scheduling

  • Resources planning

  • Team collaboration

  • Time recording and tracking

  • Issue management

  • Project reporting

Software Development Process





  • The entire scope of work is broken down into short coding cycles-sprints

  • The Sprint duration is usually from 2 to 4 weeks

  • This should strictly follow a work plan for each Sprint 

  • Predefined roles for the people involved



  • Development is built on workflow visualization

  • The work in progress (WIP) is prioritized

  • There are no time-boxed development cycles

  • The work plan can be changed at any time


  • The development cycle is as short as possible

  • The delivered product is being continuously improved
  • The team is independent and has wider range of responsibilities than Scrum and Kanban
  • Developer can also formulate the final product

Frameworks Use


Scrum works well for long-term, complex projects that require stakeholder feedback, which may greatly affect project requirements. So, when the exact amount of work can’t be estimated, and the release date is not fixed, Scrum may be the best choice.



When we need to do small releases and adapt to changing priorities. Unlike Scrum, there are no sprints with their predefined goals. Kanban is focused on doing small pieces of work as they come up.


​Lean works well for small, short-term projects due to their short life cycles. This approach is also appropriate if the customer can participate in a project realization as Lean requires ongoing feedback. Constraint: The whole team should work in one office to enable communication.

bottom of page