Thursday, January 3, 2013

Mobile Projects Delivery model

Even though the size of the mobile projects are small in terms of effort and cost, the challenges are plenty due to multiple touch-points.  Multiple challenges like establishing the ROI, filtering the diverse user need, lack of established model ( Delivery as well as Finance), Training/ramp-up model, optimal threshold for resource mix (I call it P-cube or People Proficiency Pyramid), Risk model, dependency establishment, fast pace evolving technology etc raises eyebrow to IT offices about how to go forward with the projects. People are sure they have to embark on the journey, but uncertainty creates a backward pull force.

I have been exposed to multiple clients and their needs, have been following the evolution of this space, involved in the Business Analysis and setup of Mobile CoEs. By virtue of it, I have drawn up the following model (just a snapshot given below) to amalgamate the multiple challenges on the left hand-side, the considerations the BA needs to analyse while working with the enterprise to finalize the requirement and the delivery model boosted by Agile methodology, backed by a robust KM and resourcing framework to deliver values to the end customer.


For further details, feel free to contact me (at)  pallabsen21@gmail.com


Contact me for detailed templates on the following. You would save time and money and get a jumpstart on your journey.

1. Project Plan (interweaved with dependencies)
2. Risk Planning,
3. Detailed Dependency sheets comprising different workflows from different Business Areas ( e.g. Enterprise Approvals, Dashboard, Workflow management, Field force automation, Insurance, Healthcare, Airlines, Utilities, Self-service etc.).
4. Release Plan and Iteration plans for mobile projects.
5. User Story Cards with Story points (estimated)


Note : Usage of the picture and model is restricted. Please contact me before reproduction of the same. 


No comments:

Post a Comment