Mobile Unified Process

Mobile Unified Process

Software development is a complex endeavor, one which is fraught with peril if you do not follow a proven software method. The Mobile Unified Process (MUP) is one such method.

The team at IIMT has started working on MUP to help organizations across different sectors and platforms to get a better understanding of what is needed to design and develop a successful mobile product and service, specially when it comes to sue of mobile for social change.

MUP is currently developed by a selected team of experts in the field and will be open to all individuals and organizations to contribute in a wiki format soon. In the meantime, if you are interested in joiningn the team please contact us (email to mup[at]

This project is under Creative Common license.



MUP describes an agile software development process developed by the Institute of Mobile Technologies, based on IBM’s Rational Unified Process (RUP). It involves the interaction between the three distinct, yet interlinked, processes that are involved in creating a robust mobile application.
These three processes are:

1.    Agile Software Development
This process describes the modifications required to adjust a traditional iterative software development life cycle to fit the specific needs of mobile application development.

2.     Organizational Readiness and Adoption
This is a continual process of identification and implementation of organizational changes required to ensure that an organization has sufficient processes and capacities to successfully and sustainably support the requirements of its mobile application(s).

3.    User Adoption
This is an ongoing process designed to identify and monitor users’ interactions with mobile application(s), in order to inform the continued development and improvement of those applications.


1.     Agile Software Development
1.1    Evaluation: In the first iteration of the project, conduct an initial needs assessment to determine the overarching business requirements and scope for the software.
In subsequent iterations, gather and review feedback from stakeholders to identify successes, challenges and opportunities in relation to the overarching business requirements for the software.

1.2    Planning: Outline your planned approach to addressing each of the overarching business requirements for the software. This may include information such as timelines, mid-term goals and/or designation of responsibilities.
1.3    Requirement Gathering: Identify the specific software elements necessary to successfully fulfill each element of your plan. Consult with stakeholders to ensure the details of each business requirement is considered.
1.4    Design: Design software product(s) to meet each of your requirements. This may include conceptual design, functional design, technical/architecture design, graphical and user experience design. Determine which team(s) or individual(s) will implement these product(s).
1.5    Implementation: Code and create the software product(s).
1.6    Testing: Test the software internally or externally. Determine whether it meets the requirements and make adjustments as needed.
1.7    Deployment: Release the software.

2.    Organizational Readiness and Adoption
2.1    Needs Assessment/Evaluation: In the first iteration of the project, conduct an initial needs assessment to determine the overall organizational processes and capacities that are required in order to effectively and sustainably support the use of the software. In subsequent iterations, gather and review feedback from stakeholders to evaluate the efficiency of organizational processes and sufficiency of capacity levels. Identify gaps that should be addressed.
2.2    Planning: Outline your planned approach to establishing and/or building upon the required organizational processes and capacities. Determine how team(s) and individual(s) will divide responsibilities and interact in order to meet these requirements.
2.3    Requirements Gathering:    Establish priorities and define the specific components and features required to meet them.
2.4    Capacity Appraisal: Consult with stakeholders to evaluate 1) current level of capacity and 2) human and technical resources available to pursue new requirements. Identify areas where additional capacity building is required and create a training plan to address this.
2.5    Organizational Process and Content Re-Engineering: Redesign organizational processes to appropriately allocate human and technical resources to meet new requirements, as well as to adopt new tools and technologies. Engineer content to ensure data organization, layering, packaging and visualization is optimized for mobile devices.
2.6    Capacity Building: Carry out plan to improve physical, technical, financial infrastructures, supported by training for human resources, to increase the level of capacity in identified areas.
2.7    Implementation: Put new organizational processes into practice.

3.    User Adoption
3.1    User Profiling: In the first iteration of the project, determine the key characteristics of the target user group for your software. In subsequent iterations, collect and analyze user data to determine patterns of usage and identify opportunities for growth or improvement.
3.2    User Awareness: Create and implement a marketing and/or communication strategy to convey the value-added of your software of your target user group.
3.3    User Training: If a need for user training is identified during the User Profiling process, devise and implement a plan to build the capacity of your user group to effectively utilize your software.
3.4:    User Acceptance: Monitor and evaluate user acceptance of the software once it is released.

Leave a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>

Just another WordPress site