PPMP20009 PROJECT MANAGEMENT METHODOLOGIES
Assignment: Report on the methodology used for E-Procurement Software System
Introduction:
In this report, the methodology of project designing the EProcurement software system is clearly discussed and analyzed. Agile methodology is selected for working on the project. The implementation plan on how to design the project, achieve all the requirements through the product is mentioned and described. Characteristics of the agile methodology and its implementation with regards to the project is explained and mentioned in this report. The justification of the methodology is explained and illustrated through the report.
Case Study Description:
The client organization in the discussion is Museums Victoria which is a one of the largest museum organizations with its operation all over Victoria region. As this organization has been growing over the last decades it has reached point where it became very difficult for the organization to manually carry out the operation without having an impact on its business process, revenue and customer satisfaction. A business solution using agile methodologies is proposed through this essay which helps the organization automate all its key business processes. The main purpose through this project is to redesign and automate all its major business process like automating, online tracking of transactions, making the approval process online, controlling the turnaround time etc.
Currently, there is very less monitoring or tracking of procurement, business management, financial management process in the organization. This would have impact over period proving it costly impact on the revenue and credibility of the organization. This project will safeguard the organizations interests and vital information with regards to its transactions.
Methodology:
The methodology used for the E-procurement software system for Museums Victoria is the Agile methodology. The main reason for selecting the Agile methodology for the project which undertakes the responsibility of creating an automated software system for the Museums Victoria is mainly due to its efficiency in achieving desired results when the product requirements are not certain. Agile methodologies help the project team to create a product in the initial stages and then go on to improve the product according to the client’s requirements and finally make it to meet the desired outputs. According to the project requirements and its end results Agile methodology is chosen as the project methodology which helps in bringing out best quality product. The main characteristics and its implementation with regards to the project is explained and illustrated in the below sections of the report:
Agile Methodology:
In the Agile methodology, the entire project is divided into multiple iterations of developing the project. All the different phases of the project are gone through multiple times to achieve the desired output and project objectives. The time frame is equally divided among all the iterations making sure the project is delivered on time. The main priority in choosing the agile methodology over other methodologies is to make sure the client requirements are met and the desired output is derived from the project. Agile Methodology gives a unique opportunity for the customer to suggest changes according to their requirements and they are made sure the changes are addressed in one of the iterations in the project. This approach in developing a desired solution benefits the clients more than anyone. It also helps the developing and project team to plan the project accordingly. Constant and steady progress in the project with a standard pace is an expected characteristic of developing a project using agile methodologies. In this case, the desired output is an automated software system helping the Museums Victoria to run all its manual operations online.
Characteristics of Agile Methodology:
Agile methodology is a group of various development methodologies which has similar characteristics of continuous improvement, strict timeframe with a deadline to finish the project, effective planning to achieve desired results and project objectives. Agile development methodology is responsive and flexible to changes in the project requirements and changes to the project outcome. This is both the positive and negative aspect of this approach. It inculcates team involvement in developing the project strategy, project output and in other vital areas of the project which needs different perspectives and inputs.
⦁ In the agile methodology, entire project is divided into multiple iterations with delivery goals at the end of these iterations. (VersionOne, 2017). In short, every project is divided into multiple small projects with different set of deliverables contributing in achieving the ultimate goals of the project. The continuous process of delivering a product close to the desired output makes the project open to feedback from different directions. It helps us to understand the client requirements more clearly and improve on the project.
⦁ As there are many equally divided methodologies throughout the project duration, the result of each iteration which is developed and tested according to the client requirements acts as measure of project progress. The end results of each iteration act as a medium to collaborate the team together and to analyze the current approach towards the achievements of project goals. As the product is visible to the internal and external stakeholders after each iteration it helps them stay focused and confident that the project will achieve the desired result.
⦁ As discussed earlier agile methodology has adaptive planning as one of its main characteristics. Planning is carefully done at various levels of the project. The features and project objectives are derived in the beginning of every single iteration and after every single iteration the requirements and objectives of the next iteration are decided and worked upon. This careful breaking down of project objectives will help the team in achieving the overall project success. It gives very less scope for assumptions based on the result and has more to do with practical observations and planning according to the results achieved in every single iteration.
⦁ One of the other major characteristic of agile methodologies is the amount of testing involved in the entire project. After every iteration, there’s a result of developed and tested product which is later analyzed and refined in other iterations to get the desired output. The amount of testing involved in the entire process makes the product more refined and efficient.
Justification of the methodology approach:
The main reason for choosing the Agile methodology over the others is because of the uncertainty involved in the client’s requirements of an e-solution. The client needed automation of all their key processes but had no clear idea of the result. As, the agile methodology gives a unique opportunity to divide the entire project into small tasks and to refine a product in various stages of the software development. Per discussion earlier with regards to the characteristics of the project and its requirements through this project, agile methodologies are found to be apt. As the web solution for this organization is not a set and defined output, it is recommended that the project is approached by trial and error method. In agile technologies after the first output is visible after the first iteration of key processes, the output from that iteration is discussed with the clients. Clients analyze and examine if it fits into the requirements of them through this project. Constructive feedback is always welcomed and the product is improved upon in the next iterations of the project according to the change in requirements.
Implementation:
An implementation plan is very essential for a successful project. Methodology and project approach are to be designed prior to the implementation of a project. In the diagram appended below, an implementation strategy is designed for the E-procurement software system in a view to develop a robust and sophisticated self-tracking procurement system which can automate all the key operations of the Museums Victoria. The main steps in the implementation plan designed for the E-procurement software system project are as follows:
⦁ Develop the idea for the project: In this phase, the idea for the project and its implementation strategies are identified and planned for implementation in the next phases. All the processes of Museums Victoria are analyzed and observed to redesign and automate them according to the client’s requirements.
⦁ Document and organize the requirements for this project: In this phase, after the requirements are thoroughly analyzed it is important to document and organize all the requirements into a streamline for the product design. The inputs from the staff, customers etc. through interviews, questionnaires are documented and organized for the implementation of the project.
⦁ Design the implementation plan: The implementation phase is subdivided into four steps again implementing the agile methodology selected for the project.
⦁ Create a schedule and plan: It is always important to have a structure plan for the implementation. A project schedule is necessary for the successful implementation of the ideas. The Schedule should fit into the requirements of the project clients and the project team.
⦁ Design the iterations plan: This one of the important phase in the implementation of ideas. As this methodology needs to have the project designed in various iterations, the iteration plan need to be designed in an effective way to bring out the best product for the E-procurement of software system.
⦁ Planning the iteration outcomes through the plan: Planning of the iteration to bring the necessary outcomes is very important to streamline the entire product development phase.
⦁ Reviewing the iteration plan: Reviewing of the iteration plan is also important to make sure the project is on the track according to the project schedule and requirements.
⦁ Design a testing plan: The main advantage of the agile methodology is the repetitive testing that is done after every iteration and product outcome from the iteration. A testing plan is essential to successfully design the required product for E-procurement of software system.
Conclusion:
Finally, to conclude the report discusses about the methodology used for E-Procurement Software system which is designed to automate all the key processes of the Museums Victoria organization. The implementation plan, methodology used for the design are outlined and discussed. The advantages and disadvantages of using the methodology are clearly discussed and analyzed. A clearly described implementation plan is illustrated at the end of this report to throw more light on project plan and design implementation.
Reference:
VersionOne. (2017). Characteristics of Agile Development Success. [online] Available at: https://www.versionone.com/agile-101/agile-development-success/ [Accessed 9 May 2017].
ITM Platform | Projects Programs Portfolio. (2017). 12 Keys to the Successful Implementation of the agile methodologies. [online] Available at: https://www.itmplatform.com/en/blog/12-keys-to-the-successful-implementation-of-the-agile-methodologies/ [Accessed 10 May 2017].
Agilemodeling.com. (2017). Agile Requirements Best Practices. [online] Available at: http://agilemodeling.com/essays/agileRequirementsBestPractices.htm [Accessed 10 May 2017].
Aha.io. (2017). Agile Development Definition and Examples | Aha!. [online] Available at: http://www.aha.io/roadmapping/guide/agile-development [Accessed 10 May 2017].
Istqbexamcertification.com. (2017). What is Agile methodology? Examples, when to use it, advantages and disadvantages. [online] Available at: http://istqbexamcertification.com/what-is-agile-methodology-examples-when-to-use-it-advantages-and-disadvantages/ [Accessed 10 May 2017].
Martin, Robert C. Agile Software Development. 1st ed. Harlow, UK: Pearson, 2014. Print.
Highsmith, J., and A. Cockburn. "Agile Software Development: The Business Of Innovation". Computer 34.9 (2001): 120-127. Web.
Dingsøyr, Torgeir, Tore Dybå, and Nils Brede Moe. Agile Software Development. 1st ed. Berlin: Springer, 2010. Print.
Appendix: