• Skip to main content
  • Skip to header right navigation
  • Skip to site footer

Shaping Software

Tools, Frameworks, and Templates for Product Managers

  • About
  • The PM Framework
  • Articles & Hubs

Requirements

Customer-Connected Engineering Slides

Customer-Connected Engineering Slides (PDF Download)

Customer Connected Engineering (CCE) is a practices we use across our patterns & practices teams for engaging customers throughout the life cycle. We involved customers during the planning, development, and release of our deliverables. This is a draft slide set that shares how we do Customer Connected Engineering inside patterns & practices, including our key practices and guiding principles.

Read moreCustomer-Connected Engineering Slides (PDF Download)

Agile Architecture Method

The Agile Architecture Method is a way to bake quality into the life cycle. It's also an iterative and incremental approach for architecture and design. In its simplest form, it's a way to help you identify potential hot spots against your prioritized scenarios. The hot spots are key engineering decision. The main hot spots are cross-cutting concerns, such as data access, exception management, logging ... etc. and quality attributes, such as security, performance, reliability ... etc.

Read moreAgile Architecture Method

What’s a Scenario

Photo by Wonderlane What’s a scenario?  Not everybody uses the term “scenario” the same way.  In the software industry, there’s three common usages of scenario: The same as a use case. A path through a use case. An instance of a use case. Usually, the most helpful one is “an instance of a use case.”  …

Read moreWhat’s a Scenario
What is a Use Case

What is a Use Case?

“Use cases are to software what stories are to novels.” — Unknown As a software developer or a product manager, writing use cases can be an essential step in the development process to ensure that the software solution meets the needs of its users. Use cases can help you to understand the requirements of the …

Read moreWhat is a Use Case?
user requirements vs. system requirements

Why Differentiate User Requirements vs. System Requirements?

“Precision of communication is important, more important than ever, in our era of hair trigger balances, when a false or misunderstood word may create as much disaster as a sudden thoughtless act.” — James Thurber. As someone who has worked at Microsoft for several years, I’ve often found myself in debates over whether it’s necessary …

Read moreWhy Differentiate User Requirements vs. System Requirements?
  • Go to page 1
  • Go to page 2
  • Go to page 3
  • Next