Sept 27 - Meeting with Company B (1)

Tue 27th Sept 2011

*****************************
Deadline April 30th 2011
Meeting with Company B 1 hour

*****************************


Advanced Systems Group

Team: Product Manager, Business analysts, 4 Test Users ( both technical and non technical), Developers
Project: workflow using Research and Development
Aim: Make it as user friendly as possible for both technical and non technical users. Functionally it has already achieved its goals


Methodology: DSDM, Agile, SCRUM, Microsoft framework Methodology

Plan:
2 weeks sprints of meeting with Product Manager and users to demo progress
- Stuff will be agreed upon and changes made, iterative

Test Lab - still being developed
- 3 sessions 1 hour each with user and technical staff
- sit while they use the share point work flow product

Daily 10 minute updates of status, recommendations, next steps, assistance

Roll out to clients with strict contract of expectations
Beta version will be sent to clients to test and feedback will be given to improve on the product
Poll users

Then the final version

( they do not have a high staff turnover, but they ensure that proper learning takes place and more than one person is quipped with the knowledge)

( Proper project management, proper technical skillset)


***************
Past:

SharePoint Foundation = free

Company B would provide solutions using share point to clients but internally there was a low acceptance rate.

Initiative was taken to explore internally to encourage use of share point
-Company Branding
-User friendly -> users comments etc
-Documents were stored on share point
- Top down
- Became the culture and practice to use the company intranet

***************
Past projects for Clients
Used share point to manage/create minutes for meetings
Sent to get sign off from Permanent Secretary
Business Process Optimisation
Train the Trainer approach was used
Feedback was used
Iterative
Initially it was scoped at 1 month but really took 6 month
Microsoft took that hit

Online Service for Insurance Company
Iterative, Microsoft System Framework
Bugs were reported and dealt with as stated in service agreement
Good project management
Compromise

Another project 2007 -2011
Scope kept changing
Staff changed
14 work flows were done rather than 1
The need to draw the line was not done in the project

Sept 21 - Survey work for GG (5)

Wed 21st Sept 2011

Deadline March 30th 2011
Time:   5 hours

Survey Created.
Emailed Helen (BA) about direction of survey
Emails sent to Company B and a bank for permission to work with them in final project

TO:
set up interview with BA
Agenda:
select project
select users
get her user exp

set up interview with users:
Agenda:
get their perception on system, organisation
values
trust issues
culture

Sept 9 - to do (1)

TO DO:

research TAM - for user acceptance.

What works what does not.

http://www.ncbi.nlm.nih.gov/pmc/articles/PMC150360/

rated user acceptance by rating previous projects and new ones.

Email ravi about interviewing his place

Sept 8 - Meeting with GG (2)

//********************************************************************
// Project Deadline                 :   March 30th 2011
//
// Meeting with stalk holders:   Fri  9th Sept 2011 
//                                                   2 hours
//********************************************************************


Objectives:


To make sure everyone is on board and knows the general direction of the project


Outcome:
Permission was granted to allow work of the User acceptance project.
Interaction with users must be done outside of working hours.

Issues arising from Meeting:

There is NOT low user acceptance at Company A. But there are acceptance issues.

Different Types of projects. Must dig deeper into this one. Not only RAD methodology used at company A.
Some successful others not so much
Look at projects that were in both categories and create the surveys based on that
Surveys must not be done during working hours.
Send surveys for browsing by stakeholders before sending out to users.
Select users based on the projects selected.
PUI can still be used PARTLY. Because right now there is user communication going on.
March Launch is too close to measure results in entirety.
Hence Tasks will be used from  system requests and enhancement projects


Different user acceptance for different projects
Projects were done differently due to resources and skill set at the time

Company A would have their own change management strategy and if this is mentioned in project it will be properly referenced  that company A did X. So there is no plagiarizing.

When the standards are established it is up to Company A to decide what they will choose to implement.
This is acceptable There is no obligation for the company to adhere to it. These are just recommendations.

Next steps:

• Define projects I will be working with. These are past projects successful and not so successful ones.
• Create survey for users. (5250, Genie users based on projects selected).
• Send stakeholders survey.
• Distribute to users outside of office hours
• Collect results

Sept 9 - Timeline for Project (0.5)

Sept 6 - Survey work & research (3)

//********************************
// Project Deadline :   March 30th 2011
//
// Read Literature :   2hours
// Planning Survey :   1 hour
//
//********************************


Send out Survey  to Genie and Green Screen Users

These users must also be testing or part of the new PUI changes so that the survey can given to them again to record their feedback for ProfoundUI screens.

This will be the BEFORE and AFTER feedback.

Survey both: Genie and Green Screen Users

Questions will pattern:


Levels of User Acceptance

• Initial adoption ( when PUI first implemented. By testers and users) 
• Continued use (continue user without bickering) 
• Contributing (adding comments and recommendations, enhancements to make the system more useful more efficient) 
•  Promoting (inviting others)  

Levels of User Acceptance rated between 1 and 5
1 strongly disagree/dislike
2 disagree/dislike
3 neutral
4 agree/like
5 strongly agree/like

Ease of user navigating screens such as function keys and tabbing
Impact of color combination on eyes after long hours on the screen
Extra features/enhancements that the green screen did not offer
Adequate training for enhancement or screens
Adequate support after the training
Users prefer new PUI rather than green screens
Speed of using PUI pages/Browsers issues?
Bugs were fixed in an adequate amount of time
User Recommendations were taken into consideration
Downtime of the application was not noticeable/frequent
Consistent look and feel throughout
Layout of content is in an easy on the eyes way

