
In this lecture you'll:
Meet your instructor
Introduction about this topics
Go over the course sections and how the lectures will be organized
In this lesson, you'll learn:
What is demand management?
Where does it fall within the other IT processes?
What are the outcomes of demand management?
In this lecture you'll:
Learn the 3 stage lifecycle of a work item
In this lecture you'll:
Learn the 4 phases of demand management
Understand the activities and decision points in each phase
In this lecture, you'll:
Review the work item lifecycle and demand management framework concepts
Learn about a demand funnel
Understand how the work item lifecycle and demand management framework work together
Identify what work is in your pipeline, its source and begin analyzing where the pain points are in your current work intake process.
In this lecture you'll:
Learn the roles which support Demand Management
Identify in which phases the roles participate
List the demand management related responsibilities of each role
In this lecture you'll learn more about scaling your demand management process to include decision paths for types of work that will come through your demand funnel.
This lesson expands on the Explore phase introduced in the Simple Demand Management Framework by incorporating structured practices from ISO’s Idea Management standard (ISO 56007). You’ll learn how to move beyond one-time approvals and rubber-stamp meetings by applying a thoughtful, scalable approach to evaluating ideas.
By the end of this lesson, you’ll rethink the Explore phase as a continuous, non-linear set of activities that filter and shape the right ideas to pursue. You’ll be better equipped to scale your intake process which will ensure that your team invests in ideas that truly make sense for the organization.
This lesson will introduce you to types of ideas that may come through your demand management process. These types will help you plan how best scale your demand management activities decision paths so they are sized appropriately for the idea.
In this lesson, you'll understand:
Planned and Unplanned work
how they should be handled in your demand management process
In this short wrap-up, I give you some final thoughts on scaling your demand management process.
Case study scenario: Poorly defined ideas result in incorrect estimates and solutions which aren't discovered until Execution.
Case study scenario: The Business has little interest and no resources to evaluate the ideas being submitted to IT.
Case study scenario: Decision making for work is done per request which requires a significant amount of overhead and staggered planning cycles.
Case study scenario: the IT/Business Review team isn't sure how they would solve the approved proposal which results in delayed or incorrect high level estimates.
In this case study, you'll hear the problems created when demand approvals were rubber stamped without regard to capacity and learn how the organization created objective measures so that demand would meet capacity.
Case study scenario: Unplanned changes are going straight to production without any oversight which is causing business disruption.
If Demand Management is about "demand" then Execution frameworks, like Agile, are all about supply. In this lesson, we'll answer the question "how do Demand Management and Agile work together?"
In this lesson, you’ll learn about
Basic demand management metrics
Planning for future demand management metrics
The importance of a demand management tool to your reporting
We've reached the end of this course. In this last short lecture, we'll wrap up loose ends and review your next steps so you can implement this demand management framework in your organization.
Description
Are you having trouble managing your incoming software development work?
Are bad or poorly developed ideas or features wasting your team's time?
Do you have more projects than you can finish?
Do you have lots of emergencies?
Do you have multiple ways that work is submitted, tracked and managed?
Do you have trouble determining what the priorities are?
Or, do you know that your IT work in-take processes could be improved but don’t know where to start to fix them?
This course can help you!
This course introduces a simple 4-phase framework that, when introduced, has shown time and time again to not only improve the delivery problems defined above but also improve the quality of the work coming into IT.
Every part of an organization has IT needs. Many IT teams try to deliver everything that comes in at a time when IT departments are straining under the weight of reduced staff and budget. Some IT teams try to solve the problem by adding more people. The problem to solve isn't increasing capacity. It's:
ad hoc processes for accepting and prioritizing work in-take
poorly defined work requests
operational and process work compete for the same resources and time
Simply put, when you have better quality requests coming through your work in-take, delivery becomes repeatable, sustainable and consistently adds value for the organization.
You're probably saying to yourself, "Another process! How does that add value?"
I've had IT leaders tell me that want to stay "agile" so they don't implement processes. Well, you can't solve the problems identified above by doing the same things that got you to this place. Come on, even the Agile Manifesto doesn't say no process.
The 4-phase framework gives organizations easy guardrails and gates to get them started. You can choose how and when to scale as you see improvements in quality and delivery. This course will teach you how to do that too.
You'll hear real life case studies in this course that you may encounter when rolling out this framework so you understand how to solve those problems. And finally you will get a starting point for some KPIs (key performance indicators) and other metrics so you can show your organization how this improving not just delivery but also the quality of the changes you are requesting.
In this course, you will learn…
What IT Demand Management process, where it falls in the software delivery lifecycle and its purpose
How ideas become work items and why that lifecycle is important to committing to the work
The primary roles that support IT Demand Management and their responsibilities
A simple 4 phase process framework for demand management that will work for every organization
The high-level activities and key decisions that define each phase of Demand Management and how that impacts work coming through the process
Different categories of work that come into an organization and how to apply these to your demand management activities
How to scale the IT Demand Management process for different types of projects that flow through the process
Hear case studies of common demand management issues and how they were solved
Understand how Demand Management works with Agile and innovation practices
Learn some key metrics to start reporting on the benefits of your Demand Management process
By the end of the course, you will . . .
Create a backlog of the work that has been requested of your IT teams
Draft your organization’s demand management process
Identify the roles and responsibilities you'll need to support your Demand Management process
Know the common challenges that come up in demand management and what steps to take to address them
You’ll have a set of actionable plans and artifacts to start a Demand Management practice at your organization.
Who this course is for:
Portfolio managers, Program managers, and Project Managers
Product Managers, Product Owners, Business Analysts and other roles who are responsible for defining, managing or reporting on work in-take.
Innovation leaders who are accountable turning ideas into deliverable features
IT or Business Managers who request technology work.
IT leaders who are inundated with projects that all seem to have the same priority
IT managers and supervisors who lead teams that are accountable for the delivery of projects
And, finally, developers, engineers and tech teams, this course is for you too. This course helps ensure the work coming your way is clear, prioritized, and actually doable, so you can spend less time firefighting and more time building quality solutions.