Division of the EU’s European Commission Used Material Developed by Scott M. Graffius

BY SCOTT M. GRAFFIUS | ScottGraffius.com

European Commission Using Material Developed by Scott M. Graffius - LwRes

black_spacer_lr_sq_v3
Strategic objectives play a crucial role in guiding organizations towards achieving their vision and mission. They’re fulfilled by projects, endeavors undertaken to create a unique product, service, or result.

The art and science of project management (Agile or otherwise) — the application of knowledge, skills, tools, and techniques to projects — is indispensable for the management and completion of projects. And tools can make a significant contribution to successful outcomes.

In 2007, Scott M. Graffius developed a fresh take on RACI charts, a simple project management tool. His unique material provides audiences with practical information they can use to leverage RACI charts to help manage complexities and achieve success. Graffius periodically refreshes his work. In 2020, he published an updated version on
ResearchGate, a European platform for researchers and scientists.

Graffius' respective work is
here and citation information follows:

Graffius, Scott M. (2020). How the RACI Tool Can Help You: Use RACI to Establish Roles and Responsibilities—and Improve Outcomes—for Projects and Other Work. Los Angeles, California: Exceptional PPM and PMO Solutions. DOI: 10.13140/RG.2.2.14713.62561/4.

A division of the EU’s European Commission, Erasmus+, used Graffius' material in one of their publications. Their work is
here and select visuals follow.

EU EC Features Work by Scott M Graffius - Excerpts - 1 - LwRes

The cover page is shown above.

EU EC Features Work by Scott M Graffius - Excerpts - 2 - LwRes

Page 13 is shown above.

EU EC Features Work by Scott M Graffius - Excerpts - 3 - LwRes

A zoomed-in version visual of page 13 is shown above.

About the European Commission

The European Commission (EC) is the governing body of the European Union (EU). It represents and upholds the interests of the EU as a whole and it is independent of national governments. The EC prepares legislation for adoption by the Council (representing the member countries) and the Parliament (representing the citizens). It administers the budget and the policy programs in cooperation with authorities in the member countries. The EC has an administrative body of about 32,000 European civil servants. Visit https://commission.europa.eu to learn more.

About Erasmus+

Erasmus+ (which is short for "EuRopean Community Action Scheme for the Mobility of University Students") is the European Union’s program to support education, training, youth, and sport in Europe. To learn more, visit https://erasmus-plus.ec.europa.eu.

About ResearchGate

Started in 2008, ResearchGate is a platform for researchers and scientists to connect, collaborate, and share their work. It reports, "Our mission is to connect the world of science and make research open to all." Visit
https://www.researchgate.net to learn more.

How to Cite This Article

Graffius, Scott M. (2024, April 1). Division of the EU’s European Commission Used Material Developed by Scott M. Graffius. Available at:
https://scottgraffius.com/blog/files/eu-2024.html. DOI: 10.13140/RG.2.2.23115.40488.

black_spacer_lr_sq_v3

blazing-fast-gdn-1000x1000

980x120

black_spacer_lr_sq_v3

About Scott M. Graffius

ScottGraffius-181024_1000x1000_152KB-lowres-sq

Scott M. Graffius, PMP, SA, CSP-SM, CSP-PO, CSM, CSPO, ITIL, LSSGB is an agile project management practitioner, consultant, thinker, creator, multi-award-winning author, and international public speaker. Founder and CEO of Exceptional PPM and PMO Solutions™ and subsidiary Exceptional Agility™, he has generated over $1.9 billion for Global Fortune 500 businesses and other organizations he has served. Graffius and content from his books, talks, workshops, and more have been featured and used by Microsoft, Oracle, Broadcom, Cisco, Gartner, Project Management Institute, IEEE, National Academy of Sciences, United States Department of Energy, Yale University, Tufts University, and others. He delights audiences with dynamic and engaging talks and workshops on agile project management, AI, Tech leadership, video game development, strategic alignment, the science of high performance teams, and more. To date, he's presented sessions at 89 conferences and other events across 25 countries.

His full bio is available
here.

Connect with Scott on:


Scott M Graffius on X - SG on X Design 2 - v Feb 7 2024 - LwRes

Scott M Graffius - Impact_com Platform for Influencers and Affiliates - v April 7 2024 - rev April 10 2024 - LwRes

black_spacer_lr_sq_v3

About Agile Scrum: Your Quick Start Guide with Step-by-Step Instructions

Scott_M_Graffius_Agile_Scrum_v22123007_LR_1000x1000_sq

Shifting customer needs are common in today's marketplace. Businesses must be adaptive and responsive to change while delivering an exceptional customer experience to be competitive.