In what ways did the profoundui  restrain/limit users? Explain
What does the green screen offer that the web page does not do? Explain

What were the user acceptance issues with the green screen????
What were the user acceptance issues with the Genie?????


Survey List to be updated with BA input


************** 


Determine the causes of lack of User Acceptance for Green Screen and Genie


What is the answer????

Sept 9 - Plan (1)

PLAN:

I think the tests can apply to both ProfoundUI and enhancements in GG. Record results.

20 test users
each with their own circles of information buddies and connections

5 green screen users
5 genie users
5 who uses both genie and green screen
5 new users

Select opinion leader and non opinion leader
Select person at hub of other people
Select solitary users

Short term aim is to see if they can influence their peers ( who do not belong to this group of 20 people) to use/have a positive attitude towards the PUI/enhancements.
Ideally choose users who are in the hub of people.

For example Susan is a good person to recruit for testing/engagement because her social network at work is wider than say Jennifer. Susan's chances to pull users over to PUI might be higher probability.

So Susan and Jennifer will still be recruited for test purposes to put to the test this theory

Select users based on Opinion Leaders. This means users who have more media power within the employee clique. This means employees who other employees listen to or look for answers. Some one who leads the pack with followers.

Cash/Claim/Underwriting

Which users/testers were selected so far? which category they fall into?

Natasha falls in which category?

She is green screen user but was able to follow the screens quickly  for the cash screens.

Where is her circle of friends? how many people is she linked to like in the diagram  above.

aim is to see if opinion leader and non opinion leader made any difference in bringing people over to PUI.

aim is to see if people in the hub of users can bring more people over.

Must choose the testers/users carefully to see what aids in making end user acceptance a reality.

This test is necessary because in the past there were opinion leaders who spoke adversely towards Genie and   influenced people who did not even user genie before hence making user acceptance more difficult

By recruiting users being at the hub like Susan ( in diagram) , if it works we can possibly increase the numbers of user buy in. majority in numbers and the few stragglers can fall in with the majority.

if recommendations to use PUI by an opinion leader is being  done then this is an indicator o acceptance as well.

************** 

Recordings will be taken from all now Sept 2011 and on wards of user reaction at different stages.

Testing, Initial launch, Continued use, Feedback from users, recommendations.

Sept 4 - User Acceptance (2)

Define User Acceptance.

Levels of User Acceptance

• Initial adoption ( when PUI first implemented. By testers and users) 
• Continued use (continue user without bickering) 
• Contributing (adding comments and recommendations, enhancements to make the system more useful more efficient) 
•  Promoting (inviting others)  

Levels of User Acceptance rated between 1 and 5
1 strongly disagree/dislike
2 disagree/dislike
3 neutral
4 agree/like
5 strongly agree/like

Ease of user navigating screens such as function keys and tabbing
Impact of color combination on eyes after long hours on the screen
Extra features/enhancements that the green screen did not offer
Adequate training for enhancement or screens
Adequate support after the training
Users prefer new PUI rather than green screens
Speed of using PUI pages/Browsers issues?
Bugs were fixed in an adequate amount of time
User Recommendations were taken into consideration
Downtime of the application was not noticeable/frequent
Consistent look and feel throughout
Layout of content is in an easy on the eyes way

In what ways did the profoundui  restrain/limit users? Explain
What does the green screen offer that the web page does not do? Explain

What were the user acceptance issues with the green screen????

What were the user acceptance issues with the Genie?????

Based on the GG crowd, younger people tend to navigate to genie web based but older folks are more resistant to change. to move away from what they know.

Conditions that have helped in the past:
It also helps with Genie if there is top down management involvement to help introduce the change to the employees.

Also helps if the managers use the application to break the ice with users.

Work on the opinion leaders. get opinion leaders as the testers

Delimiters in the past:

Genie was not properly managed, therefore proper investigation on machine requirements and upgrades were not done.
No speed test was done.
Opinion Leaders advertised that it was slow, hard on the eyes so news spread and discouraged people from using it even before trying it themselves.

Culture
Culture of company - top down management
Culture of the individual
            - Older folks more resistant to change
            -Younger folks -> willing to take ownership and try new things, more technology/online aware, take              more risk

Individual Reaction to people/managers.
If a manager is disliked and he.she is pushing PUI., due to subconscious messages users might not want to support an initiative taken by that manager. More resistant

Will the past with genie discourage users from trying out the new web version of PUI?

IDEA:

Social Networking Analysis?
People and chain. If I talk to 10 people regularly and you talk to 2 people regularly.
It might be more productive to engage me in  testing for profoundui. Since I can bring in and convince more people to use PUI.

Get opinion leaders as the testers since they influence other people. Once buy in from opinion leaders are found, they can bring other users in.

Sept 4 - Next steps

Project Due April 2012
 7 months left

Next steps:

1. Waiting on feedback from ISM supervisors on proposal.
2.  Start work on Actual Project
3. Find companies willing to be part of end user acceptance project. This means willing to share time, employees and information.
4. Hoping for Guardian General, Ministry of Finance

         Bank - FCB ? Another Ministry Ministry of Science technology?

         Emails sent to Guardian General, Ministry of Finance

         => waiting on feedback

5. Must read up literature for end user acceptance - statistics, solutions, causes