Individual Essay Assignment
gnsv.srinivas
PMGT572IndividualEassyAssignment.pptxAGENDA
Introduction
Processes & Definitions
Initiating
Planning
Executing
Monitoring & Controlling
Closing
Conclusion
Introduction
Similarities between waterfall and agile methodologies
Feasibility Analysis: For waterfall cost benefit analysis is performed for the purpose of product development in all the aspects whereas in agile the feasibility analysis takes place but it will take less time and the time spent would be sprint refinement.
Planning: In waterfall, detailed planning is done during the project initiation where as in agile detailed planning analysis is done during sprint planning.
Monitoring & Controlling: In waterfall, the project’s progress is always monitored by involving plan of the project for measurement where as in agile project’s progress is monitored in each and every sprint
Communication: In waterfall, the communication includes review meeting weekly once or twice and also on monthly basis where as in agile communication includes daily stand up, sprint planning, retrospective and sprint reviews.
Documentation: In waterfall, documentation work is included more where as in agile documentation includes in preparation of requirements and writing test plans.
Differences between waterfall and agile methodologies
Project Scope: In waterfall, the project accomplishes good when the scope of the project is good and advanced whereas in agile scope of the project can be changed or modified in advance and within the budget, moreover agile works out fine even scope is not well defined in advance.
Team: In waterfall, the team sizes are large where coordination between team members would be less whereas in agile the team size could be small or mid-level but the coordination levels would be high enough.
Clients: In waterfall, the project expects client’s presence only during the delivery of the project whereas in agile, the project allows and expects clients to be involved and present through the whole project.
Prioritization: In waterfall, features are not prioritized so the result can be both success or failure of the project whereas in agile, the features are prioritized according the importance and criticality, the issues are resolved as per the priority levels.
Funding: In waterfall, the project functions well when there is reduction in fixed funding whereas in agile, the project functions well when the funding increases constantly.
Process and Definitions
The project management processes includes
Identification of project requirements
Identifying needs and expectations of the project stakeholders.
Management of resources
Balancing project constraints which includes scope, schedule, cost, quality, resources and risks.
Project management tools includes software, meeting, virtual office support, web interfaces, project portals and work management tools.
PMBOK
Waterfall approach towards project management
Waterfall approach has around five process of approach towards project management those are basically phases of project management.
Agile approach towards project management
Agile methodology is where project team can able to manage the work by dividing into various stages and consistently collaborate with stakeholders. In agile methodology the project team needs to understand the value of product or service utilization and important benefits and solutions towards an issue.
Initiating
| Knowledge Areas | Initiating |
| Project scope management. | In this phase of knowledge area the project goals, deliverables and objectives are well defined. Scope validation is done by identifying in scope and out of scope of activities |
| Project time management. | In this phase and knowledge area, it is defined on how project schedule established. Aspects such as devlopment, methodologies and software are scheduled. |
| Project cost management. | In this phase and knowledge area, the team does resource identification which are expected to produce estimates. The project will be responsible for creating budget rouhgly to figure out whether the project can be achieved. |
| Project quality management. | In this phase and knowledge area, it is important to consider project quality's initiation factors such as customer satisfaction, process improvement, fact based deliverable and empowered performance. |
| Project Human Resource Management. | In this phase and knowledge area, it is important to define the roles and responsibilities in the name of job descriptions so that it would be clear on what needs to be accomplished in the project. The requirements, expectations and location will be determined. |
| Project Communication Management. | In this phase and knowledge area, it is important to creat RACI matrix for the project i.e. Responsible, Accountable, Consult and Inform which would be like a checklist for the project. This would be good communication structure. |
| Project Risk Management | In this phase of knowledge area it inclues top level of estimation in the project on things which can threat or opportunity. The project team should accomplish identification of risks, impact assessment, design and develop strategies for risk mitigation. |
| Project Stakeholder Management | In this phase of knowledge area it is important to know who are affected by the project directly or indirectly. The management of key stakeholders is really important and for that stakeholders need to well identified. |
| Project procurement Management | In this phase of knowledge area it is important to understand the requirement or need of the project so that value can be estimated. Project analysis is done from all presectives such as cost and schedule. |
| Project integration. | In this phase of knowledge area, it is important to the know the objective of delivering the project. It is important to deliver what would be the end product or service |
Initiation in Waterfall
Objectives: It includes aspects such as establishment of project sponsorship, developing the charter of the project, project management identification, formation of team and initial analysis of business process improvement.
Goals: The main goal is to start the project.
Deliverables and Approvals: The SDLC documentation would provide a structure of relevant content. The deliverable mainly includes concept proposal which explains the need to start the project and the documentation includes strategic goals. The project charter gives information on project sponsor, project manager. The project sponsor authorizes the project manager for the execution of the project.
Roles: The roles includes the project resources such as executive sponsor, project sponsor, chief information officer, business owner, project manager and project stakeholder. For every roles RACI chart i.e. Responsible, Accountable, Consult and Inform.
Task and Activities: It includes initiation activities such as sponsorship analysis and identifying members involved in the initiation phase. Project sponsor needs to establish everything by understanding the value of project scope and accountability of project success.
Initiation in Agile
Initiation phase in agile is all about communication where the ideas which are collected should be relevant, trustworthy and collaborative.
Product vision statement: In waterfall methodology, it requires to define scope, objectives, deliverables and tasks. This becomes the time taking aspect.
On other side, the initiation phase of the project requires product vision. The product vision statement makes sure where the product desires to be in future and it should be able to meet the stakeholder requirements and expectations. Vision always be helping in mapping the current and future course of actions.
Wanderlust Product Vision
We aim to provide best itineraries to our customers by having great features such as best route maps, travels tips and locations to explore at the desired destinations.
Unlike our competitors, we offer more features such as safety, help and guide customers in the case emergencies during travel time.
Wanderlust Product Vision Board
TARGET GROUP
Our target audience will be customers who are looking for economical flights
NEEDS
The application helps travelers streamline travel plans and explore vacation opportunities/attractions
FEATURES
VALUE
Cheaper Flight options and also booking of Flights, Railways, Hotels, Cars, Local Events, Vacation Packages all at same place
The application provides suggestions towards the most exclusive and uncommon tourist locations at their destinations
Planning Overview
| Knowledge Areas | Planning |
| Project scope management. | In this phase of knowledge area, the scope management defines how much planned work should be done in the entire project from start till end. |
| Project time management. | The project time management in planning phase includes the schedule management, how the deliverables of work are been scheduled which would explain on which day what needs to be accomplished and project team needs to committed towards the specific time or date. |
| Project cost management. | Project cost management in planning phase, the budgeting which is estimated are calculated and the approval needs to be taken place in order to move into the next phase. |
| Project quality management. | In this phase and knowledge area, it is important quality planning factors are included such as planned process qualification levels and integrative utilization of supplier input process output customer to enhance ways of project planning. |
| Project Human Resource Management. | In this phase and knowledge area, the acquiring project team is really important.Tasks involved would be advertising jobs, interviewing resources. |
| Project Communication Management. | In this phase of knowledge area includes activities such as calendar invitation of meeting. When are where the meeting are exactly scheduled. |
| Project Risk Management | In order to enhance the risk register, risk management needs to be developed in the planning phase of the project where the risk breakdown structure can be utilized to identify the level of detailed risk analysis. Make sure how the risks needs to be shared and what risks needs to be accepted |
| Project Stakeholder Management | In this phase of the project, the management plan for stakeholders is well documented in order to know the actions and methods would be utilized for supporting stakeholder throughout the project. |
| Project procurement Management | In this phase of the project, it requires to identify procurements to be involved in the project. The procurement management plan includes requirement documents, resource requirements, project schedule and cost estimates of the activity. |
| Project integration. | In this phase of the project, the project charter is included. The project charter involves objectives, schedule, resources. It explains the exact approach of plan can be implemented in order to get the project completed successfully. There should be proper documentation which should help in execution and control of the project for the next phases. |
| KNOWLEDGE AREAS | WATERFALL TASKS | AGILE TASKS |
| Project scope management | Work Break Down Structure | User Stories |
| Project time management | Gantt Chart | Releases |
| Project cost management | Budget | Estimation |
| Project quality management | Requirements | Acceptance Criteria |
| Project Human Resource Management | Roles and Responsibilities | Roles, JIRA |
| Project Communication Management | Documentation work | Scrum Dairy, MS Teams |
| Project Risk Management | Risk Register | Iterations |
| Project Stakeholder Management | Stakeholder Register | Continuous communication with stakeholders |
| Project procurement Management | ||
| Project integration |
.MsftOfcThm_Accent1_Fill { fill:#4472C4; } .MsftOfcThm_Accent1_Stroke { stroke:#4472C4; }
