Difference between revisions of "IS480 Team wiki: 2017T1 CodeBenders Change"
Line 29: | Line 29: | ||
− | + | {|style=" width="100%" cellspacing="0" border="0" || style="font-family:Century Gothic; font-size:100%; text-align:left; background-color:#FFFFFF; " width="10%" | | |
<!--CONTENT--> | <!--CONTENT--> | ||
<div style="text-align: left;"> | <div style="text-align: left;"> | ||
<center>[[File:Codebenderschange.png|1000px]]</center> | <center>[[File:Codebenderschange.png|1000px]]</center> | ||
− | Due to the inherent nature of volatility present with respect to most Software Development Projects, the CodeBenders work hand in hand to tackle any unexpected changes that come their way. As with most of the project management strategies employed, the change management process is based on domain knowledge obtained from the PMBOK 5th Edition. | + | Due to the inherent nature of volatility present with respect to most Software Development Projects, the CodeBenders work hand in hand to tackle any unexpected changes that come their way. As with most of the project management strategies employed, the change management process is based on domain knowledge obtained from the PMBOK 5th Edition. |
+ | |||
+ | |||
<center>[[File:Codebendersflowchart.png|1000px]]</center><br> | <center>[[File:Codebendersflowchart.png|1000px]]</center><br> | ||
As employed above, the change management strategies largely revolve around the effect towards the following factors: <br> | As employed above, the change management strategies largely revolve around the effect towards the following factors: <br> | ||
Line 47: | Line 49: | ||
5) How to minimise the effects of the change to other unrelated project areas. <br><br> | 5) How to minimise the effects of the change to other unrelated project areas. <br><br> | ||
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. | 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. | ||
+ | |||
{| class="wikitable" style="font-family:Century Gothic; background-color:#FFFFFF; width: 1000px;" align="center" | {| class="wikitable" style="font-family:Century Gothic; background-color:#FFFFFF; width: 1000px;" align="center" | ||
|- | |- | ||
Line 60: | Line 63: | ||
|- | |- | ||
− | |style="text-align: center; background-color:#ffffff;"| | + | |style="text-align: center; background-color:#ffffff;"| 3 |
− | |style="text-align: center; background-color:#ffffff;" | | + | |style="text-align: center; background-color:#ffffff;" | 14/06/17 |
− | |style="text-align: center; background-color:#ffffff;" | | + | |style="text-align: center; background-color:#ffffff;" | Scope |
− | |style="text-align: center; background-color:#ffffff;" | | + | |style="text-align: center; background-color:#ffffff;" | Shreyas |
− | |style="text-align: | + | |style="text-align: left; background-color:#ffffff;" | Addition of functionality in line with expansion of X-Factor Scoping |
− | |style="text-align: | + | |style="text-align: left; background-color:#ffffff;" | Following a meeting with the project supervisor, it was recommended that the scope be revised and expanded to include more novel X Factor Ideas in order to set our project apart. |
− | |style="text-align: | + | |style="text-align: left; background-color:#ffffff;" | Addition of innovative X-Factor Ideas |
− | |style="text-align: | + | |style="text-align: left; background-color:#ffffff;" | Chatbot and NLP development, as well as Geospatial analytics development was added to the scope |
− | |style="text-align: center; background-color:#ffffff;" | | + | |style="text-align: center; background-color:#ffffff;" | Closed |
|- | |- | ||
+ | |style="text-align: center; background-color:#ffffff;"| 6 | ||
+ | |style="text-align: center; background-color:#ffffff;" | 28/07/17 | ||
+ | |style="text-align: center; background-color:#ffffff;" | Tooling | ||
+ | |style="text-align: center; background-color:#ffffff;" | Jaren | ||
+ | |style="text-align: left; background-color:#ffffff;" | Request to switch used tooling from Microsoft Xamarin to Apache Cordova due to | ||
+ | |style="text-align: left; background-color:#ffffff;" | Request issued on the grounds that utilised more familiar using standard web stack (HTML + CSS + JS3) which increased familiarity with development and ease for testing and debugging. | ||
+ | |style="text-align: left; background-color:#ffffff;" | No change was taken due to preference of the sponsor | ||
+ | |style="text-align: left; background-color:#ffffff;" | No action was taken | ||
+ | |style="text-align: center; background-color:#ffffff;" | Closed | ||
+ | |- | ||
+ | |||
+ | |} | ||
|} | |} | ||
− | |||
− | |||
</div> | </div> |
Revision as of 21:41, 9 August 2017
PROJECT SCHEDULE |
Due to the inherent nature of volatility present with respect to most Software Development Projects, the CodeBenders work hand in hand to tackle any unexpected changes that come their way. As with most of the project management strategies employed, the change management process is based on domain knowledge obtained from the PMBOK 5th Edition.
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
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 Request | Change Description | Issued By | Decision | Action Taken | Status of Request |
---|---|---|---|---|---|---|---|---|
3 | 14/06/17 | Scope | Shreyas | Addition of functionality in line with expansion of X-Factor Scoping | Following a meeting with the project supervisor, it was recommended that the scope be revised and expanded to include more novel X Factor Ideas in order to set our project apart. | Addition of innovative X-Factor Ideas | Chatbot and NLP development, as well as Geospatial analytics development was added to the scope | Closed |
6 | 28/07/17 | Tooling | Jaren | Request to switch used tooling from Microsoft Xamarin to Apache Cordova due to | Request issued on the grounds that utilised more familiar using standard web stack (HTML + CSS + JS3) which increased familiarity with development and ease for testing and debugging. | No change was taken due to preference of the sponsor | No action was taken | Closed |