There are a variety of frameworks supporting the development of products and services, and most approaches fall into one of two broad categories: traditional or agile. Traditional practices such as waterfall engage sequential development, while agile involves iterative and incremental deliverables. Organizations are increasingly embracing agile to manage projects, and best meet their business needs of rapid response to change, fast delivery speed, and more.

With clear and easy to follow step-by-step instructions,
Scott M. Graffius's award-winning Agile Scrum: Your Quick Start Guide with Step-by-Step Instructions helps the reader:

  • Implement and use the most popular agile frameworkโ€•Scrum;
  • Deliver products in short cycles with rapid adaptation to change, fast time-to-market, and continuous improvement; and
  • Support innovation and drive competitive advantage.

Hailed by Literary Titan as “the book highlights the versatility of Scrum beautifully.”

Winner of 17 first place awards.

Agile Scrum: Your Quick Start Guide with Step-by-Step Instructions is available in paperback and ebook/Kindle in the United States and around the world. Some links by country follow.



black_spacer_lr_sq_v3

About
Agile Transformation: A Brief Story of How an Entertainment Company Developed New Capabilities and Unlocked Business Agility to Thrive in an Era of Rapid Change

Scott_M_Graffius_Agile_Transformation_LR_1000x505

Thriving in today's marketplace frequently depends on making a transformation to become more agile. Those successful in the transition enjoy faster delivery speed and ROI, higher satisfaction, continuous improvement, and additional benefits.

Based on actual events,
Agile Transformation: A Brief Story of How an Entertainment Company Developed New Capabilities and Unlocked Business Agility to Thrive in an Era of Rapid Change provides a quick (60-90 minute) read about a successful agile transformation at a multinational entertainment and media company, told from the author's perspective as an agile coach.

The award-winning book by
Scott M. Graffius is available in paperback and ebook/Kindle in the United States and around the world. Some links by country follow.



black_spacer_lr_sq_v3

The short link for this article is:
https://bit.ly/eu-2024

© Copyright 2024 Scott M. Graffius. All rights reserved. This material may not be published, broadcast, rewritten or redistributed without the express written permission of Scott M. Graffius.



custom - back to main page of blog


What Are Your Chances of Project Success? [From the Archives - First Published in 2003]

ScottGraffius_Com - From the Archives - Chances of Project Success - 2003 - LwRes



black_spacer_lr_sq_v3

This article was first published on 12 July 2003.

black_spacer_lr_sq_v3

The Standish Group provides research reports valued by those in technology management. In their
Chaos Report and the follow-up Compass Report, Standish reported the top 10 criteria for project success.

This unique self-assessment is based on Scott M. Graffius' professional experience and Standish's findings. You're invited to take it to identify your project's success potential.

Note: This tool is tailored for projects utilizing a waterfall or hybrid approach and is not applicable to agile projects.

User Involvement

  • Are the right users involved?
  • Additionally, are the right users involved early and often?
  • Are there good relationships with the users?
  • Is involvement easy (frictionless)?
  • Are the users’ needs uncovered?

___ total items with a “Yes” x 3.8 = ___.

Executive Management Support

  • Is the right key executive(s) involved?
  • Does the key executive(s) have a stake in the outcome?
  • Does the project team have a stake as well?
  • Is there a well-defined project plan?
  • Is it understood that failure is a possibility?

___ total items with a “Yes” x 3.2 = ___.

Clear Statement of Requirements

  • Is there a concise vision?
  • Is there a business case?
  • Is there a functional analysis?
  • Is there a risk assessment?
  • Have metrics been identified for tracking and reporting?

___ total items with a “Yes” x 3.0 = ___.

Proper Planning

  • Is there a problem/pain/opportunity statement?
  • Is there a solution statement?
  • Have the right team members been assigned to the project?
  • Is there a firm specification/requirements?
  • Are there attainable milestones?

___ total items with a “Yes” x 2.2 = ___.

Realistic Expectations

  • Are the specifications/requirements clear?
  • Prioritization of needs? (While the default plan is to fulfill all requirements, the importance/value of each one should be quantified or qualified so that the most important items are prioritized.)
  • Are there small/manageable milestones?
  • Is change manageable (through a change management process or otherwise)?
  • Can the project be prototyped or delivered in phases or incrementally?

___ total items with a “Yes” x 2.0 = ___.

Small Milestones

  • Is the 80/20 rule observed (focus on the 20% of features that result in 80% of the benefit)?
  • Is top-down design used?
  • Are time limits set?
  • Is a prototype tool used?
  • Can progress be objectively measured?

___ total items with a “Yes” x 1.8 = ___.

Competent Staff

  • Has a gap analysis on skills been done (and needed skills identified, if applicable)?
  • Are the right people on the team?
  • Is there a training program or otherwise an opportunity for team members to level up their skills?
  • Are there appropriate incentives?
  • Is the team appropriately skilled/equipped/available to see the project to completion?

