| |
Public Product Management Training Day 2:
Working with Development
How do you guarantee an on-time product delivery with a feature-set
that meets your customers needs? Accurately translating market
needs into product requirements and delivering on time is
of huge value to your company. It increases product sales
and dramatically improves the efficiency of your product development
team. Day two of Tarigo’s product management training
course concentrates on the requirements process; how to build
a requirements document, write and prioritize requirements,
assess technical feasibility, and work with your company to
keep delivery dates on track. Tarigo’s product management
training provides the framework and real-world techniques
to help companies deliver on-time and on-target.

The Requirements Specification Process
This initial session sets out to define the importance of
a good requirements process, and the elements that go into
making that process work effectively. Delegates find out about
the risks and pitfalls in the requirements process, and the
huge benefits that the right process can bring to their company.
Walking through an end-to-end requirements process, delegates
learn how to implement the process and make sure it is used
consistently, improving product quality and product take-up.
Key areas covered:
- The benefits of a requirements process
- Efficiency gains through requirements
- Key elements of a requirements process
- Requirements process description

User Profiles and Scenarios
Product managers must understand who their customers are
and how those customers will use the product. Understanding
their customers’ level of technical skill, working environment,
and likes/dislikes leads to a product that better meets customer
needs. In this session delegates learn how to build User Profiles,
User Scenarios, and Use Cases to help clarify product requirements,
and how to use these tools to give a more complete picture
of product requirements to the development team
Key areas covered:
- Developing User Profiles and Scenarios
- Building Use Cases
- Using profile, user scenarios and profiles to support
development

Writing Accurate Requirements
When it comes to writing actual requirements, language is
important. Being too ambiguous, or describing an implementation
method, or using non-testable language all increase the chances
of the end product not meeting customer expectations. In this
session, delegates learn what makes a good requirement, how
to avoid the common mistakes, and how to structure the requirements
document so that it remains relevant throughout the product
lifecycle.
Key areas covered:
- What makes a good requirement?
- The language of requirements
- Structure a requirements document

Prioritization
No matter how well planned, requirements can change during
product development; new customers might have new requirements,
or issues may be uncovered at the design phase. Prioritization
is a great tool to help product managers’ deal with
change and manage risk. In this session, delegates are taught
how to produce and maintain a prioritized feature list, use
it to manage risk and requirement tradeoff, and how it can
assist in the early delivery of a product.
Key areas covered:
- Feature prioritization benefits
- Getting stakeholder support
- Managing risk with prioritization
- Maintaining priorities through the development lifecycle

Delivering On-Time and On-Target
Perhaps the most difficult aspect of product delivery is
ensuring that the product you define is delivered on time
and feature-complete. There are enormous pressures working
against you; external pressures from customers and competition
combine with internal pressures from development, sales, and
senior management. Couple this with limited visibility of
development progress, and the potential to miss delivery dates
or lose key product features becomes a very real threat. In
this session delegates investigate the reasons behind feature
and date changes, strategies to minimize their effect and
methods of working with development to gain real clarity on
progress versus plan.
Key areas covered:
- Why releases go off track
- Dealing with external pressures
- Dealing with internal pressures
- Gaining clarity of progress vs plan
|
|