Earthsoft foundation of guidance presents - Project management - PowerPoint PPT Presentation


PPT – Earthsoft foundation of guidance presents - Project management PowerPoint presentation | free to view - id: 3ad6b0-ODBmN


The Adobe Flash plugin is needed to view this content

Get the plugin now

View by Category
About This Presentation

Earthsoft foundation of guidance presents - Project management


Project management is a special skill or a common sense? most imp is to track,b alert, reviews & mitigate risks - Know Schedule, Efforts, Time Management, Quality, Delivery, Estimation, Closure, Client, Project, for other presentations visit – PowerPoint PPT presentation

Number of Views:120


Write a Comment
User Comments (0)
Transcript and Presenter's Notes

Title: Earthsoft foundation of guidance presents - Project management

Project Management Guide
Please circulate to all your friends, colleagues,
relatives, associates and to everyone on
your mailing list. Let them also gain! Please
visit Download the
presentations Topics - Education, Career,
Finance, Health, Personality, Religion, etc
  • Defining project
  • Bypassing planning
  • Project objectives
  • Setting limitations
  • Project planning
  • Effective planning
  • Project resources
  • Launching a project
  • Effective Monitoring
  • Scope creep
  • Software
  • Closing a project

Defining project
  • Define Goal expected changes after project
  • What are the benefits for client
  • For organisation (helps to set the priorities)
  • Time boundaries
  • Resources needed
  • People
  • Money
  • Hardware Software
  • Facilities
  • Element of the risks
  • Maximising result plan optimize efforts

Defining project
  • Steps
  • Define the project
  • Plan the project
  • Estimate duration, money and resources
  • Build a project team
  • Launch the project, Party with stake holders
  • Monitor the project, review the progress
  • Closure of the project

Bypassing planning
  • Mentality of
  • Pushing the project
  • Planning means waste of money and time
  • Laziness, Shying away new methods
  • Overconfidence
  • Deceiving that adopted methods are the best
  • Hoping everything will be all-right
  • Lesser / Poor experience of manager
  • Sr. management involved in many crisis
  • Too much dependency on consultants

Project objectives
  • Sense of purpose? Would help on focus
  • Target? Would help motivating the team members
  • Prioritization Time sensitive? Would help to
    organise measure how much to go
  • Specific Clear Simple
  • Measurable to measure the success of the
  • Aggressive but Realistic to achieve action
  • Who has created the project?
  • Have you suggested? Or
  • Direct client? Or senior management of client? Or
  • Their client? Or
  • Consultant of client? Or
  • Consultants of clients client?

Define Project
  • Ask - What project should attempt to achieve?
  • Is there a need to change? How?
  • To create something new? Why?
  • Why is it important? Is any liability linked?
  • How soon it is needed? Is it time dependant?
  • Define Key players from client organizational
  • Vision statement share during kickoff meeting
    Seek agreement
  • Be flexible to revise the vision statement or

Setting limitations
  • Time constraints
  • Who is setting the time constraints?
  • Is any scope shifting the time frame?
  • Is it realistic? Is it shorter than team
  • Does it have right distribution across phases?
    e.g. RA 2 months entire development 2
  • Budget constraints
  • To control the scope of the project, Client would
    always want to have as much
  • To check, monitor control the budgets
  • Can you absorb over-run of efforts budget?
  • Structural constraints - To get buying from all
    the hierarchy

Risk mitigation
  • Estimate probability of occurrence and impact
    thus likely exposure
  • External - Out of control of manager good to
    identify the owner transfer
  • Internal - Understand, measure the impact,
    mitigate or transfer
  • Track till closure or transfer
  • Think always contingency plan

Project planning
  • Look at the bigger picture - Think priority,
    available resources, budget, schedule, resources
    to be recruited, etc
  • Set a reference point - Baseline the schedule for
  • Communicate a vision - Share a well written plan
    to all
  • Delegate the tasks - Cover all the activities,
    define role of everyone, make delegation
  • Break into modules - Clearer smaller tasks helps

