This document provides an overview of the waterfall and agile project management models. It describes the linear sequential nature of the waterfall model where each phase must be completed before moving to the next. In contrast, the agile model is iterative with evolving requirements and collaboration between cross-functional teams. Key aspects of agile include the agile manifesto's focus on individuals, working software, customer collaboration, and response to change. The document discusses advantages of the agile model and outlines human resource project management processes like developing a plan, acquiring a team, and managing the team. It concludes that the best project methodology depends on the specific project and organization.

1. PRESENTED BY
NILDIP PATEL

2. OVERVIEW
● Introduction Waterfall model
● Waterfall Development
● Introduction Agile model
● Agile Manifesto
● Characteristic of Agile
● Advantages of Agile model
● HR Project management plan
● Conclusions
2

3. INTRODUCTION –WATERFALL MODEL
● First Process Model
● Linear-sequential life cycle model
● Phases do not overlap
3

4. WATERFALL DEVELOPMENT
● You complete one phase (e.g. design) before moving on to the next phase (e.g. development)You
rarely aim to re-visit a ‘phase’ once it’s completed.That means, you better get whatever you’re doing
right the first time!
4

5. WATERFALL DEVELOPMENT (CONTD.)
● You don’t realize any value until the end of the
project
● You leave the testing until the end
● You don’t seek approval from the stakeholders
until late in the day
● This approach is highly risky, often more costly
and generally less efficient than Agile
approaches
5

6. INTRODUCTION – AGILE MODEL
● Agile software development is a set of
principles for software development in which
requirements and solutions evolve through
collaboration between self- organizing, cross-
functional teams.
6

7. AGILE MANIFESTO
● Individuals and interactions: self-organization and motivation are important, as are interactions
like colocation and pair programming.
● Working software: working software is more useful and welcome than just presenting documents
to clients in meetings.
● Customer collaboration: requirements cannot be fully collected at the beginning of the software
development cycle, therefore continuous customer or stakeholder involvement is very important.
● Responding to change: agile methods are focused on quick responses to change and continuous
development.
7

8. CHARACTERISTICS OF AGILE MODEL
● Light Weighted methodology
● Small to medium sized teams
● Vague and/or changing requirements
● Vague and/or changing techniques
● Simple design
● Minimal system into production
8

9. ADVANTAGES OF AGILE MODEL
9

10. HR PROJECT MANAGEMENT PLAN
“Failing to plan is like planning to fail “
10

11. HR PROJECT MANAGEMENT PLAN PROCESSES
11
● Develop Human Resource Plan
● Acquire ProjectTeam
● Develop ProjectTeam
● Manage ProjectTeam

12. CONCLUSION
● Depends on the project for the selection of methodology.
● Best fit Human Resource Planning does vary between agile projects
and between organizations and it depends on business strategy of the
customer and the organization.
12

13. Thank you
&
Questions please!!
13