Business vs academic paper.
Once there is critical evaluation of the paper then that makes it academic.
Recommendations - too deep or too narrow dilemma?
Write everything on paper then filter out after.
Recommendations -2 models
Agile & change management model
-It's ok make sure the 2 groups communicate to work seamless
-does the agile work for all solutions?
Saturday, 31 March 2012
Thursday, 29 March 2012
Wednesday, 28 March 2012
Monday, 26 March 2012
Mon 26 Mar 2012 (4) -write up
To Do:
Chapter 5 - Recommendations (started)
Chapter 6 - Limitations of paper
Chapter 7 - Critical Analysis of Paper
Chapter 8 - Conclusion
Sunday, 25 March 2012
Sun 25 Mar 2012 (10) finish up chapter 4 - issues with UA
Status Update:
Done:
Chapter 4 - Issues with User Acceptance - 1st draft
To Do:
Chapter 5 - Recommendations
Chapter 6 - Limitations of paper
Chapter 7 - Critical Analysis of Paper
Chapter 8 - Conclusion
Did some restructuring hence the time spend on it. Next I am looking to write the recommendations.
Marina.
Thursday, 22 March 2012
Thur 22 Mar 2012 (10) Write up
Restructure of Chapter with
-Recommendations on achieving user acceptance
Write the 2 chapters base on this new layout
Assess Limitations of each recommendations
Smooth flow
-Research Findings about User acceptance
-Recommendations on achieving user acceptance
Write the 2 chapters base on this new layout
Assess Limitations of each recommendations
Smooth flow
Thursday, 15 March 2012
Thur 15th Mar 2012 (15) -TO DO
TO DO:
Look up slides from outsourcing
Look up change management in conjunction with my points
Look at user curve
Look up Agile
Look up Kurt Lewin - Model of Change
Get supporting articles for evidence of each point
Follow layout of my checklist of questions for each point
devise the change management model to use wip
Write up base on information gathered - chap 4, 5 - not yet done :(
Look up slides from outsourcing
Look up change management in conjunction with my points
Look at user curve
Look up Agile
Look up Kurt Lewin - Model of Change
Get supporting articles for evidence of each point
Follow layout of my checklist of questions for each point
devise the change management model to use wip
Write up base on information gathered - chap 4, 5 - not yet done :(
Thur 15th Mar 2012 (15) Check list of questions WIP
Question to be answered in each point of Chapter 4 and 5
-Root causes of acceptance issues
-Recommendations
What are the root causes of each point?
What is the recommendation for each point?
How do we measure it in terms of the success or failure of implementation the recommendation?
Limitations of each recommendations/point?
Is it mixing up under normal human behavior? Make sure to separate.
How does change management fit into the point?
-Root causes of acceptance issues
-Recommendations
What are the root causes of each point?
What is the recommendation for each point?
How do we measure it in terms of the success or failure of implementation the recommendation?
Limitations of each recommendations/point?
Is it mixing up under normal human behavior? Make sure to separate.
How does change management fit into the point?
Saturday, 10 March 2012
Sat 10 Mar 2012 - (2) Consultation Meeting with Supervisor
IMPORTANT: if i say trust is important in org - how does one measure it? quantify it?
Look at Change management in relation to other concepts such as trust, etc
Dont deal with it in isolation.
Look at user curve. Find data at each level of the curve. if data is gathered in Jan = Fear, Data in Dec = acceptance.
So beware these are normal reactions of user, may or may not reflect the trust issues. How much is trust, how much is normal curve.
Look at outsourcing notes for user reaction to change curve. and another slide - compromise, supporter etc.
lecture 5 slides also
**
Find papers, to support trust, etc,don't just let it be an anecdotal tale.
Look at model by Kurt Lewin - Model of Change
Freeze, Unfreeze,release
**
Look at Change management in relation to other concepts such as trust, etc
Dont deal with it in isolation.
Look at user curve. Find data at each level of the curve. if data is gathered in Jan = Fear, Data in Dec = acceptance.
So beware these are normal reactions of user, may or may not reflect the trust issues. How much is trust, how much is normal curve.
Look at outsourcing notes for user reaction to change curve. and another slide - compromise, supporter etc.
lecture 5 slides also
**
Find papers, to support trust, etc,don't just let it be an anecdotal tale.
Look at model by Kurt Lewin - Model of Change
Freeze, Unfreeze,release
**
Thursday, 8 March 2012
Thur 8th Mar 2012 (9) - Write up session
Thur 8th Mar 2012
Agenda:
-Reread the research paper to ensure flow - done
-Include the Company C findings from today's meetings
-Continue write up for Chapter 4/5
Agenda:
-Reread the research paper to ensure flow - done
-Include the Company C findings from today's meetings
-Continue write up for Chapter 4/5
Thur 8th Mar 2012 (2) - Company C - meeting
Meeting with Company C - tertiary education center.
Projects
-CMS site they maintain but staff does the updates of the content
-Information systems project
Students & staff needs are priority
Customer service comes 1st
Methodology
Scrum now implementing it. learning curve. after this phase it will be revisited and things learnt will be modified and added to scrum structure right now.
scrum = 2 week sprints
AGILE
This phase student registration and scheduling of courses/classrooms - end date end of Mar 2012
Process
The final product is not when it is in production.
Production will have a functional version that users/staff can work with, without the nice to haves.
Once dust has settled and recommendations, issues have been taken, list is prioritized and the enhancements/fixes are done then promoted to production.
Short coming - users on board kinda
- takes away from their work so it is difficult to get the a lot of testing fro users- they have other obligations and they may not see the value of it as yet.
User acceptance/monitoring sessions:
sit with staff while they register a student and monitor the findings
Projects
-CMS site they maintain but staff does the updates of the content
-Information systems project
Students & staff needs are priority
Customer service comes 1st
Methodology
Scrum now implementing it. learning curve. after this phase it will be revisited and things learnt will be modified and added to scrum structure right now.
scrum = 2 week sprints
AGILE
This phase student registration and scheduling of courses/classrooms - end date end of Mar 2012
Process
The final product is not when it is in production.
Production will have a functional version that users/staff can work with, without the nice to haves.
Once dust has settled and recommendations, issues have been taken, list is prioritized and the enhancements/fixes are done then promoted to production.
Short coming - users on board kinda
- takes away from their work so it is difficult to get the a lot of testing fro users- they have other obligations and they may not see the value of it as yet.
User acceptance/monitoring sessions:
sit with staff while they register a student and monitor the findings
Tuesday, 6 March 2012
Tue 6 March 2012 - ( 4) Meetings with research companies
Meeting with Programmer in Company A (1 hour ) about requirements gathering issue - getting it right
Meeting with team for Company B on status update ( 3 hours)
Notes updated on word doc
Meeting with team for Company B on status update ( 3 hours)
Notes updated on word doc
Sunday, 4 March 2012
Sun 4 MAR 2012 (15) chapter 4 wip
Chapter 4 - user acceptance issues
1st draft of trust part
chapter 5 - recommendations
1st draft of trust part
1st draft of trust part
chapter 5 - recommendations
1st draft of trust part
Subscribe to:
Comments (Atom)