Me and my team have been asked to develop a database according to the standards and specifications of the University of South Northen Florida. This database is specifically for software stacking and will be utilized and maintained by the USNF IT department. What follows is the implementation plan for the process of developing the database to track the institution’s software. This will be done through the six steps of project management outlined in the Project Management Handbook (Baars. W, 2006). In this handbook Baars outlines the six phases of project management: Initiation, Definition, Design, Development, Implementation, and Follow-up. In this implementation plan I will define all these steps and what takes place within them, while also explaining how they relate to the software tracking database for USNF.
The first phase of project management as defined by Baars is the Initiation Phase. In this phase the idea for the project will be fleshed out. This entails defining possible partners for the project, finding what the boundaries of the project could be, and examining what the end product/ goal should look like (Baars. W, 2006). As it relates to this project, this phase would be about brainstorming the initial outline of it. Defining possible partners for the database. How far should the data base reach? Is it just for USNF or other schools as well? Is it only for one campus or multiple? This phase will see the finished design of the database start to take shape in the form of an goal.
The second phase defined on the Project Management Handbook is the Definition Phase. This phase is very important because it makes sure that all the parties involved share the same vision for the completed project. By allowing everyone the opportunity to voice how they picture the finished project, this phase allows everyone to be on the same page. This phase also defines things like where the database will store their files and how the files will be formatted. As this phase relates to this project, this phase would see me and my team collaborate with any outside parties that are involved with the project and make sure that everyone is on the same page and has the same visions for the future outcomes of this project. We would deliberate about included features and ideas and only once the project and goals seemed adequately defined and agreed upon would we begin discussing file formatting and other nuances of the project.
The third phase of project management is the Design Phase. Once we have reached the design phase there has already been a clear definition of the scope of the project, and we all know what the project should look like and include once it is completed. The design phase sees the team begin to develop and detail some of the design aspects of the project. This could include sketches or prototypes, maybe a diorama. This phase focuses on visual representation to develop the best UI for whatever project is being worked on. This phase doesn’t only focus on front end design however, it is important to design the backend of the project as well as defining how they will interact with each other. This phase would see my team develop the interface of the database as well as how the data would be stored. Interactions with the database would be defined and mapped out.
The fourth phase is the development phase. In this phase of project management everything that will be needed for the compilation of the project will be gathered. This could include materials and tools as well as potential buyers and suppliers being secure. Another important part of this phase is the schedule. This phase is where a timeline could be created if needed. During this phase my team would gather everything they needed for our database and begin giving USNF a timeline for completion.
The second to last phase is Implementation. This phase sees the project take shape. Development and construction of the project takes place here and the project is created in physical form. Baars specifies that unexpected road bumps always take place here and it is virtually impossible to reach every goal and specification from the definition phase. What is important is to not get bogged down and keep momentum and focus on the final goal. My team would build the database here, including the coding and frontend design of the database. Creating a great product and fulfilling the goals we set in a timely manner.
The final phase is the follow-up phase. This phase is like the icing on the cake. You need to do all the small things like decorating the cake before we hand it over to our buyers. This phase sees the creation of handbooks and instructional tutorials. You create the helpdesk in this phase as well as writing the project report and dismantling the developmental team. This is the “wrap-up” phase. My team would create any informational help the university asked for while ensuring that our product is ready to be implemented into a real-world environment.
Through this exercise I hope I have demonstrated some sort of understanding of the managerial and developmental processes that take place throughout an IT project. Utilizing the information in the Project Manager Handbook has allowed me to gain some insight into these processes and I hope to one day have the chance to apply what I have learned throughout this assignment.
REFERENCES
Baars, W. (2006) Project Management Handbook Version 1.1 Data Archiving and Networked Services
Andrew Kennedy 