Remove 2007 Remove Agile Remove Software Review Remove Systems Review
article thumbnail

A Better Problem Statement Template

Tyner Blain

In 2003, Managing Software Requirements: A Use Case Approach by Leffingwell and Widrig (p.101) Scaled Agile shares a narrative, free-form approach (figure 4) for problem statement writing. Dean references his work from 2007 & 2011 in support of this page. 101) introduced a slightly different syntax.

article thumbnail

What Makes Amazon’s Product Strategy So Sticky?

ProductPlan

Open 24 hours a day, the site was user-friendly, encouraging browsers to post their own reviews of books and offering discounts, personalized recommendations, and searches for out-of-print books.”. And in 2007, the Kindle, Amazon’s digital book reader, was launched. Accountability and empowerment fuel an agile environment.

Insiders

Sign Up for our Newsletter

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

Trending Sources

article thumbnail

Seeing Around Corners | Rita McGrath | BoS USA 2019

Business of Software Conference

She is also one of the most regularly published authors in the Harvard Business Review. Do you empower small, agile teams? Want us to let you know about new talk videos, speaker AMAs, Business of Software Conference and other event updates? There was no sort of software there. Upcoming Events. Unsubscribe anytime.

article thumbnail

The Rise & Fall Of Enterprise Software | Bill Janeway, Warburg Pincus | BoS Europe 2018

Business of Software Conference

There are few people as qualified to talk about the landscape of software investment as Bill Janeway. On joining Venture Capital firm Warburg Pincus in 1988 he built their IT Investment practice, which focussed heavily on Enterprise Software. The Rise And Fall Of Enterprise Software”. Upcoming Events.

article thumbnail

Launching a New Breakout Product | Jason Fried | BoS USA Online 2020

Business of Software Conference

And then you just lose track of who’s doing what and what’s due when and you don’t know where the feedback is. In 2007, we launched Highrise; we launched a new product every year for like four or five years, basically. And we were just using email, phone calls, in person meetings. And it was a mess. That worked well.