Change management: Difference between revisions
Mr. MacKenty (talk | contribs) (Created page with "right|frame|System Fundamentals<ref>http://www.flaticon.com/</ref> How are systems planned? Are systems just thrown into the users face without any p...") |
Mr. MacKenty (talk | contribs) No edit summary |
||
Line 1: | Line 1: | ||
[[file:system_fund.png|right|frame|System Fundamentals<ref>http://www.flaticon.com/</ref>]] | [[file:system_fund.png|right|frame|System Fundamentals<ref>http://www.flaticon.com/</ref>]] | ||
Students should understand there are a number of factors that need to be managed to ensure change is successful. The way that change is managed can have significant effects on employers and employees. | |||
=== SL version === | === SL version === | ||
When you have a system that is working, it is common to get requests to change the system. '''There is a difference between a feature request, and a bug report'''. If something if isn't working it needs to be fixed. If everything is working and the user wants to change it, we begin the change management process. | |||
The important thing to understand about change management is '''you MUST carefully consider all the possible ramifications of the change'''. Changes must be carefully planned, implemented, tested and then refined. We don't just make a change without thinking because this could create unintended problem later on. We could also create [[technical debt]] that we need to pay later. Changes should follow the same process as building software (that is, the [[design cycle]]). | |||
Revision as of 12:31, 3 July 2016
Students should understand there are a number of factors that need to be managed to ensure change is successful. The way that change is managed can have significant effects on employers and employees.
SL version[edit]
When you have a system that is working, it is common to get requests to change the system. There is a difference between a feature request, and a bug report. If something if isn't working it needs to be fixed. If everything is working and the user wants to change it, we begin the change management process.
The important thing to understand about change management is you MUST carefully consider all the possible ramifications of the change. Changes must be carefully planned, implemented, tested and then refined. We don't just make a change without thinking because this could create unintended problem later on. We could also create technical debt that we need to pay later. Changes should follow the same process as building software (that is, the design cycle).
HL version[edit]
Real-world practical advice[edit]
You should always be nervous when there is more than one person in charge of a project. We call this double-headed management, and it is very dangerous because you may get two very different specifications about the system. It is always a good idea to have only one single person who describes what a system should do. In project management, we call this a "senior customer" or a "senior user".
Do you understand this material?[edit]
Imagine you are the chief information officer for a company. The company wants to plan a system that keeps track of employees, their birthdays, salaries, and date the employee was hired. What are ten questions you would ask as you plan this system? It may be helpful to review this wikipedia entry which discusses context analysis.
Please consider the following examples, and answer the questions:
Example 1[edit]
This is a simple example:
A small business which wants to plan a new system. The new system is a computer kiosk inside the store which allows customers to sign up for a email newsletter. If a custmer signs up for a newsletter inside the store, they will get a 10% discount on their first purchase at the store. The owner hopes this 10% discount will be an incentive for customers to sign up for the email newsletter. The business will then regularly email the customers special offers and savings. The business owner expects to benefit from this system by having increased sales. The customers expect to benefit from this system by having access to special offers, to save money, and to see what is new and trendy at their store.
Question 1: List the stakeholders we should consult when planning this new system. Be careful, as there is a hidden stakeholder group that is not mentioned here!
Question 2: Infer from the example what questions should be asked of each stakeholder group.
Do you have an advanced understanding of this material?[edit]
Example 2[edit]
This is a complex example:
A school of 900 students wants to plan a new system. The school hopes the new system is a secure web-based application which manages attendance data. The school administrators want to carefully track attendance for the students so it can identify when students have been absent for a customizable threshold. For example, the school might set a threshold of 5 absences within 30 days, which then automatically notifies the student, parent, and teacher there is a problem with attendance. The threshold might be 3 times within 10 days, or something like that. The system should keep track of attendance and tardies. The system should have customizable attendance codes. For example, "abscence for school trip", "excused abscence", "medical abscence" are all allowed abscence codes.
School administrators expect to benefit by having data about attendance so they can support students and parents to be in school. School administrators also expect to benefit by giving parents and students information about attendance (so parents can support their children to be in school). Finally, school adinistrators expect to benefit by using attendance data to apply for government funding (as they can prove how many students were in class on a specific day).
Parents expect to benefit by knowing when their children are in school or miss school. This way parents can support their children to be in school. Being in school is a shared value that the school hopes the parents share.
Students expect to benefit by understanding how many days of school of they have missed. The school expects students to have a strong "ownership of learning" and manage their attendance.
Question 1: List the stakeholders we should consult when planning this new system. Be careful, as there is a hidden stakeholder group that is not mentioned here!
Question 2: Infer from the example what questions should be asked of each stakeholder group.
Standards[edit]
- Identify the context for which a new system is planned. Level 2
- Describe the need for change management. Level 2