Product Design Management for Agile Practitioners

This is a very brief introduction of what will be covered in this section of the course.

This lecture introduces the product life cycle and explains its key phases in the context of tangible engineered products.

This lecture elaborates on an alternate perspective of the product life cycle.

In this lecture, we will explain another perspective of the product life cycle that views it from a sales and product maturity standpoint. We will also discuss some implications of technical debt as a function of the product maturity curve.

In this lecture, we will make a pit-stop by the topic of the requirements life cycle. We will expose a simple model of this very important life cycle and share some important tips and examples of the need for capturing 'through-life' product requirements.

This lecture exemplifies a powerful tool traditionally used in design & manufacturing engineering for mapping across the 'voice of the customer' and the 'voice of the engineer'. The tool is called the House of Quality and can readily be applied in the area of software product management.

This lecture introduces what will be covered in the Product Strategy sections of the course.

SWOT stands for strengths, weaknesses, opportunities and threats and is a tool used for product positioning. In this lesson, we will first expose classic SWOT analysis and then focus on explaining a more objective approach for conducting SWOT.

Commercial acumen is quite key when operating in agile product management. One quite straightforward approach of determining the financial viability of some product sales model is through conducting break-even analysis. This lecture, therefore, provides an overview of product break-even analysis.

In this lecture, we will extend the discussion on the application of product break-even analysis.

In this lecture, we will go through the concept of technology readiness which is an important definition that describes the maturity of a technology in regard to its particular application. 

This lecture is a continuation of the previous one on technology readiness.

This is the first part of four lectures on the product roadmap and introduces the concept.

This is the second part of four lectures on the product roadmap, which explains the phase-based roadmap and period-based roadmap.

This is the third part of four lectures on the product roadmap, which explains the idea of swim-lane roadmap using Trello.

This is the fourth part of four lectures on the product roadmap, which further elaborates on the idea of swim-lane roadmap using Trello.

This lecture provides examples of other kinds of product roadmap formats which you may find useful.

This lecture will discuss the whole idea of presenting the product roadmap and provides various tips on the importance of doing so.

This lecture introduces what will be covered in the Product Tactics section of the course.

This lecture introduces the concept of attribute analysis and identifies the need for doing multi-attribute analysis in agile due to the multifaceted nature of requirements and stakeholder needs to be evaluated and prioritised.

In this lecture, we will expose the radar chart method for conducting multi-attribute analysis.

This is a continuation of the previous lecture on the radar chart method for conducting multi-attribute analysis.

A software product can be considered from multiple different perspectives depending on the audience or stakeholders 'viewing' the product. The proper embodiment of a product can be achieved by capturing its multiple perspectives.

Reference models can be used to capture 'blueprints' for representing knowledge. These are more formally known as 'ontologies', which provide a basis for sharing meaning and representing subject matter. In this lecture, we will encounter and explain one such reference model applied to a product context.

This is a continuation of the topic of multi-viewpoint product embodiment design focusing on architecture diagrams.

This is a continuation of the topic of multi-viewpoint product embodiment design focusing on business process modelling techniques.

This is a continuation of the topic of multi-viewpoint product embodiment design focusing on data and information flow modelling techniques.

This is a continuation of the topic of multi-viewpoint product embodiment design focusing on domain modelling and semantic modelling techniques.

This is a continuation of the topic of multi-viewpoint product embodiment design that provides a glimpse of the exciting area of user interface design.

In this lesson, you will learn conceptually what showcases are, why they are important and the considerations for conducting (or participating in) one of them.

This lecture touches on two aspects of technology change management namely user acceptance testing (UAT) and release management.

This lecture explains the essence of change control, which is another aspect of technology change management. We will also swing by an expectation-setting model to aid you in the process of raising requests for product changes.

This lesson introduces the topic of root cause analysis (RCA) and identifies its general importance.

A key technique used in root cause analysis for product quality management is Ishikawa. This lecture kicks off the explanation of this easy-to-use technique. 

This is a continuation of the explanation on Ishikawa.

This lecture provides a cheat-sheet of a number of direct and indirect applied techniques for conducting root cause analysis.

Critical path analysis (CPA) is a technique typically used in the area of project management to understand and analyse flows of activities required in order to achieve a goal. In this section, we will look at an application of CPA as a troubleshooting analysis technique. This lecture, therefore, introduces the concept of CPA.

This is the second part of the explanation of CPA where we will show how the basics of a network diagram is mapped.

This is the third part of the explanation of CPA where we will show how to identify the critical path.