Professional Documents
Culture Documents
Management
Session 3
❑Not just construction and large infrastructure projects; New product development; Mergers and
acquisitions; Advertising; small projects
❑Early in life cycle – project scope is of prime importance over cost and schedule
❑Recent trend →scope and schedule are more important than cost in all stages.
❑Agile project management approaches were developed to provide greater flexibility to respond to
changing customer requirements, and ultimately complete projects more efficiently.
❑Teams must be staffed with people who can work efficiently with other
❑Team spends more time on work and less time on administrative activities.
❑Waterfall approach → customers are involved at the start of the project, when the scope needs
to be changed, and at the end of the project.
❑Developing a contract at the start of the project may not be a good idea, as least is known about
the project.
❑Agile →values fostering a collaborative relationship between the project team and the customer.
❑Waterfall → the team relies on detailed and structured change management procedures that
ultimately discourage changes and stifle creativity.
❑Highest priority is to satisfy the customer through early and continuous delivery
❑Business people and developers must work together daily throughout the project.
❑Give environment and support to the team. Trust them to get the job done.
❑The sponsors, developers, and users should be able to maintain a constant pace indefinitely.
❑Simplicity
❑The best architectures, requirements, and designs emerge from self-organizing teams
❑At regular intervals, the team reflects on how to become more efficient, then tunes and adjusts
its behaviour accordingly.
❑Scrum
❑Kanban
❑Extreme Programming
❑Crystal
❑Etc.
❑What is unique?
❑Create team and organization, unlike functional managers who take over existing operations.
❑Decide how things should be done instead of simply managing set processes.
❑They are typically the direct link to the customer and must manage the tension between
customer expectations and what is feasible and reasonable.
❑Ensure that the proper knowledge and resources are available when and where needed
❑Provide direction, coordination, and integration to the project team, which is made up of part-
time participants loyal to their functional departments.
❑Sometimes, this work is full-time, but in most cases, people work part-time.
❑How to avoid the dangers of scope creep, manage the critical path, negotiate, communicate,
understand project priorities, and make independent decisions.
❑Compliance
❑Operational
❑Strategic
❑These projects are typically those needed to meet regulatory conditions required to operate in a
region. Hence, they are called “must-do” projects.
❑Compliance and emergency projects usually have penalties if they are not implemented.
❑To improve the efficiency of delivery systems, reduce product costs, and improve performance.
❑These have limited scope and cost, and require only immediate manager approval.
❑They are frequently directed towards increasing revenue and market share.
❑A business case explains how the benefits of a project overweigh its costs and why it should be
executed.
❑A business case typically includes the strategic justification for the project, its monetary cost, the
expected benefits, any known or anticipated risks, the expected time of completion, and who will
be responsible for each of the phases of the project.
❑It includes non-monetary factors such as expected behavioural impacts, increase in efficiency,
service improvements, competitiveness effects, etc.
❑Identify the business problem → should be aligned with business goals. To solve specific
business problems or create a business opportunity.
❑Identify the alternative solutions → identify different ways of solving the problem
❑Recommend a preferred solution → rank the solutions on the basis of different criteria