The Typical Flow of an Implementation Project topic describes the typical flow of a

new customer installation.

Note: the triple chevron symbol in the slide >>> indicates an animation trigger

1
This is the typical flow of an implementation project. These project phases tend to
vary from customer to customer primarily due to customer culture, required timeline
to go live, and available resources. The variations tend to be around how many of the
deliverables are done. There can be a lack of discipline or effort with respect to
accomplishing each goal of each phase. This can cause problems at later phases of
the project and can make supportability and training quite difficult.

The key points here are that experience has demonstrated that when each of these
phases of the project implementation is done and all the goals outlined in each phase
is completed before moving on to the next phase, the probability of a successful
implementation is going to be as high as it can possibly be.

Each phase is equally important, but we have discovered that the more complete the
first three phases are, the less time it takes to complete the last two phases. The
phases are as follows: Mobile Strategy, Planning and Discovery, then Design, followed
by Deployment, then Operational Rollout.

2
The topics that need to be addressed in the first phase of a project, the Mobile
Strategy phase, are outlined here. MobileIron helps customers to develop or refine
their position on these topics. What this means in practical terms, is that during the
Mobile Strategy phase, customers get a comprehensive roadmap which addresses
the five key Mobile First management areas of People, Devices, Networks, Apps and
Content. The benefits of beginning with a Mobile Strategy are: it accelerates an
organizations journey to becoming MobileFirst; it offers flexibility to an organization
through customization; and it leverages MobileIrons highly trained and skilled EMM
expertise. Customers who take the time to think through their mobile strategy have
much easier deployments.

3
Once the customer has their Mobile First roadmap strategy, they are ready to move
on to the Planning and Discovery phase. The key here is to ensure that the customer
is asked the proper questions and to ensure that relevant information has been
gathered so that guiding the customer through a deployment is easier. Its also key to
agree upon success criteria of the overall deployment. Customers who complete
these in detail and before the project is underway, have a much easier time
measuring and reporting success at the end of the project as well as tracking progress
and reporting status.

4
In typical MobileIron deployments, the design or the architecture can be very
straight-forward. However most enterprise customers have very complex networks
and, as our feature complexity increases, it leads to more and more variants on
design approaches. An optimal design in this phase is absolutely critical for long term
success, so focusing on long term plans is very important. Ensuring that the initial
design is suitable for the customers long-term growth helps ensure the deployment
will not have to be re-designed midway through the project. Later in this course we
focus on some key complex architectural design considerations.

5
The deployment phase is a phase where success is very dependent on how well the
previous phases were completed. The single biggest delay which occurs in this phase
is not having the network prepared for the deployment. With smaller customers this
can be a simple delay, but with enterprise class customers these delays can take
weeks when maintenance windows are factored in. Besides the technical
deployment, its critical to perform valid tests which represent customers specific use
cases. Deployments can fail down the line in cases where not enough use case
validation was done or conversely because TOO much testing was done.
Understanding the importance of avoiding testing on use cases that arent pertinent
to customers environment will save test cycles, and therefore time and resources.

6
The Operational Rollout is typically the least technical of the phases and instead really
focuses on people and process. The key to its success is ensuring the various teams
are ready to manage the environment once the large scale rollout is underway.
Successful customers avoid stops and starts due to missing process or training, as
these could lead to loss of confidence in the overall solution.

7
Thank you for attending this MobileIron University training.