- IBM Cognos Fix Packs and Hot Fixes: What is Fix Pack? A Fix Pack is a product update that contains a cumulati... t.co/KfD2Oozb
- Deciding between Cognos TM1 and Cognos Transformer: Cognos TM1 Vs Transformer Click here for the presentation t.co/k8B9dhW6
- TM1 Rules Vs TI Processes: One of the most important decision that TM1 Developers need to make during design pha... t.co/8dpfZjM9
- Congrats to Chetan for clearing COG-385 and earning his #TM1 Black Belt. That makes 5 #TM1 black belts at Fabica! t.co/zJnX8s8
- IT Information Security Engineer t.co/xMBuH4W
Engagement Model
A typical engagement follows the follow steps:
- Program Assessment
- System Inventory
- Artifact Inventory
- Role Decompositions
- Reporting relationship and stakeholder map
- Identify Critical Systems – to be transitioned at the earliest
- Shadow resource transitioning out
- Work in parallel with transitioning team
- Take handover of relationship management and communication
- Take ownership of activities
Our engagements are high touch and data driven. You should expect a metric based approach to:
- Value Measurement
- Program Control and Administration
- Delivery Management
- Quality Management
- Stakeholder Management
- Resource Management
- Communication
Clear, accurate and timely communication is critical to the success of any project as miscommunication can result in increased project risk. Clear project communication therefore ensures that the correct stakeholders have the right information with which to make informed decisions.
Various types of formal communication may be undertaken within a project, including releasing regular project status reports, communicating project risks / issues / changes.
Typical communication methods and tools will include:
- Project Status Reports
- Change Requests and Change Request Reports
- Acceptance Plan and Acceptance Reports
- Issue Forms and Issue Register Report
- Quality Plans and Quality Reports
- Go Forward Plan (Review Meeting)