Project planning
  • Allow to control - Define ownership once modules
    are defined
  • Set clear roles - Helps avoiding confusion, no
    excuses for missing deadline
  • Adapt to change Plan creates direction, revisit
    original assumptions change if as required,
    needs agreement
  • Check history Similar project might have been
    executed, visit previous templates, talk with
    team members who were involved, capture the tips
    act accordingly

Project planning
  • Plan brainstorming meeting chaired by third party
    - Gather team members to brainstorm
  • Requirements understanding knowledge transfer
  • Detailed Plan
  • Risk mitigation
  • Resourcing and Budgets
  • Pre-project activities are listed scheduled
  • To check if re-scheduling is required
  • To group the activities logically,
    chronologically and cost based to make
    assignment eazier
  • To plan further meetings for checking
    completion, acceptance, availability of the

Project planning
  • Creating milestones
  • To measure the progress
  • To focus on results
  • To divide work schedule
  • To raise alerts for risks difficulties
  • Attributes of mile stones
  • Defined milestones in agreement with client
  • Direct clear statements for deliverables
  • Verifiable results
  • Adaptability By client and team members

Effective planning
  • Time estimate Estimate the size of the project
    , convert it to schedule check is it inline
    with clients expectations?
  • Resource need- Build the team using the best
    possible members, also include infrastructure,
    hardware, software, etc
  • Cost determine how much would the project cost?
    Have a firm grip on direct (salary, travel,
    equipment) indirect cost(overheads like
    management cost, stationary, administration, etc.
    Track the cost as project progresses

Effective planning
  • Completeness
  • Do not miss any activity/ feature/ function.
    Include all review rework activities.
  • Estimate efforts time needed to complete the
    activity Allow contingency time for holdups ,
    overruns, quality rejections, delivery failures,
    leave, holidays, meeting, emergency, accidents,
  • Identify dependent non dependent activities,
    Connect activities based on priorities
    dependency. Non-dependent activities can be
    completed in parallel. Create network diagram for
    dependent activities determine critical path
  • Track all activities

Effective planning
  • Assign the resources
  • Changing objectives- review to check the changes
    due to inadequacy at starting phase, Address
    appropriately re-estimating re-scheduling.
  • Experience-Use organisational experience
  • Recorded data PCB (project capability baseline)
    - Use historical data- PCB, ready components,
  • Consultant Hire expert for estimation reviews
  • Do not agree under pressure- Client or management
    might push estimation or schedule. Unless it is
    realistic doable, do not agree.
  • Communication Synchronize the communication
    with all stake holders seek agreement

Leadership style
  • Authorative Making most of the decision on own,
    discouraging different ways of looking at thing
  • Disadv team members can get disgruntled since
    unable to vent their opinions
  • Hands-on Less dependent on fellow members, can
    work with less confident members
  • Consensus seeking - spend time listening to
    members, helps building team confidence,
    encourage members to use their initiatives, long
    time for decision making
  • Analytical more time spend analyzing the
    situation planning, fine tuning decision
    making, attention to details, need to be good at

Project resources
  • Check the leadership of manager
  • Ownership of failures
  • Ability to motivate team
  • Ability developing team members
  • Ability to cope up with the changes
  • Ability to delegate
  • Leading from front

Project resources
  • Project performance depends on the skills of the
    best possible team without burdening the budgets
    to ensure quality speed
  • List the key role, designation, brief description
    of each tasks, necessary preferred skills
  • Check team logic by grouping different roles
  • Get the best available resources, identify the
    training needs
  • Assure to have back up for the key resources
  • Revisit schedule to adopt available resource
  • Chase second choice if first choice is not
  • Workout new recruitment, invest as if necessary
  • Get agreement on the team, hierarchy and their
  • Forecast direct (Salary subcontract) indirect
  • Arrange a team meeting, convey goal objectives,
    communicate the role and schedule
  • Request for explaining understanding of role

Teamwork spirit
  • Forming Seek commitment from individual,
    explain their roles seek their understanding,
    discuss their expectation, understand their
    background, areas of expertise, etc
  • Storming Address the grievances conflict,
    avoid getting too personal, brainstrom to carry
    assigned tasks effectively, what support do they
    need, etc
  • Norming Allow members to settle, set the
    guideline for daily reporting, conduct start up
    meeting for daily updates, etc
  • Performing Motivate working together to
    perform towards shared objectives, recognize good
    work, grant higher role, more responsibility,
    encourage to develop new skills, etc
  • Boring If project is long, members feel they
    have outlasted their role, remind their deadlines
  • Mourning Finishing tasks early could
    de-stabilise, assign more tasks to bind those

Project resources
Project resources
Delegate effectively
To motivate team
Launching a project
  • Halfway pointrevisit again while launching a
  • What are the main constraints of the project?
  • What are the reasons for the project? What are
    the problems of the client which lead to this
  • Who suggested the project? Vision of the project
  • Who will be main beneficiaries of the project?
  • What would happen if project is failed or
    shelved? (Loss of revenue or profitability?)
  • What are the desired outcome of the project?
  • Who have you involved in the project? Have you
    identified all the resources needed for this
  • Activities needed to complete the project?
  • Set monitoring process and reporting mechanism?

Launching a project
  • Re-launching project
  • Understand the problem
  • Seek main beneficiaries inspiration to push
  • Reestate project objectives
  • Focus on activities
  • Reenergise team
  • Revisit time table
  • Revisit members- right members numbers
  • Consider the risks their handling
  • Focus on monitoring keep close eye on
    performance progress

Launching a project
Launching a project
Effective Monitoring
Effective Monitoring
Effective Monitoring
Scope creep
  • Process of introducing new parameters
    approaches to a completed project plan
  • Factors for scope creep
  • Fear of turning down a client
  • Not realizing or underestimation of impact of
    changing project plan
  • Over-optimism of new suggestion to improve a
    difficult situation
  • Lack of faith in original plan, desire of over
  • Effect of scope creep
  • Risking / derailing the project
  • Encourages client to make further suggestions

Scope creep
  • Controlling the scope creep
  • Reasons for change to be convincing
  • Check impact of not making changes doing
  • Do not be afraid, convey the proposed changes, it
    could hinder the project
  • Managing the risk
  • Identify the risk, probability of occurrence,
    impact, exposure, mitigation plan owner
  • Be objective while avoiding occurrence of the
  • Develop risk management strategy, close or
    transfer the risk, develop contingency plan
  • Communicate the risks to all stake holders, seek
    feedback, device alternative strategy

Closing a project
  • Following are advantages closing the project
  • Measure success if objectives have been achieved?
  • Satisfies the team- sense of achievement of
    completing project
  • Paves the way for future teamwork recognizing
    efforts hard work
  • Avoid repeating mistakes create records of
    lesson learnt, derive benefits from mistakes
  • Control expenserelease the resources
  • Improves communication with end users, earns
  • Offer personal satisfaction, write challenges you
    have faces how did you overcome

Closing a project
  • Plan project closure - To arrange a meeting with
    all stake holders communicating formally the
    closure, presenting data of efforts, schedule,
    quality (defect data) and cost (actual
    variances), degree of achievement, change
    requests, feedback, progress reports, positive
    negative points, challenges, risks how those
    were managed, lessons learnt corrective
    actions, performers, emerging leaders,
    productivity, do dont for future projects,
    areas of improvements, etc
  • Release hard soft resources (Hardware, source
    code, software, team members, their access
    rights, project email id)
  • Complete appraisal
  • Celebration thanking Foster a spirit of
    collaboration, improves morale, underline core
  • Seek official approval of closure

Thank You