Home About IUP Magazines Journals Books Archives
     
A Guided Tour | Recommend | Links | Subscriber Services | Feedback | Subscribe Online
 
Projects and Profits Magazine:
Using Multiple Project Management Frameworks
:
:
:
:
:
:
:
:
:
 
 
 
 
 
 
 

Large, medium or small, each project is significant and needs management across all phases in the software development lifecycle. Most of the projects adopt or blend frameworks, which are necessary to get the best output. Here is an example of a project, where the requirements were prioritized using the Product Backlog and the Sprints were implemented for a maximum duration of 4-6 weeks. For each Sprint, the task was estimated using the personal software process-based estimation technique for size and effort. Every artifact had a quality measure, which was being tracked as part of the execution. Reviews and formal inspections were also included as part of the Sprint. The combination of planned activities as part of agile process is novel by itself and one needs to understand the variation and adopt, accordingly.

 
 
 

Every project in any field has its own significance, right from the inception until completion. The entry and exit criteria can be very challenging and we need project management framework to ensure smooth execution. The framework must not be a process burden to the teams that have willingly signed up for adopting the same. Different project management frameworks are available but selecting the right one for the project is very crucial for the project.

Each project can be undertaken in a planned or a responsive way. The project must be able to select the framework, based on the priority of the feature set, it needs to deliver at every milestone. With the multitude of frameworks available, it is very difficult for the teams to understand what would be best suited for a project, unless there is a tool that helps teams to evaluate the frameworks before adopting them.

The evaluation criteria are based on: scope, cost, location, size, and technology, which are the critical indicators to select one framework over the other. Each of these indicators is plotted on a scale and the links are joined to interpret the dynamism of the project. On the basis of the same, teams can decide if a project needs to be executed in a planned or a responsive way.

Based on the connected marks, if the connector is towards the center of the scale, the project framework indicates agility, whereas if we form the connectors towards the periphery, it indicates a planned approach.

 
 
 

Projects & Profits Magazine, Software Development Lifecycle, Project Management Framework, Planning and Risk Mitigation, Communication, Project Management, Personal Software Process, PSP, Team Software Process, TSP, Product Quality, Software Development Framework, Waterfall Development Model