Difference between revisions of "IS480 Team wiki: 2018T1 analyteaka changemanagement"
Jump to navigation
Jump to search
(8 intermediate revisions by 2 users not shown) | |||
Line 66: | Line 66: | ||
! style="color:#ffffff; background-color:#7D5B53;" width="50pt" | Request Status | ! style="color:#ffffff; background-color:#7D5B53;" width="50pt" | Request Status | ||
|- | |- | ||
+ | |||
|style="text-align: center; background-color:#ffffff;"| 3 | |style="text-align: center; background-color:#ffffff;"| 3 | ||
− | |style="text-align: center; background-color:#ffffff;" | | + | |style="text-align: center; background-color:#ffffff;" | 22/6/2018 |
− | |style="text-align: center; background-color:#ffffff;" | | + | |style="text-align: center; background-color:#ffffff;" | Schedule |
− | |style="text-align: left; background-color:#ffffff;" | | + | |style="text-align: left; background-color:#ffffff;" | Changing of UT schedule due to stackholder's schedule and re-estimate of task |
− | |style="text-align: left; background-color:#ffffff;" | | + | |style="text-align: left; background-color:#ffffff;" | Shifting the schedule of UT and shifting certain tasks around |
|style="text-align: center; background-color:#ffffff;" |Team | |style="text-align: center; background-color:#ffffff;" |Team | ||
− | |style="text-align: left; background-color:#ffffff;" | To | + | |style="text-align: left; background-color:#ffffff;" | To go ahead |
|style="text-align: center; background-color:#ffffff;" | Proceed with change | |style="text-align: center; background-color:#ffffff;" | Proceed with change | ||
|style="text-align: center; background-color:#ffffff;" | Closed | |style="text-align: center; background-color:#ffffff;" | Closed | ||
|- | |- | ||
− | |style="text-align: center; background-color:#ffffff;"| | + | |style="text-align: center; background-color:#ffffff;"| 7 |
− | |style="text-align: center; background-color:#ffffff;" | 8 | + | |style="text-align: center; background-color:#ffffff;" | 14/8/2018 |
− | |style="text-align: center; background-color:#ffffff;" | Schedule | + | |style="text-align: center; background-color:#ffffff;" | Schedule / Scope |
− | |style="text-align: left; background-color:#ffffff;" | | + | |style="text-align: left; background-color:#ffffff;" | Updating of schedule for changing of modules |
− | |style="text-align: left; background-color:#ffffff;" | Sponsor is | + | |style="text-align: left; background-color:#ffffff;" | Sponsor realize it would be useful to have marketing planning feature as well as bein able to name their categories as the cateorgies naming is ever changing. Having the system to do so would be great. |
− | |style="text-align: center; background-color:#ffffff;" | | + | |style="text-align: center; background-color:#ffffff;" |Sponsor |
− | |style="text-align: left; background-color:#ffffff;" | To go ahead with the | + | |style="text-align: left; background-color:#ffffff;" | To go ahead with the change. |
|style="text-align: center; background-color:#ffffff;" | Proceed with change | |style="text-align: center; background-color:#ffffff;" | Proceed with change | ||
|style="text-align: center; background-color:#ffffff;" | Closed | |style="text-align: center; background-color:#ffffff;" | Closed | ||
|- | |- | ||
− | + | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
|} | |} | ||
[[File:Analyteaka_Footer_Transparent.png|1000px|center]] | [[File:Analyteaka_Footer_Transparent.png|1000px|center]] | ||
<!--CONTENT--> | <!--CONTENT--> |
Latest revision as of 16:50, 7 October 2018
As employed above, the change management strategies largely revolve around the effect towards the following factors:
1) Stakeholder that initiated the change
2) Reason behind requesting for the change
3) Consequences of implementing vs ignoring the changes to
- Scope
- Schedule
- Risk
- Scope
4) Steps taken and documentation affected if the change was to be implemented
5) How to minimise the effects of the change to other unrelated project areas.
By following this structured approach to change management, we can work hand in hand with the relevant project stakeholders to manage their expectations with regards to change, gain their feedback and input during implementation and contribute to the eventual success of the project.
Iteration | Date | Type | Change Reason | Description | Issued By | Decision | Action Taken | Request Status |
---|---|---|---|---|---|---|---|---|
3 | 22/6/2018 | Schedule | Changing of UT schedule due to stackholder's schedule and re-estimate of task | Shifting the schedule of UT and shifting certain tasks around | Team | To go ahead | Proceed with change | Closed |
7 | 14/8/2018 | Schedule / Scope | Updating of schedule for changing of modules | Sponsor realize it would be useful to have marketing planning feature as well as bein able to name their categories as the cateorgies naming is ever changing. Having the system to do so would be great. | Sponsor | To go ahead with the change. | Proceed with change | Closed |