Software Product Engineering and Management Flashcards

A set of vocabulary flashcards covering the core concepts of software product engineering, management roles, user-centric design tools (personas/scenarios), and feature development.

Software product

A generic software system that provides functionality useful to a range of customers.

Custom software

Software built for a specific external client/customer and their specific requirements.

Project-based software engineering

Software development where an external customer owns the requirements and a contractor builds the system.

Product-based software engineering

Software development that starts from a business opportunity, where the company decides what features to build and when to release them.

Software product line

A set of software products that share a common core but can be adapted for specific customers.

Platform

A software or software+hardware product that allows new applications to be built on top of it.

Stand-alone execution model

An execution model where the software runs entirely on the customer’s computer.

Hybrid execution model

An execution model where some features run on the customer’s computer, while others run on the developer’s servers.

Software service execution model

An execution model where all features run on the developer’s servers and users access them through a browser or mobile app.

Product vision

A simple statement that defines the essence of the product to be developed and answers what the product is, who the target customers are, and why they should use it.

Moore’s vision template

A specific template for defining product vision: FOR target customer, WHO has a need, THE product is a category, THAT gives a benefit, UNLIKE competitors, OUR PRODUCT has a key difference.

Domain experience

Knowledge gained from working in or understanding a specific area where the product will be used.

Product experience

Experience with existing products that helps developers identify improvements or new product ideas.

Software product management

A business activity focused on planning, developing, marketing, and managing software products.

Product manager

An individual who connects the business, customers, and development team, often focusing on outward customer needs.

Product vision management

The activity of managing and protecting the product vision so the product does not drift away from its original purpose.

Product roadmap

A strategic plan for product development, release, and marketing.

Product backlog

A prioritized to-do list of features or work that must be developed.

Acceptance testing

Testing conducted to verify that a software release meets roadmap goals and is efficient and reliable.

Customer testing

Giving a release to customers to get feedback on features, usability, and business value.

Product prototyping

Developing an early version of a product to test ideas and demonstrate market potential.

Feasibility demonstration prototyping

A prototype used to show that the product idea works and has useful features.

Customer demonstration prototyping

Extending a prototype to show specific customer features after learning more about users.

Software feature

A fragment of functionality that users may need or want.

User understanding

The process of learning about potential users, their work, and how they use software through techniques like interviews and surveys.

Persona

An imagined user that represents a type of person who might use the product, used to help developers empathize with users.

Proto-persona

A persona created from limited user information, often developed as part of a team exercise.

Scenario

A narrative describing how a user might use the system to achieve an objective from the user's perspective.

User story

A structured, fine-grain description of something a user wants from a software system, often following the format 'As a role, I want/need to do something'.

Epic

A user story that is too large for one sprint and must be broken down into smaller stories.

Feature identification

The process of creating a list of features that define the product.

Independent feature

A quality of a good feature where it does not depend on how other features are implemented or activated.

Coherent feature

A quality of a good feature where it focuses on one item of functionality and does not perform multiple unrelated things.

Relevant feature

A quality of a good feature where it supports tasks users normally need and does not obscure rarely used functionality.

User knowledge

Knowledge about what users want and how they may use the software.

Technology knowledge

Knowledge of current technologies that can enable new or improved features.

Simplicity vs functionality tradeoff

The balance between making a system easy to use and providing enough features to attract different users.

Familiarity vs novelty tradeoff

The balance between including familiar tasks users expect and introducing new features that differentiate the product from competitors.

Automation vs control tradeoff

The balance between automatic system behavior and providing user control and customization.

Feature creep

The act of adding new features without considering if they are generally useful, often leading to a product that is harder to use.

Vision drift

A situation where changes cause the product to move away from its original product vision.