This post is part of a series. The previous posts in the series can be found here:
In my last post, I discussed the types of questions that need to be answered about your mobile applications. If you have any specific application requirements, answering the questions in last month’s post should have helped you to narrow the field of candidate devices. Notice that we haven’t really addressed devices yet. It seems counter intuitive but it really makes more sense to address devices near the end of the strategy as many of the device constraints will have been established by addressing other elements of the strategy.
This month I’m going to address Users.
Understanding User Requirements
Many of the same techniques we would use as part of a standard workforce analysis are useful to build a mobile device user strategy. Typically we would create a series of personas that represent the user population. Personas are fictitious, specific, and concrete representations of target users. For an overview of workforce personas, please refer to the Ted Schadler’s blog. Once personas are created, you will need to understand the use case scenarios that each persona will be presented with. In an organization with many personas and scenarios, it might make sense to prioritize both personas and scenarios to focus on the most important combinations. It is the combination of personas and use case scenarios that will lead to the solution design.
Once the personas are use cases are defined, create a matrix similar to the one presented above. For each cell in the matrix consider the following question and record the answer:
Which of the following does the Persona in this Scenario require?
- Access to web-based apps on-premises
- Access to web-based apps in the cloud
- Access to corporate mobile apps
- Access to files located in file servers on-premises
- Access to files located in the cloud
- Access to computers using Remote Desktop
- Access to other computers located on-premises
Do you need to link Users to Devices?
Although we are not addressing devices specifically at this time, it is also a good time to determine whether or not there is a requirement to map users to the devices that they use. This requirement may be driven by many factors including:
- Asset Management (SAM/ITAM)
- Compliance Requirements
Now that we have a good understanding of our applications and users I plan to discuss Data Access and Protection. Stay tuned.
A great reference for BYOD with a Microsoft slant can be found on TechNet. I got a lot of my ideas from this guide.