Project whispering-v1

1,030 views

Published on

Published in: Business, Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
1,030
On SlideShare
0
From Embeds
0
Number of Embeds
78
Actions
Shares
0
Downloads
5
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide
  • ----- Meeting Notes (8/24/11 11:43) -----Limited introduction of myself. Save for later slide when I talk about my professional experience
  • Project whispering-v1

    1. 1. ProjectWhispering By Nicole Lind SVP, Treehouse Agencynlind@treehouseagency.com
    2. 2. Why this session? Drupal is evolving Drupal is moving into the enterprise business and government space and it is forcing the increase in the number or Drupal projects running at the same time in any given organization
    3. 3. Why this session? Drupal Complexity Migrations from legacy systems or integrations with non-Drupal systems is forcing the available resource pool to become more skilled, expensive, difficult to manage and retain
    4. 4. The goals Provide a management framework to navigate the evolution and complexity of Drupal Provide an organizational (cultural) framework in setting priority and making decisions
    5. 5. Management Framework Project Management Product Management Program Management Portfolio Management
    6. 6. Description: Project management is the act of creatingManagement plans and managingFramework resources in order to accomplish a project.Project A project is a scheduledManagement undertaking for the purpose of creating a product or service
    7. 7. Description: A discipline that is responsible for theManagement overall success of aFramework product (not a project with very specific constraints like budget and schedule). ProductProduct managers remain toManagement manage the product through the products entire lifecycle
    8. 8. Description: Program management is the act of creatingManagement and managing multipleFramework projects, most of the projects are usually related to one another usually throughProgram dependencyManagement
    9. 9. Description: Project portfolio management is aManagement management processFramework designed to help an organization acquire and view information about all of itsPortfolio projects, then sort andManagement prioritize each project according to certain criteria, such as strategic value, impact on resources, cost, and
    10. 10. Organizational Evolution Portfolio Management Program Management Project Management and Product Management
    11. 11. Program Management A deeper lookProject Management Office (PMO)DependenciesProject Templates
    12. 12. Project Management Office(PMO) The PMO is the group or department within a organization that defines and maintains standards for project management. The primary goal is to achieve benefits from standardizing and following project management policies, processes and methods PMO is usually based upon 3 models:  Project repository, Project coaching, and Enterprise
    13. 13. Project Dependencies Finish to start (FS) – Project B can’t start before A is finished (i.e. Foundations dug then concrete is poured) Finish to finish (FF) – Project B can’t finish before A is finished (i.e. Last chapter written before entire book is finished) Start to start (SS) – Project B can’t start before A starts (i.e. Project work started before project management activities started) Start to finish (SF) – Project B can’t finish before A starts (i.e. New shifts starts after previous shift finishes)Important to know due to impact on resourcing
    14. 14. Project Templates Business Development  Contract/Statement of work Kickoff Discovery Sprint 1 (including multiple milestones) Sprint 2 (including multiple milestones) Training QA Launch Post Mortem Support Idea is to standardize so project plans and lifecycles are not created from scratch each time
    15. 15. Project Portfolio Management A deeper lookBusiness ObjectivesPrioritizationScoring and ratingMechanism for checks and balances
    16. 16. Business ObjectivesExamples: We want our team to gain D7 experience We need more revenue We want to start doing more business in the educational sector
    17. 17. Prioritization We want our team to gain D7 experience - Very important We need more revenue - Critical We want to start doing more business in the educational sector – Nice to have We want more repeat business
    18. 18. Scoring and Rating Diversification Prestige Future WorkPotential Project Total Budget Profit Potential (technology) (brand) Loyalty Factor Potential Total RatingProject A with D7 1 4 1 3 0 4 13Project B atUniversity 2 3 2 1 3 3 11Project C withold client 1 3 2 1 2 2 9Project D with D7and University 4 3 3 2 0 3 12
    19. 19. Planning and trackingDEMO
    20. 20. Final thoughtsGrow your organizational project cultureUnderstand planning at this level is hard and EVERYONE is struggling with these conceptsThe myth of the central system
    21. 21. Thank youQuestions?

    ×