___ total items with a “Yes” x 1.6 = ___.

Project Ownership

  • Are roles for team members defined?
  • Are roles for those involved with the project but not a member of the team (such as sponsors or executives) also defined?
  • Does everyone have a good understanding of they will collaborate and contribute on the project?
  • Are incentives tied to success?
  • Is everyone involved committed?

___ total items with a “Yes” x 1.2 = ___.

Clear Vision and Objectives

  • Is the vision shared?
  • Is the vision aligned with the organization’s goals?
  • Are objectives achievable?
  • Are objectives measurable?
  • Are sanity checks/gates in place?

___ total items with a “Yes” x 0.6 = ___.

Focused Staff

  • Are there incentives?
  • Is there a focus on the deliverables?
  • Does each team member have part ownership?
  • Is everyone working together?
  • Is confidence being built as the team progresses?

___ total items with a “Yes” x 0.6 = ___.

Add all of the points to obtain the final score. Total score is ____ out of a maximum of 100 points.

Results range from 100 to 0, with 100 being the ideal for the project's success potential.

It is suggested that projects with a score less than 90 are revisited, and that challenges or impediments are resolved.

black_spacer_lr_sq_v3

How to Cite This Article

Graffius, Scott M. (2016, January 2). What Are Your Chances of Project Success? [From the Archives - First Published on 12 December 2012]. Available at:
https://scottgraffius.com/blog/files/archive---chances-of-project-success.html.
black_spacer_lr_sq_v3

© Copyright 2016 Scott M. Graffius. All rights reserved. This material may not be published, broadcast, rewritten or redistributed without the express written permission of Scott M. Graffius.





custom - back to main page of blog





Typical Software Development Risks: Symptoms, Causes, Indicators, and Mitigations [From the Archives - First Published in 2012]

ScottGraffius_Com - From the Archives - Typical Software Development Risks and Mitigations - LwRes



black_spacer_lr_sq_v3

This article was first published on 16 December 2012.

black_spacer_lr_sq_v3

The risks for software development projects can vary. However, this article provides a view of the
typical risks along with the respective symptoms, root causes, leading indicators, and mitigations for each.

Risk: Inaccurate effort and estimates and schedules

  • Symptoms to watch for: Pattern of late deliverables; lack of awareness of schedule and status.
  • Potential root cause: Schedules based on business ('top down') need rather than team-generated ('bottom up').
  • Leading indicators: Earned value - schedule performance index (SPI).
  • Mitigations: 'Bottom up' planning; monitor effort and schedule; engage earned value for monitoring, control as needed.

Risk: Unconstrained requirements growth

  • Symptoms to watch for: Development staff cannot keep up with requirements changes.
  • Potential root cause: Requirements change not well-managed.
  • Leading indicators: Requirements change rate.
  • Mitigations: Plan for change (employ a requirements/change control process); don't start development until there is a stable set of requirements.

Risk: Dysfunctional organization

  • Symptoms to watch for: High project staff turnover; frequent staff reassignments; poor work environment; low productivity; staff lacks necessary skills and experience; and key role(s) are vacant.
  • Potential root cause: Lack of motivating work environment; poor management of project prioritization; lack of experience with work needed on project.
  • Leading indicators: Project staff turnover compared with historical trend; productivity; project team does not have an appropriate understanding of the requirements and project status.
  • Mitigation: Monitor, manage, and control issues and risks; status reporting; external (peer) assessment of project plans.

Risk: Poor software quality

  • Symptoms to watch for: High test defect counts; significant rework.
  • Potential root cause: Focus on schedule rather than quality.
  • Leading indicators: Test inspection yield; test defect density; defect discovery and closure rates/profiles.
  • Mitigation: Create a development quality plan that focuses on inspection rather than (only) test; measure and track against quality plan; cultivate a focus on software quality.

Risk: Under-performance

  • Symptoms to watch for: Low productivity.
  • Potential root cause: Technical complexity; development environment changes; under-achievement.
  • Leading indicators: Earned value - cost performance index (CPI).
  • Mitigation: Engaged earned value, control as needed.

Manage risks and you'll greatly improve the probability of success.

black_spacer_lr_sq_v3

How to Cite This Article

Graffius, Scott M. (2016, January 2). What Are Your Chances of Project Success? [From the Archives - First Published on 16 December 2012]. Available at:
https://scottgraffius.com/blog/files/archive---software-development-risks-and-mitigations.html.

black_spacer_lr_sq_v3

© Copyright 2016 Scott M. Graffius. All rights reserved. This material may not be published, broadcast, rewritten or redistributed without the express written permission of Scott M. Graffius.





custom - back to main page of blog