This document discusses project management principles and concepts for nonprofits. It introduces the speaker, Norman Reiss, and his background in both the corporate and nonprofit sectors. The presentation covers basic project management terminology and processes. These include defining characteristics of projects, establishing objectives, managing scope, schedule and budget. It also addresses challenges specific to nonprofits, such as stakeholders and change management.
Is Agile Project Management Right for your NonprofitNorman Reiss
This document discusses whether agile project management is suitable for nonprofits. It begins by defining traditional project management and some of the challenges nonprofits face with projects. It then defines agile project management, emphasizing collaboration, iterative development, and responding quickly to change. Benefits of the agile mindset include seeing value earlier and adapting more easily. However, agile may not work for very predictable projects or teams that prefer strict planning. The document provides examples of using tools like Trello and Pivotal Tracker to manage agile processes and concludes by offering advice and resources for nonprofits adopting agile.
During the Agile Austria Conference 2017, Graz, Austria
Speaker: Fariz Saracevic
This session will examine how requirements management can bring significant value to agile development teams.
The document discusses Agile project management. It describes Agile as delivering value through frequent small releases called sprints. The Agile lifecycle consists of Envision, Speculate, Explore, Adapt, and Close phases. In Envision, the project charter, stakeholders, and team norms are established. Speculate identifies features for the sprint. Explore is when development occurs through daily stand-ups and collaboration. Adapt involves reviewing results and making adjustments. Close ensures deliverables are complete and lessons captured. Risks include large teams, ambitious schedules, and lacking decision makers.
Introduction to Recipes for Agile Governance in the Enterprise (RAGE)Cprime
Large enterprises that develop software cannot function without structure, but often develop structures that cripple productivity and impair responsiveness to customer needs. This Webinar introduces an approach to building effective structures by introducing the concept of Agile governance.
Agile governance provides formalized practices for decision making (governance) which incorporate the principles of the Agile Manifesto and Lean Engineering. The result is a set of simple recipes for selecting, planning, organizing, and tracking work at all levels in the organization (the Portfolio, Program, and Project levels), which apply within or across Business Units. We also provide guidance on how to develop new recipes, when needed.
This webinar introduces the basic concepts of Agile governance. We will look at some existing concepts (such as Scrum of Scrums and SAFe), and lay the foundations for subsequent webinars that address specific scenarios of common interest.
The document discusses agile leadership and how organizations need to adapt to constant change. It advocates for an agile approach where leaders emphasize collaboration, empowerment, learning and unlearning. The key aspects of agile leadership are outlined as setting a clear vision or strategy, establishing targets, empowering teams through humble management, focusing on individual effectiveness, and driving continuous improvement. Case studies on Amazon, Best Buy and CRISIL are presented showing how they embraced agile approaches to transform their businesses and focus on customers. The parting message is that agile leadership is essential for unlocking growth but must go beyond revenues and costs to truly transform organizations.
Executive Presentation on Agile Project Management by Boardroom Metrics Inc.Boardroom Metrics
This presentation was delivered to a group of senior executives with little or no understanding of Agile methodologies. It was an eye-opening experience!
If interested, please reach out to our firm to discuss how we can help your organization: 1.416.994.6552 or info@boardroommetrics.com
Learn how an evolved PMO can bring discipline to project prioritization, track project portfolios, and provide the support teams need to embrace Agile.
This document provides an overview of Agile Project Management. It begins by describing some of the limitations of traditional project management approaches, such as long timelines and products becoming outdated. It then introduces Agile Project Management as an alternative approach that allows for flexibility and incorporating feedback throughout the project. Several key aspects of Agile Project Management are summarized, including focusing on short "sprints" of work, daily stand-up meetings, emphasizing customer collaboration, and being able to change direction based on learning. Comparisons are made between Agile and traditional approaches, with Agile noted as particularly suitable for unstable or changing environments.
Is Agile Project Management Right for your NonprofitNorman Reiss
This document discusses whether agile project management is suitable for nonprofits. It begins by defining traditional project management and some of the challenges nonprofits face with projects. It then defines agile project management, emphasizing collaboration, iterative development, and responding quickly to change. Benefits of the agile mindset include seeing value earlier and adapting more easily. However, agile may not work for very predictable projects or teams that prefer strict planning. The document provides examples of using tools like Trello and Pivotal Tracker to manage agile processes and concludes by offering advice and resources for nonprofits adopting agile.
During the Agile Austria Conference 2017, Graz, Austria
Speaker: Fariz Saracevic
This session will examine how requirements management can bring significant value to agile development teams.
The document discusses Agile project management. It describes Agile as delivering value through frequent small releases called sprints. The Agile lifecycle consists of Envision, Speculate, Explore, Adapt, and Close phases. In Envision, the project charter, stakeholders, and team norms are established. Speculate identifies features for the sprint. Explore is when development occurs through daily stand-ups and collaboration. Adapt involves reviewing results and making adjustments. Close ensures deliverables are complete and lessons captured. Risks include large teams, ambitious schedules, and lacking decision makers.
Introduction to Recipes for Agile Governance in the Enterprise (RAGE)Cprime
Large enterprises that develop software cannot function without structure, but often develop structures that cripple productivity and impair responsiveness to customer needs. This Webinar introduces an approach to building effective structures by introducing the concept of Agile governance.
Agile governance provides formalized practices for decision making (governance) which incorporate the principles of the Agile Manifesto and Lean Engineering. The result is a set of simple recipes for selecting, planning, organizing, and tracking work at all levels in the organization (the Portfolio, Program, and Project levels), which apply within or across Business Units. We also provide guidance on how to develop new recipes, when needed.
This webinar introduces the basic concepts of Agile governance. We will look at some existing concepts (such as Scrum of Scrums and SAFe), and lay the foundations for subsequent webinars that address specific scenarios of common interest.
The document discusses agile leadership and how organizations need to adapt to constant change. It advocates for an agile approach where leaders emphasize collaboration, empowerment, learning and unlearning. The key aspects of agile leadership are outlined as setting a clear vision or strategy, establishing targets, empowering teams through humble management, focusing on individual effectiveness, and driving continuous improvement. Case studies on Amazon, Best Buy and CRISIL are presented showing how they embraced agile approaches to transform their businesses and focus on customers. The parting message is that agile leadership is essential for unlocking growth but must go beyond revenues and costs to truly transform organizations.
Executive Presentation on Agile Project Management by Boardroom Metrics Inc.Boardroom Metrics
This presentation was delivered to a group of senior executives with little or no understanding of Agile methodologies. It was an eye-opening experience!
If interested, please reach out to our firm to discuss how we can help your organization: 1.416.994.6552 or info@boardroommetrics.com
Learn how an evolved PMO can bring discipline to project prioritization, track project portfolios, and provide the support teams need to embrace Agile.
This document provides an overview of Agile Project Management. It begins by describing some of the limitations of traditional project management approaches, such as long timelines and products becoming outdated. It then introduces Agile Project Management as an alternative approach that allows for flexibility and incorporating feedback throughout the project. Several key aspects of Agile Project Management are summarized, including focusing on short "sprints" of work, daily stand-up meetings, emphasizing customer collaboration, and being able to change direction based on learning. Comparisons are made between Agile and traditional approaches, with Agile noted as particularly suitable for unstable or changing environments.
Traditional vs Lean Portfolio Management, Agile PMO & OrganisationsBarry O'Reilly
This deck showcases how the future can look for organisations as they attempt to scale up agile and lean practices and principles across the entire organisation.
Regardless if we have entered to do project/programme/portfolio work, once onsite I find it is a great way to introduce the wider organisation to the ideas that we use to deliver and how they can support all areas and activities in the organisation.
Key concepts;
- How traditional PMO and organisation are setup
- Legacy mindset for are alive and still driving the majority of portfolio/organisation behaviours
- Comparisons of traditional and agile/lean mindsets
- Principles of agile/lean portfolio/organisation management
- Organisational structure
- Annual vs Incremental funding (Beyond Budgeting)
- Limiting Work in Progress i.e. its only matters how many projects you finish, not start.
- Managing and visualising capability
- Coping with portfolio complexity through experimentation and validated learning
- Removing the concept of projects and focusing on continuous delivery of value
- Benefits of agile/lean portfolio/organisation management
This deck was compiled using referenced materials and the support of David Joyce (@dpjoyce) and Ian Carroll (@caza_no7)
This document discusses the journey of a company transitioning from a waterfall development process to an agile development process. Some key points:
- The company initially tried introducing agile in 2012 but did not make much progress until hiring an agile coach in late 2012 and forming an agile champions team in early 2013.
- The transition involved reorganizing teams, training staff in agile practices, and shifting roles like business analysts becoming product owners. It took time for people to adapt to their new roles and responsibilities.
- Challenges included staff adjusting to writing user stories instead of long requirements documents, estimating story points consistently across teams, planning releases, and managing expectations around faster delivery from management.
The document discusses the importance of adaptive planning in projects. It states that organizations encourage adaptive planning as planning to re-plan is a successful way to achieve project goals. Adaptive planning enables organizations to effectively manage inevitable changes in projects and accommodate changing requirements throughout development. As a result of adaptive planning, organizations are able to continuously increase business value, reduce risk, adapt to changing requirements, and achieve high visibility of project progress. The document then contrasts agile and traditional planning approaches and discusses various principles and concepts related to agile planning such as iterative planning, customer engagement, transparency, tailoring processes, estimating techniques, and release planning.
Agile methods have evolved over several decades through iterative improvements. The document discusses the history and key principles of various agile frameworks including Scrum, DSDM, Crystal, FDD, Lean, XP, and ASD. It evaluates the different approaches based on criteria like project size, team size, development style, required technology environment, and business culture fit.
Agile Project Management explained and examined from several angles. Agile Software Development delivers better results when it is managed in an agile way.
During the Agile Austria Conference 2017.
Speaker: Wolfgang Richter
This case study reflects on the Scrum journey of an Austrian insurance company. For the audience it illustrates how to apply Large Scale Scrum in a stalled environment which is not used to change quickly. Challenges and incidents typical for adopting the agile mindset in such an environment at larger scale are addressed. It shows, that the journey continues and the difficulties when setting expected dates or milestones for the adoption.
The document discusses how adopting an agile methodology can help projects address challenges like unclear requirements and communication issues, noting that agile approaches focus on iterative development, collaboration between self-directed teams and customers, and adapting to change based on regular feedback rather than extensive up-front planning. It provides an overview of agile principles and values like incremental delivery and learning through doing, while cautioning that agility does not mean abandoning practices like documentation, planning, and requirements altogether.
Professional Project Manager Should Be Proficient in AgileNitor
This document discusses the benefits of being proficient in Agile project management. It begins with an introduction of the presenter and their experience in IT projects. It then contrasts the Waterfall and Agile approaches. Waterfall involves detailed upfront planning while Agile values adaptability and frequent delivery of working software. The document emphasizes that due to global competition, it is not enough to simply complete a project but to exceed expectations and adapt quickly. It provides examples of how companies like Nitor have seen success through Agile methods and discusses key Agile principles like small batch sizes and effective communication.
The document discusses understanding agile project management. It outlines some key aspects of agile project management including managing for uncertainty rather than out of uncertainty. It discusses managing cost, time, and scope with techniques like planning scope in rolling waves and allowing room for negotiation. The document also discusses emphasizing deliverables over activities, reducing dependencies, prioritizing over sequencing work, and always finishing work on time. It promotes techniques like test-driven development, continuous integration, and continuous testing to focus on quality.
Learn the basics of the agile way-of-life that has helped many companies realize their potential in the market. The agile secret sauce was once a thing that was only enjoyed by software organizations on the East and West coasts, but is now invading Indianapolis -- increasing productivity, making teams empowered (and happier!), and helping managers focus less on the taskmaster role and more on the important stuff.
Achievements and Lessons Learned Introducing Large Scaled Agile DevelopmentWolfgang Richter
Presentation given at the Agile Austria Conference 2017 in Graz.
Track: Scaling Agile
"Achievements and Lessons Learned Introducing Large Scaled Agile Development"
Speakers: Stefan Wunder & Robert Dietze
The document discusses risk management for large agile projects. It begins by explaining why explicit risk management is needed for large projects operating in high uncertainty. It then outlines a three part approach: [1] Identify risk drivers by defining objectives and determining factors that could impact success or failure, [2] Conduct agile risk assessments by evaluating threats and opportunities against the risk drivers, and tracking this in a risk profile, [3] Integrate risk management by planning responses, using a risk board, and including risks in acceptance criteria. The document provides examples of how to identify common risk drivers in areas like business, technical, feedback, organizational, and dependencies.
#8 agile governance questions you can and should be askingaboobier
The document discusses 8 questions that agile teams should ask regarding governance. It provides context around each question and examples of how they could be addressed. The questions focus on defining success criteria and measures, understanding scope and requirements, estimating timelines and costs, tracking progress, and ensuring work is releasable. Continuous learning and improvement is important, as the questions help teams reflect on what they have learned.
The Agile PMO: Ensuring visibility and governanceMatt Holitza
The document discusses how an agile project management office (PMO) can help ensure visibility and governance of agile projects. It outlines some pitfalls that can jeopardize a traditional PMO and attributes of a successful PMO. The document then discusses how agile benefits PMOs by helping them align projects to goals, improve success rates over time, enhance competence, develop standards, promote a collaborative tone, and encourage continuous learning. An agile PMO can achieve these benefits through practices like a whole team approach, transparency, integrated tooling, and continuous process improvement.
From dysfunction to cross function in 8,593 easy steps- team building at the cbcJade Stephen, PSM II
Digital Operations is a department of 100 staff members at CBC who work in autonomous teams to build digital products using agile frameworks like Scrum and Kanban. They previously struggled with a lack of shared goals, collaboration, and trust between teams. To address this, they formed a leadership team, developed core values, introduced new cross-team meetings, and emphasized transparency. As a result, collaboration and engagement improved, they found more opportunities to work together, gained stakeholder trust, and created a more unified approach to problem solving. Their focus going forward is on continuous improvement and upholding their values of collaboration, learning, and helping each other grow.
As more organizations begin to adopt agile on multiple, interdependent teams, how do we ensure that the success within a team can translate to success at the enterprise level?
Presented by: Sanjiv Augustine, President of LitheSpeed
These slides--based on the webinar featuring leading IT analyst firm Enterprise Management Associates (EMA) and IBM--reveal the challenges of managing today’s complex IT environments and the benefits associated with moving to a true hybrid IT management approach.
The document discusses applying project management principles and techniques to nonprofit organizations. It provides an overview of basic project management concepts and challenges in establishing project management practices within nonprofits. It also discusses how project management could be applied to three common nonprofit initiatives: redesigning a website, introducing new ephilanthropy tools, and enhancing integration between departments.
This document provides an overview of tools and resources available on the MindTools.com website to help with project management. MindTools.com has over 1,000 resources to help people be effective managers and leaders. It provides assessments to evaluate skills, frameworks and tools for project planning and scheduling, stakeholder management, and change management. MindTools.com aims to teach 50 individual project management skills through frameworks, tools and assessments.
Traditional vs Lean Portfolio Management, Agile PMO & OrganisationsBarry O'Reilly
This deck showcases how the future can look for organisations as they attempt to scale up agile and lean practices and principles across the entire organisation.
Regardless if we have entered to do project/programme/portfolio work, once onsite I find it is a great way to introduce the wider organisation to the ideas that we use to deliver and how they can support all areas and activities in the organisation.
Key concepts;
- How traditional PMO and organisation are setup
- Legacy mindset for are alive and still driving the majority of portfolio/organisation behaviours
- Comparisons of traditional and agile/lean mindsets
- Principles of agile/lean portfolio/organisation management
- Organisational structure
- Annual vs Incremental funding (Beyond Budgeting)
- Limiting Work in Progress i.e. its only matters how many projects you finish, not start.
- Managing and visualising capability
- Coping with portfolio complexity through experimentation and validated learning
- Removing the concept of projects and focusing on continuous delivery of value
- Benefits of agile/lean portfolio/organisation management
This deck was compiled using referenced materials and the support of David Joyce (@dpjoyce) and Ian Carroll (@caza_no7)
This document discusses the journey of a company transitioning from a waterfall development process to an agile development process. Some key points:
- The company initially tried introducing agile in 2012 but did not make much progress until hiring an agile coach in late 2012 and forming an agile champions team in early 2013.
- The transition involved reorganizing teams, training staff in agile practices, and shifting roles like business analysts becoming product owners. It took time for people to adapt to their new roles and responsibilities.
- Challenges included staff adjusting to writing user stories instead of long requirements documents, estimating story points consistently across teams, planning releases, and managing expectations around faster delivery from management.
The document discusses the importance of adaptive planning in projects. It states that organizations encourage adaptive planning as planning to re-plan is a successful way to achieve project goals. Adaptive planning enables organizations to effectively manage inevitable changes in projects and accommodate changing requirements throughout development. As a result of adaptive planning, organizations are able to continuously increase business value, reduce risk, adapt to changing requirements, and achieve high visibility of project progress. The document then contrasts agile and traditional planning approaches and discusses various principles and concepts related to agile planning such as iterative planning, customer engagement, transparency, tailoring processes, estimating techniques, and release planning.
Agile methods have evolved over several decades through iterative improvements. The document discusses the history and key principles of various agile frameworks including Scrum, DSDM, Crystal, FDD, Lean, XP, and ASD. It evaluates the different approaches based on criteria like project size, team size, development style, required technology environment, and business culture fit.
Agile Project Management explained and examined from several angles. Agile Software Development delivers better results when it is managed in an agile way.
During the Agile Austria Conference 2017.
Speaker: Wolfgang Richter
This case study reflects on the Scrum journey of an Austrian insurance company. For the audience it illustrates how to apply Large Scale Scrum in a stalled environment which is not used to change quickly. Challenges and incidents typical for adopting the agile mindset in such an environment at larger scale are addressed. It shows, that the journey continues and the difficulties when setting expected dates or milestones for the adoption.
The document discusses how adopting an agile methodology can help projects address challenges like unclear requirements and communication issues, noting that agile approaches focus on iterative development, collaboration between self-directed teams and customers, and adapting to change based on regular feedback rather than extensive up-front planning. It provides an overview of agile principles and values like incremental delivery and learning through doing, while cautioning that agility does not mean abandoning practices like documentation, planning, and requirements altogether.
Professional Project Manager Should Be Proficient in AgileNitor
This document discusses the benefits of being proficient in Agile project management. It begins with an introduction of the presenter and their experience in IT projects. It then contrasts the Waterfall and Agile approaches. Waterfall involves detailed upfront planning while Agile values adaptability and frequent delivery of working software. The document emphasizes that due to global competition, it is not enough to simply complete a project but to exceed expectations and adapt quickly. It provides examples of how companies like Nitor have seen success through Agile methods and discusses key Agile principles like small batch sizes and effective communication.
The document discusses understanding agile project management. It outlines some key aspects of agile project management including managing for uncertainty rather than out of uncertainty. It discusses managing cost, time, and scope with techniques like planning scope in rolling waves and allowing room for negotiation. The document also discusses emphasizing deliverables over activities, reducing dependencies, prioritizing over sequencing work, and always finishing work on time. It promotes techniques like test-driven development, continuous integration, and continuous testing to focus on quality.
Learn the basics of the agile way-of-life that has helped many companies realize their potential in the market. The agile secret sauce was once a thing that was only enjoyed by software organizations on the East and West coasts, but is now invading Indianapolis -- increasing productivity, making teams empowered (and happier!), and helping managers focus less on the taskmaster role and more on the important stuff.
Achievements and Lessons Learned Introducing Large Scaled Agile DevelopmentWolfgang Richter
Presentation given at the Agile Austria Conference 2017 in Graz.
Track: Scaling Agile
"Achievements and Lessons Learned Introducing Large Scaled Agile Development"
Speakers: Stefan Wunder & Robert Dietze
The document discusses risk management for large agile projects. It begins by explaining why explicit risk management is needed for large projects operating in high uncertainty. It then outlines a three part approach: [1] Identify risk drivers by defining objectives and determining factors that could impact success or failure, [2] Conduct agile risk assessments by evaluating threats and opportunities against the risk drivers, and tracking this in a risk profile, [3] Integrate risk management by planning responses, using a risk board, and including risks in acceptance criteria. The document provides examples of how to identify common risk drivers in areas like business, technical, feedback, organizational, and dependencies.
#8 agile governance questions you can and should be askingaboobier
The document discusses 8 questions that agile teams should ask regarding governance. It provides context around each question and examples of how they could be addressed. The questions focus on defining success criteria and measures, understanding scope and requirements, estimating timelines and costs, tracking progress, and ensuring work is releasable. Continuous learning and improvement is important, as the questions help teams reflect on what they have learned.
The Agile PMO: Ensuring visibility and governanceMatt Holitza
The document discusses how an agile project management office (PMO) can help ensure visibility and governance of agile projects. It outlines some pitfalls that can jeopardize a traditional PMO and attributes of a successful PMO. The document then discusses how agile benefits PMOs by helping them align projects to goals, improve success rates over time, enhance competence, develop standards, promote a collaborative tone, and encourage continuous learning. An agile PMO can achieve these benefits through practices like a whole team approach, transparency, integrated tooling, and continuous process improvement.
From dysfunction to cross function in 8,593 easy steps- team building at the cbcJade Stephen, PSM II
Digital Operations is a department of 100 staff members at CBC who work in autonomous teams to build digital products using agile frameworks like Scrum and Kanban. They previously struggled with a lack of shared goals, collaboration, and trust between teams. To address this, they formed a leadership team, developed core values, introduced new cross-team meetings, and emphasized transparency. As a result, collaboration and engagement improved, they found more opportunities to work together, gained stakeholder trust, and created a more unified approach to problem solving. Their focus going forward is on continuous improvement and upholding their values of collaboration, learning, and helping each other grow.
As more organizations begin to adopt agile on multiple, interdependent teams, how do we ensure that the success within a team can translate to success at the enterprise level?
Presented by: Sanjiv Augustine, President of LitheSpeed
These slides--based on the webinar featuring leading IT analyst firm Enterprise Management Associates (EMA) and IBM--reveal the challenges of managing today’s complex IT environments and the benefits associated with moving to a true hybrid IT management approach.
The document discusses applying project management principles and techniques to nonprofit organizations. It provides an overview of basic project management concepts and challenges in establishing project management practices within nonprofits. It also discusses how project management could be applied to three common nonprofit initiatives: redesigning a website, introducing new ephilanthropy tools, and enhancing integration between departments.
This document provides an overview of tools and resources available on the MindTools.com website to help with project management. MindTools.com has over 1,000 resources to help people be effective managers and leaders. It provides assessments to evaluate skills, frameworks and tools for project planning and scheduling, stakeholder management, and change management. MindTools.com aims to teach 50 individual project management skills through frameworks, tools and assessments.
Eating the elephant portfolio management 1 step at a time - Oracle Primave...p6academy
Portfolio management implementation requires taking small, incremental steps to avoid overwhelming users. The document recommends starting with a single process area and engaging stakeholders throughout. It also emphasizes managing expectations, establishing clear scope, and focusing on business change management to ease adoption. Continuous improvement is needed to expand functionality in a controlled manner as understanding grows.
Entroids Introduces the "Think-Plan-Do" framework for execution - A GPS for N...Entroids
This document introduces the Think-Plan-Do framework for managing new product development projects. The framework provides three tiers - Think, Plan, and Do - to link strategic project needs to tactical planning and daily actions. The Think tier identifies the key strategic needs through four pillars: business model, risks, requirements, and milestones. The Plan tier develops major tasks from the strategic needs. The Do tier focuses execution through a dashboard of small actions needed to complete tasks. Using this framework aims to spend less time planning and more time taking action through visual tools and accountability.
Entroids provides a Think-Plan-Do framework to help manage new product development projects. The framework links strategic project needs identified in "four pillars" (business model, risks, requirements, milestones) to tactical planning and daily actions. It separates major tasks from smaller actions to focus on what's important. Using visual tools and establishing routines helps teams spend less time planning and more time executing, improving accountability and focus on the right actions. The framework is designed to help projects navigate change and avoid wasted effort through lean and flexible execution.
The document discusses project management paradigms and approaches. It defines project management as having the customer agree that the project is "done" based on measures that are meaningful to them. It then discusses various frameworks for project management like PMI PMBOK, CMMI, Prince2, and Scrum. A key theme is that these approaches identify the work, plan the work, estimate costs, execute the work, measure performance, and adjust plans as needed while engaging stakeholders. The document advocates using deliverables-based planning with four core processes: identify capabilities and requirements, establish a project baseline, execute against the baseline, and manage changes.
Expectations from IT Team
Project Methodology - Why it is as important as the Technology for your Product
Gaps in Recent Graduates
How to bridge these gaps?
DISCUSSION POINTS:
1. UNDERSTANDING PROJECT BASICS
2. IMPORTANCE OF PROJECT MANAGEMENT
3. PROJECT MANAGEMENT KNOWLEDGE AREAS
4. PROJECT CONSTRAINTS
5. MAJOR CHALLENGES AND THE WAY FORWARD
Free Webinar on "Major Project Management Challenges and the Way Forward"
https://www.facebook.com/events/1240889433429450
Five immutable principles of project successGlen Alleman
All successful projects adhere to five immutable principles during their lifecycle. These principles are independent of any project or program domain or context in that domain. They are also independent of any project management or product development method as well, including Agile. They ask five questions that must have credible answers that establish the foundation for success. Without credible answers to these 5 questions, the project has little hope of success.
This document provides guidance on managing portfolio projects. It discusses key dimensions of project delivery including product, organization, process, and client/business needs. It emphasizes setting project levers in equilibrium to reduce risk and increase certainty. Successful delivery requires good processes, people, technology, and great leadership. The four essential disciplines of portfolio management are planning, resource management, financial management, and change management. Status reporting must be consistent to effectively manage projects. Challenges include applying a flexible rather than "one size fits all" methodology. Tips for programme managers include allowing time for decisions, surrounding oneself with good project managers, and clearly understanding goals and authority.
The document discusses best practices for running projects successfully. It emphasizes that projects should be run using a structured framework or methodology. This involves clearly defining the project scope, planning the execution, regularly reviewing progress, and tracking assumptions, risks, dependencies and other factors. It also stresses the importance of selecting the right people for projects and developing their leadership capabilities, as leadership is a key factor in determining project success.
The document discusses the challenges of modern project management. It begins by defining a project and the key characteristics. It then discusses project management processes according to PMI, including the five process groups. It outlines the typical project life cycle and what constitutes project success. Common reasons for project failure are listed, such as poor requirements, unrealistic timelines, and scope creep. The document then discusses project management maturity models from ad-hoc to optimized. Finally, it provides best practices for project management, such as managing stakeholders, risks, issues, and change, and the benefits of PMP certification.
Enterprise Project Management Solutions - Install and train, job done? by "Da...Project Controls Expo
Enterprise Project Management Solutions - Install and train, job done? by "David Dunning - Chairman for CPS, UK" at Project Controls Expo 2017, Arsenal Stadium, London
Discussion Paper PMO And Merger Projectstheteflonpm
The document discusses establishing a project management office (PMO) for a merger project. It recommends establishing a hierarchy of PMOs with different mandates that ultimately report to an enterprise PMO managed by a project director. The PMO would facilitate project teams, identify resource gaps, and ensure standards are followed for portfolio management, methodology, communication, and status reporting. It emphasizes the need for governance, defining projects and deliverables, and balancing autonomy with standardization.
The document discusses 7 keys to sustaining project excellence: 1) Establishing project management processes; 2) Defining an organizational structure with roles and responsibilities; 3) Selecting project management tools to support processes; 4) Ensuring capable people are in key roles; 5) Establishing involvement and communication guidelines; 6) Implementing project performance management; and 7) Leadership commitment to a high-performing project organization. The article provides examples of how organizations have implemented these keys to improve project success rates and better achieve business results. Sustaining excellence requires a long-term, comprehensive approach rather than a single quick fix.
Team Misfocus and Error in software projectsAdam Russell
we all know that software development projects often fail or are impaired, but what is the cause? There are many sources of error, and this presentation looks at team-based patterns of mis-focus on one part of the project at the expense of others. Observed from many software development projects over more than 20 years, this presentation will generate ideas for project review and alignment activities
Misfocus-caused error in software projectsAdam Russell
We know that many projects fail, or become impaired, but what is the reason given so many methodologies, tools and support systems. Error comes from many places. For whatever reason, teams create problems by investing more time in aspects of software development practice that have a smaller impact on project overall success, and accordingly invest less time in areas that have a larger impact.
GSC - Project Management for Startups and Small BusinessesKevin Murphy
Introducing project management to your startup or small business doesn’t have to mean a full-time hire or creating stacks of paperwork. You can take some small, simple steps on your own that will increase your productivity and on-time, on-budget delivery. We hope this brief overview presentation helps to get you started!
The document discusses software project management and provides 20 project management proverbs. It then defines what a project is and explains that projects have timeframes, require planning and resources, and need evaluation criteria. Finally, it discusses what a project manager does, including developing plans, managing stakeholders, teams, risks, schedules and budgets.
Winning 100% Buy-In from Staff and Board for your next Nonprofit Technology A...Norman Reiss
The document outlines 10 common scenarios for why a nonprofit technology adoption project may fail to gain full buy-in from staff and board members. These scenarios include a lack of planning for staff adoption and training after launch, not involving key stakeholders until late in the process, differing priorities between management and board, and failure to account for changes in business needs or organizational priorities. The best tip provided to ensure stakeholder buy-in is to start building relationships with stakeholders long before beginning any technology project.
Why Organization Structure Matters for Online Success (2 of 2)Norman Reiss
The document provides 5 organizational tips for effective digital media: 1) Include digital representatives in strategic planning, 2) Plan digital media campaigns in advance through calendaring, 3) Maintain a central repository of approved messaging, 4) Establish clear workflows for decision making in digital campaigns, 5) Crowdsource content creation from all levels of the organization.
Why your nonprofit needs a mobile websiteNorman Reiss
The document discusses why nonprofits need mobile websites to engage constituents who increasingly access the internet from mobile devices. It provides statistics showing large portions of users rely on mobile and recommends nonprofits check their own website statistics. The document then offers tips on planning a mobile site, such as using a content management system that can generate mobile-friendly content. It also provides examples of effective nonprofit mobile sites and best practices for design, testing, and resources.
The document outlines 20 tips for non-profits to kickstart their online fundraising in 20 minutes or less. The tips include creating an editorial calendar, tracking results across departments, coordinating online and offline appeals, obtaining email addresses from offline donors, limiting initial asks but getting more donor information later, and promoting recurring donations. The document stresses segmenting audiences, telling impactful stories, testing appeals, acknowledging donors, reporting on funds usage, and using technology like donor databases to improve fundraising.
How the NYPL Successfully Project Managed a Drupal Website RolloutNorman Reiss
The document discusses how the New York Public Library successfully managed the project of developing a new website using the Drupal content management system. It describes why Drupal was chosen, how management support was obtained and maintained, the organizational structure for the development process including use of outside vendors, and how content and staff training were handled. Lessons learned included allowing more time for content migration and training, and recognizing that website maintenance is ongoing.
Career management for project managers pmi westchesterNorman Reiss
The document summarizes Norman Reiss' presentation on career management for project managers. It outlines Reiss' job search process, lessons learned, and recommendations for using social media and tools like JibberJobber to organize networking activities, track target companies and job applications. The presentation also provides an overview of JibberJobber's features to help users manage their job search.
Selecting and implementing donor or membership databaseNorman Reiss
How a nonprofit organization can select and implement a donor / membership database, presented at the 2011 Congregations 2.0 Conference on Jan. 14, 2011
The document outlines Norman Reiss's presentation on social networking for IT managers at nonprofits. Some of the main points covered include focusing social media efforts on platforms where constituents engage like Facebook and Twitter, designating staff to manage accounts, devoting 2 hours per week minimum to see success, and using social media to engage constituents and communicate about the nonprofit's cause rather than just the organization. Resources for developing strategies and measuring results are also provided.
This document provides tips for non-profits to succeed with ePhilanthropy. It recommends optimizing online donations, reviewing email newsletter signup options, using email newsletter and multichannel strategies, keeping in touch with constituents on multiple platforms, promoting online fundraising, using web analytics, focusing on usability, and staying positive during economic downturns. It also discusses who typically drives online strategies at non-profits and the skills required for developing effective online strategies.
The document discusses best practices for online event registration and fundraising. It recommends setting up online registration well in advance, keeping registration forms simple, coordinating online and offline marketing, and personalizing registration confirmations. It also suggests maximizing fundraising by asking past participants to register again, offering prizes for fundraising, and appreciating top fundraisers. The document notes there are different types of events like pledge-based, non-pledge based, and third party events which organizations should make online registration available for.
1. Project ManagementProject Management
for Nonprofitsfor Nonprofits
Norman ReissNorman Reiss
Feb. 12, 2008 / updated May 2015Feb. 12, 2008 / updated May 2015
Nonprofit BridgeNonprofit Bridge
Bridging Technology, Communications & DevelopmentBridging Technology, Communications & Development
http://www.nonprofitbridge.comhttp://www.nonprofitbridge.com
nreiss@nonprofitbridge.comnreiss@nonprofitbridge.com
2. 2
Norman Reiss | Project Management for Nonprofits
Feb. 12, 2008 | updated May 2015
AgendaAgenda
IntroductionsIntroductions
Basic Project Management PrinciplesBasic Project Management Principles
Project Management for NonprofitsProject Management for Nonprofits
Project Management Techniques applied toProject Management Techniques applied to
Three Major Nonprofit InitiativesThree Major Nonprofit Initiatives
QuestionsQuestions (but welcome at any time)(but welcome at any time)
3. 3
Norman Reiss | Project Management for Nonprofits
Feb. 12, 2008 | updated May 2015
Introductions – Norman ReissIntroductions – Norman Reiss
Core strengths:Core strengths:
Internet / Web Site Strategies Internet / Web Site Strategies
Project ManagementProject Management
CMS / CRM Selection / ImplementationCMS / CRM Selection / Implementation
Moved to nonprofit in 2000 after corporate career, mostly inMoved to nonprofit in 2000 after corporate career, mostly in
financial services.financial services.
Received PMP certification in fall 2006Received PMP certification in fall 2006
Active member / speaker at Nonprofit Technology EnterpriseActive member / speaker at Nonprofit Technology Enterprise
Network, Project Management InstituteNetwork, Project Management Institute
Member of selection committee for Nonprofit Excellence AwardsMember of selection committee for Nonprofit Excellence Awards
Currently Project Manager at Center for Court InnovationCurrently Project Manager at Center for Court Innovation
4. 4
Norman Reiss | Project Management for Nonprofits
Feb. 12, 2008 | updated May 2015
Introductions – Norman ReissIntroductions – Norman Reiss
““When attending meetings of the Project Management Institute, rarelyWhen attending meetings of the Project Management Institute, rarely
have I heard much talk about nonprofit organizations or have I methave I heard much talk about nonprofit organizations or have I met
people who focus on nonprofits. Similarly, in my current organization,people who focus on nonprofits. Similarly, in my current organization,
I often have to explain the benefits of project management in planningI often have to explain the benefits of project management in planning
and implementing initiatives.and implementing initiatives.
““Project management would be helpful inProject management would be helpful in anyany organization yet nonprofitsorganization yet nonprofits
have been a bit slow to get on the bandwagon. One of the biggesthave been a bit slow to get on the bandwagon. One of the biggest
challenges I've faced recently is getting all stakeholders tochallenges I've faced recently is getting all stakeholders to
participate. If only a few people / departmentsparticipate. If only a few people / departments
dominate conversations, it is less likely that the results will bedominate conversations, it is less likely that the results will be
acceptable to all who are affected by its implementation.”acceptable to all who are affected by its implementation.”
From my blog, Nonprofit Bridge, March 6, 2007From my blog, Nonprofit Bridge, March 6, 2007
5. 5
Norman Reiss | Project Management for Nonprofits
Feb. 12, 2008 | updated May 2015
Introductions – About YouIntroductions – About You
Please introduce yourself:Please introduce yourself:
NameName
OrganizationOrganization
Project Management experience?Project Management experience?
For Profit? Not for Profit background?For Profit? Not for Profit background?
What you hope to learn from today’s sessionWhat you hope to learn from today’s session
6. 6
Norman Reiss | Project Management for Nonprofits
Feb. 12, 2008 | updated May 2015
Basic Project Management PrinciplesBasic Project Management Principles
7. 7
Norman Reiss | Project Management for Nonprofits
Feb. 12, 2008 | updated May 2015
Project Management PrinciplesProject Management Principles
PMBOK – Project Management Body of KnowledgePMBOK – Project Management Body of Knowledge
Characteristics of a ProjectCharacteristics of a Project
Temporary - definite beginning & endTemporary - definite beginning & end
Create unique product, service or resultsCreate unique product, service or results
Progressive elaboration – series of stepsProgressive elaboration – series of steps
Specific objective vs. ongoing operationsSpecific objective vs. ongoing operations
Project ManagementProject Management
Application of knowledge, skills, tools and techniques toApplication of knowledge, skills, tools and techniques to
meet project requirements.meet project requirements.
8. 8
Norman Reiss | Project Management for Nonprofits
Feb. 12, 2008 | updated May 2015
Project Management PrinciplesProject Management Principles
Project PlanProject Plan
StakeholdersStakeholders
Selecting Your TeamSelecting Your Team
Risk ManagementRisk Management
Communications StrategiesCommunications Strategies
probably the most important project management skillprobably the most important project management skill
Handling Change RequestsHandling Change Requests
Must have process in place from beginningMust have process in place from beginning
9. 9
Norman Reiss | Project Management for Nonprofits
Feb. 12, 2008 | updated May 2015
Project Management PrinciplesProject Management Principles
Project management involves:Project management involves:
Identifying requirementsIdentifying requirements
Establishing clear & achievable objectivesEstablishing clear & achievable objectives
‘‘Triple constraint’ – changing one must change others:Triple constraint’ – changing one must change others:
TimeTime
CostCost
ScopeScope
also Qualityalso Quality
Adjusting specifications, plans and approach to meetAdjusting specifications, plans and approach to meet
concerns / expectations of stakeholdersconcerns / expectations of stakeholders
10. 10
Norman Reiss | Project Management for Nonprofits
Feb. 12, 2008 | updated May 2015
Project Management TermsProject Management Terms
Program – group of related projects managed togetherProgram – group of related projects managed together
Portfolio – collection of projects and programs managedPortfolio – collection of projects and programs managed
togethertogether
Project Management Office (PMO) – oversees management ofProject Management Office (PMO) – oversees management of
projects, programs, or combination of bothprojects, programs, or combination of both
Scope Creep – have a formal process in place to evaluateScope Creep – have a formal process in place to evaluate
proposed changes then approve or reject.proposed changes then approve or reject.
Critical Path – tasks that must be done to finish project on timeCritical Path – tasks that must be done to finish project on time
11. 11
Norman Reiss | Project Management for Nonprofits
Feb. 12, 2008 | updated May 2015
Project Management ProcessesProject Management Processes
Initiating – defines, authorizes projectInitiating – defines, authorizes project
Planning – plans actions required to achieve objectivesPlanning – plans actions required to achieve objectives
and scopeand scope
Executing – integrates people and other resources toExecuting – integrates people and other resources to
carry out plancarry out plan
Monitoring / Controlling – regularly measures andMonitoring / Controlling – regularly measures and
monitors progress to identify variances from plan somonitors progress to identify variances from plan so
corrective action can be takencorrective action can be taken
Closing – formalizes acceptances of product, service orClosing – formalizes acceptances of product, service or
results and brings project to endresults and brings project to end
12. 12
Norman Reiss | Project Management for Nonprofits
Feb. 12, 2008 | updated May 2015
More Project Management ConceptsMore Project Management Concepts
Project objectives (SMART):Project objectives (SMART):
SpecificSpecific
MeasurableMeasurable
AchievableAchievable
RealisticRealistic
Time specificTime specific
Project manager often has no supervisory relationship over staffProject manager often has no supervisory relationship over staff
Reasons for project failureReasons for project failure
Fear – team members need to protect their own interestsFear – team members need to protect their own interests
Misaligned expectations – project deliverables not clear to allMisaligned expectations – project deliverables not clear to all
Confusion – over roles, responsibilities or processConfusion – over roles, responsibilities or process
Loss of momentum – problems not dealt with when they come upLoss of momentum – problems not dealt with when they come up
Team member job dissatisfactionTeam member job dissatisfaction
Lack of commitment to success of project – not part of ‘job description’Lack of commitment to success of project – not part of ‘job description’
13. 13
Norman Reiss | Project Management for Nonprofits
Feb. 12, 2008 | updated May 2015
Project Management ApproachesProject Management Approaches
Traditional / Waterfall – series of steps in linear sequenceTraditional / Waterfall – series of steps in linear sequence
Agile / Extreme / Radical – work best when requirements areAgile / Extreme / Radical – work best when requirements are
vague, organization is undergoing change, or risk is highvague, organization is undergoing change, or risk is high
Project split into small phasesProject split into small phases
Requirements modified as you goRequirements modified as you go
Constant interaction between developers and usersConstant interaction between developers and users
Short timeframesShort timeframes
Used mostly in software and web site developmentUsed mostly in software and web site development
Rapid feedback from usersRapid feedback from users
Adapt to change if you can’t predict itAdapt to change if you can’t predict it
Agile manifesto – www.agilemanifesto.orgAgile manifesto – www.agilemanifesto.org
14. 14
Norman Reiss | Project Management for Nonprofits
Feb. 12, 2008 | updated May 2015
Top 10 Reasons for Project SuccessTop 10 Reasons for Project Success
(Standish Group)(Standish Group)
User involvementUser involvement
Executive management supportExecutive management support
Clear business objectivesClear business objectives
Optimizing scopeOptimizing scope
Agile processAgile process
Project manager expertiseProject manager expertise
Financial managementFinancial management
Skilled resourcesSkilled resources
Formal methodologyFormal methodology
Standard tools and infrastructureStandard tools and infrastructure
15. 15
Norman Reiss | Project Management for Nonprofits
Feb. 12, 2008 | updated May 2015
Top 10 Project Management SkillsTop 10 Project Management Skills
(Tech Republic)(Tech Republic)
1. Define project1. Define project 6. Manage risks6. Manage risks
2. Plan work2. Plan work 7. Manage communication7. Manage communication
3. Manage work plan3. Manage work plan 8. Manage documentation8. Manage documentation
4. Manage issues4. Manage issues 9. Manage quality9. Manage quality
5. Manage scope5. Manage scope 10. Manage metrics10. Manage metrics
16. 16
Norman Reiss | Project Management for Nonprofits
Feb. 12, 2008 | updated May 2015
Project Management SoftwareProject Management Software
Microsoft ProjectMicrosoft Project
BasecampBasecamp
Central DesktopCentral Desktop
OmniPlan (Macintosh)OmniPlan (Macintosh)
DreamTeam (SalesForce add-in)DreamTeam (SalesForce add-in)
Active CollabActive Collab
Microsoft Office (Word, Excel etc.)Microsoft Office (Word, Excel etc.)
17. 17
Norman Reiss | Project Management for Nonprofits
Feb. 12, 2008 | updated May 2015
Dealing with StakeholdersDealing with Stakeholders
Stakeholder – individual or organization whoseStakeholder – individual or organization whose
interests may be affected by projectinterests may be affected by project
Importance of identifying all stakeholders at theImportance of identifying all stakeholders at the
beginning of projectbeginning of project
Project success depends on how you manageProject success depends on how you manage
stockholders, so engage them in decision making andstockholders, so engage them in decision making and
keep lines of communication open.keep lines of communication open.
Meet individually with stakeholders to advise of updatesMeet individually with stakeholders to advise of updates
and adjust expectations.and adjust expectations.
18. 18
Norman Reiss | Project Management for Nonprofits
Feb. 12, 2008 | updated May 2015
Managing NonprofitManaging Nonprofit
Technology ProjectsTechnology Projects
Stress-Free Technology Project Management forStress-Free Technology Project Management for
Nonprofits (Nten)Nonprofits (Nten)
Six Views of Project Management SoftwareSix Views of Project Management Software
(Idealware)(Idealware)
How Project Management Can Be Used AtHow Project Management Can Be Used At
Your Nonprofit (PMI Educational Foundation)Your Nonprofit (PMI Educational Foundation)
19. 19
Norman Reiss | Project Management for Nonprofits
Feb. 12, 2008 | updated May 2015
Project Management for Nonprofits?Project Management for Nonprofits?
20. 20
Norman Reiss | Project Management for Nonprofits
Feb. 12, 2008 | updated May 2015
Establishing Project ManagementEstablishing Project Management
Within Your OrganizationWithin Your Organization
Project success measured by whether objectives are metProject success measured by whether objectives are met
AND whether team members found work rewarding.AND whether team members found work rewarding.
Educate staff on how Project Management can helpEducate staff on how Project Management can help
If organization is not ‘project friendly,’ need moreIf organization is not ‘project friendly,’ need more
authority and/or money to succeed.authority and/or money to succeed.
PM isn’t only useful for technology projectsPM isn’t only useful for technology projects
PM isn’t the same as software developmentPM isn’t the same as software development
21. 21
Norman Reiss | Project Management for Nonprofits
Feb. 12, 2008 | updated May 2015
Establishing Project ManagementEstablishing Project Management
Within Your OrganizationWithin Your Organization
Don’t use IT terms with non IT peopleDon’t use IT terms with non IT people
Find a supporter on business sideFind a supporter on business side
Use a variety of communications techniquesUse a variety of communications techniques
Start small to build successesStart small to build successes
Must understand business side of organizationMust understand business side of organization
Address organization’s points of painAddress organization’s points of pain
22. 22
Norman Reiss | Project Management for Nonprofits
Feb. 12, 2008 | updated May 2015
‘‘Project Friendly’ OrganizationsProject Friendly’ Organizations
(Rob Purdie, Important Projects)(Rob Purdie, Important Projects)
Management balance between tasks & peopleManagement balance between tasks & people
Balance between output and processesBalance between output and processes
Teamwork / cooperation is focus vs. dept ‘silos’Teamwork / cooperation is focus vs. dept ‘silos’
Tolerance for conflict / taking risksTolerance for conflict / taking risks
23. 23
Norman Reiss | Project Management for Nonprofits
Feb. 12, 2008 | updated May 2015
Top Project Strategy MistakesTop Project Strategy Mistakes
Identifying a new technology, then trying to developIdentifying a new technology, then trying to develop
ways to apply itways to apply it
Failing to insure projects are business drivenFailing to insure projects are business driven
Failing to access projects and capabilities beforeFailing to access projects and capabilities before
committing to plan and schedulecommitting to plan and schedule
Not identifying possible risksNot identifying possible risks
Not learning from poorly performing projectsNot learning from poorly performing projects
Inadequate communication with business staffInadequate communication with business staff
Not integrating new systems with oldNot integrating new systems with old
Inadequate metrics, documentationInadequate metrics, documentation
24. 24
Norman Reiss | Project Management for Nonprofits
Feb. 12, 2008 | updated May 2015
Top 10 Technology ProjectsTop 10 Technology Projects
Which Apply to Nonprofits? (Baseline Magazine)Which Apply to Nonprofits? (Baseline Magazine)
Business Process Management /Business Process Management /
ImprovementImprovement
Break down business functions, figure out better ways ofBreak down business functions, figure out better ways of
executing them, building technology systems to do them.executing them, building technology systems to do them.
Disaster Planning / RecoveryDisaster Planning / Recovery
Preparing for the worst.Preparing for the worst.
Customer (Constituent) RelationshipCustomer (Constituent) Relationship
Management (CRM)Management (CRM)
Universal need of for profit and not for profit organizations.Universal need of for profit and not for profit organizations.
Intrusion Detection and PreventionIntrusion Detection and Prevention
Do you know where your laptops are and what information is onDo you know where your laptops are and what information is on
them?them?
Business Analytics / BusinessBusiness Analytics / Business
IntelligenceIntelligence
Analyzing what’s happening and figuring out how to respond.Analyzing what’s happening and figuring out how to respond.
Server UpgradesServer Upgrades
Are you prepared for organizational growth by increasingAre you prepared for organizational growth by increasing
capacity?capacity?
Desktop / Laptop UpgradesDesktop / Laptop Upgrades
Do you have a schedule or do you wait until something breaks?Do you have a schedule or do you wait until something breaks?
Enterprise Systems PlanningEnterprise Systems Planning
Getting systems to work together after a mergerGetting systems to work together after a merger
Web ServicesWeb Services
Early adopters – financial services, governmentEarly adopters – financial services, government
Financial ReportingFinancial Reporting
For nonprofits, how does your fundraising software talk to yourFor nonprofits, how does your fundraising software talk to your
accounting software?accounting software?
25. 25
Norman Reiss | Project Management for Nonprofits
Feb. 12, 2008 | updated May 2015
Project Management TechniquesProject Management Techniques
Applied to Three Major Nonprofit InitiativesApplied to Three Major Nonprofit Initiatives
26. 26
Norman Reiss | Project Management for Nonprofits
Feb. 12, 2008 | updated May 2015
Project Management Techniques Applied toProject Management Techniques Applied to
Three Major Nonprofit InitiativesThree Major Nonprofit Initiatives
Web Site RedesignWeb Site Redesign
Use of agile techniquesUse of agile techniques
Identifying and updating all stakeholdersIdentifying and updating all stakeholders
Introduction of Content Management SystemIntroduction of Content Management System
Planning who will update web sitePlanning who will update web site
Ease of use vs. total flexibilityEase of use vs. total flexibility
Introduction / Enhancement of ePhilanthropy ToolsIntroduction / Enhancement of ePhilanthropy Tools
Jointly involving all departments that will be affectedJointly involving all departments that will be affected
Selecting products that integrate with existing softwareSelecting products that integrate with existing software
How would project management strategies improve how projectsHow would project management strategies improve how projects
are implemented at your organization?are implemented at your organization?
27. 27
Norman Reiss | Project Management for Nonprofits
Feb. 12, 2008 | updated May 2015
Questions?Questions?
Nonprofit BridgeNonprofit Bridge
Bridging Technology, Communications & DevelopmentBridging Technology, Communications & Development
http://www.nonprofitbridge.comhttp://www.nonprofitbridge.com
nreiss@nonprofitbridge.comnreiss@nonprofitbridge.com