Capritto Discussion Module 1

.pdf
7/24/23, 4:56 PM MGMT555-840-202360: Submit Discussion Post Text for Module 1 https://moodle.louisiana.edu/mod/assign/view.php?id=1467668 1/3 My initial post: Module 1- MGMT 555 1. The largest project I've faced was an application upgrade at Vanderbilt for our menu system and POS for ordering patient meals. This program interfaced with the hospital EMR (electronic medical record) and allowed meals to be ordered based diets/preferences/allergies. The objective of the project was to update the system without error or major flaws upon the go- live date and with no major safety events. According to PMI, "a project as a temporary endeavor undertaken to create a unique product, service, or result". This project meets the textbook definition because a custom POS/menu system was created as the result. My time constraint was two months, as my coworker left in the middle. I was the project manager for this and worked closely with the culinary team. The culinary team had to ensure their team was trained on proper recipes, portions, etc.... I was also the trainer for the POS in our call center. Almost the entire staff was involved—from Sodexo IT and Hospital IT, the diet office to the patient tray line, to culinary and hostesses (30-40 people). There wasn't a definitive budget, as the program is propriety property of Sodexo. The only thing that was paid for was the program itself, the work was all done onsite with minimal cost. The risk from the onset was not meeting the timeline without safety issues. There was a ton of work to be done by the time my coworker left. But, we did manage to get everything completed. However, when dealing with the ticket printers we had firewall issues until midnight. We did overcome the challenges with hospital IT. We executed flawlessly without major safety events within the timeframe—which was the goal! 2. According to Watt, "projects have several characteristics. Projects are unique, are temporary in nature and have a definite beginning and ending date and are completed when the project goals are achieved, or it's determined the project is no longer viable" (2014). a. Reading a chapter before attending a university lecture would not be considered a project. But, a larger assignment in the grander scheme of a project. For example, you're in school for a degree. The project would be obtaining all the required courses to get said degree. Reading a chapter before attending a lecture would attribute to passing the course and working your way towards the goal of graduating. b. Taking a bus to work each day is a routine function without more context. It is not necessarily a project unless there are goals defined like taking a bus each day to measure the commute of my employees. This can be seen as a project if there is a definitive end. For example, I am taking the bus every day to measure the variability in time from point A to point B for the next 30 days. c. Piloting an aircraft between Vancouver and Fiji can be seen as a project or routine business activity. If you're a pilot, this is your profession, thus routine. But what if this is a type of exam or achievement? There would be markers for success (no safety events), it has a definitive begin/end, and once you've landed the goals are achieved. d. Teaching a course for the first time could be considered a project. First time teachers prepare most of their material and instruction, which would have to be done before class starts (begin/end). They are understanding their teaching style/approach and figuring out best practices (this could be done during the course). My point, it's unique, it has time constraints, and there are clear goals. However, teaching the same course every semester may vary and can be considered routine. The routine part is the information being given and the process. But, teachers have goals. They have metrics for success with students passing/failing. 3. Two project lifecycle models PMI discusses is Agile and Scrum. According to Simplilearn, "An Agile methodology is a collaborative and flexible approach that teams typically adopt to accomplish tasks more efficiently. It is an Iterative Process. Scrum methodology is an Agile framework that facilitates collaboration and efficiency in software development and testing. Scrum is an Agile process aimed at delivering business value in the shortest possible time, whereas Agile is a continuous iteration of development and testing" (2023). However, there are more models. There is Kanban and Waterfall. Kanban "is a project management methodology focused on lean principles and increasing efficiency" (Aston, 2023). It works to constantly deliver better quality work in a faster way. This type of project management is well-suited for work that requires steady output (production, support, or maintenance). On the other hand, "Waterfall is a is a project management methodology with a simple sequential approach that values solid planning to do it once and do it right" (Aston, 2023). In this type of project management, one person is in the charge and the work cascades down in phases. There is little scope to reflect, revise, and adapt once you've completed something. And there is not much to show the client along the way. 4. Adrienne Watt discusses four phases in the lifecycle:
7/24/23, 4:56 PM MGMT555-840-202360: Submit Discussion Post Text for Module 1 https://moodle.louisiana.edu/mod/assign/view.php?id=1467668 2/3 · Initiation- the project need or objective is identified. · Planning- the project is planned in further detail, with steps and processes outlined (scope management, strategy) · Implementation- Execution, work is performed. · Closing- Completion, final deliverables (2014). The application of a phased approach to project management varies in different industries but the concept doesn't. According to Berry, "a phased approach to implementation is a crucial element of a successful implementation strategy because it helps overcome resistance to change, allows lessons learned in early phases to be incorporated in the systems installed in later phases, and ensures that a solid foundation of project-level data is available prior to rolling-up enterprise- level information" (2022). Each industry will be working with different types of projects—construction projects will differ from IT projects. Industries will follow the framework, but outcomes, goals and stakeholders will be different. I think the phases do work the same in each industry. References: Agile Vs Scrum: Know the Main Differences and Similarities . (2023, June 5). Retrieved June 10, 2023, from https://www.simplilearn.com/agile-vs-scrum- article#:~:text=Agile%20is%20a%20development%20methodology,incremental%20changes%20are%20delivered%20timely. Aston, B. (2023). 9 Of The Most Popular Project Management Methodologies Made Simple. The Digital Project Manager . https://thedigitalprojectmanager.com/projects/pm-methodology/project-management-methodologies-made-simple/ Berry, K. (2022). A Phased Approach to Project Management Implementation. PMAlliance, Inc . https://pm- alliance.com/phased-project-management-implementation/ Watt, A. (2014). Project Management [E-Book]. http://open.bccampus.ca ____________________________________________________________________________ My first response: Hi Emily, I agree that the phased approach is the same despite the industry. As you indicated, there are four phases in the lifecycle that all work in the same way from industry to industry. •Initiation- the project need or objective is identified. •Planning- the project is planned in further detail, with steps and processes outlined (scope management, strategy) •Implementation- Execution, work is performed. Tasks are executed according to planning. •Closing- Completion stages, final deliverables (Watt, 2014). The application of a phased approach to project management varies in different industries but the concept doesn't. According to Berry, "a phased approach to implementation is a crucial element of a successful implementation strategy because it helps overcome resistance to change, allows lessons learned in early phases to be incorporated in the systems installed in later phases, and ensures that a solid foundation of project-level data is available prior to rolling-up enterprise- level information" (2022). Each industry will be working with different types of projects—construction projects will differ from IT projects. Industries will follow the framework, but outcomes, goals and stakeholders will be different. I think the phases do work the same in each industry. In conclusion, as Watt stated, "projects have several characteristics. Projects are unique,
7/24/23, 4:56 PM MGMT555-840-202360: Submit Discussion Post Text for Module 1 https://moodle.louisiana.edu/mod/assign/view.php?id=1467668 3/3 are temporary in nature and have a definite beginning and ending date and are completed when the project goals are achieved, or it's determined the project is no longer viable" (2014). As you indicated above, the differences for construction versus software development per task but overall, the phases and tasks in each phase, were constant. References: Berry, K. (2022). A Phased Approach to Project Management Implementation. PMAlliance, Inc. https://pm- alliance.com/phased-project-management-implementation/ Watt, A. (2014). Project Management [E-Book]. http://open.bccampus.ca My Second response: Hi Kendall, I appreciated the insight you provided in your submission. I wanted to further elaborate on the phased approach. The application of a phased approach to project management varies in different industries but the concept doesn't. According to Berry, "a phased approach to implementation is a crucial element of a successful implementation strategy because it helps overcome resistance to change, allows lessons learned in early phases to be incorporated in the systems installed in later phases, and ensures that a solid foundation of project-level data is available prior to rolling-up enterprise-level information" (2022). Each industry will be working with different types of projects—construction projects will differ from IT projects. Industries will follow the framework, but outcomes, goals and stakeholders will be different. I think the phases do work the same in each industry. In conclusion, as Watt stated, "projects have several characteristics. Projects are unique, are temporary in nature and have a definite beginning and ending date and are completed when the project goals are achieved, or it's determined the project is no longer viable" (2014). As you indicated above, the differences for construction versus software development per task but overall, the phases and tasks in each phase, were constant. With all that being said, do you still feel undecided? I see what you mean, that it can go both ways. But, the conceptual framework is the same, the type of work is different. Food for thought maybe! Berry, K. (2022). A Phased Approach to Project Management Implementation. PMAlliance, Inc. https://pm- alliance.com/phased-project-management-implementation/ Watt, A. (2014). Project Management [E-Book]. http://open.bccampus.ca
Page1of 3
Uploaded by BrookeC43 on coursehero.com