Amazon Project Teams - Revision history

Marcin at 21:42, 15 August 2019

2019-08-15T21:42:19Z

← Older revision		Revision as of 21:42, 15 August 2019
Line 1:		Line 1:
			Keep team size to that which can be fed by two pizzas (4-10 people).

			http://blog.idonethis.com/two-pizza-team/

	Work is done by small teams. (Amazon famously describes these as “two-		Work is done by small teams. (Amazon famously describes these as “two-
	pizza teams,” that is, teams small enough to be fed by two pizzas.) These teams		pizza teams,” that is, teams small enough to be fed by two pizzas.) These teams

Marcin at 18:00, 16 January 2018

2018-01-16T18:00:37Z

← Older revision		Revision as of 18:00, 16 January 2018
Line 4:		Line 4:
	to accomplish. Any project at Amazon is designed via a “working backwards”		to accomplish. Any project at Amazon is designed via a “working backwards”
	process. That is, the company, famous for its focus on the customer, starts with a		process. That is, the company, famous for its focus on the customer, starts with a
	press release that describes what the finished product does and why. (If it’s an		'''press release''' that describes what the finished product does and why. (If it’s an
	internal-only service or product, the “customer” might be another internal team.)		internal-only service or product, the “customer” might be another internal team.)
	Then they write a ~~“Frequently~~ Asked ~~Questions”~~ document. They create mock-		Then they write a '''Frequently Asked Questions''' document. They create '''mock-
	ups and other ways of defining the customer experience. They go so far as to		ups''' and other ways of defining the customer experience. They go so far as to
	write an actual user manual, describing how to use the product. Only then is the		write an actual '''user manual''', describing how to use the product. Only then is the
	actual product green-lighted. Development is still iterative, informed by		actual product green-lighted. Development is still iterative, informed by
	additional data from actual users as the product is built and tested, but the		additional data from actual users as the product is built and tested, but the
Line 14:		Line 14:

	-from Tim O'Reilly, What the Future, 2018.		-from Tim O'Reilly, What the Future, 2018.

			So in summary:

			#Press release
			#FAQ
			#Mockups
			#User Manual

Marcin at 02:15, 16 January 2018

2018-01-16T02:15:23Z

← Older revision		Revision as of 02:15, 16 January 2018
Line 13:		Line 13:
	promise of the final product is where everything starts.		promise of the final product is where everything starts.

	-from O'Reilly, ~~WTF?~~		-from Tim O'Reilly, What the Future, 2018.

Marcin at 05:56, 15 January 2018

2018-01-15T05:56:09Z

← Older revision		Revision as of 05:56, 15 January 2018
Line 12:		Line 12:
	additional data from actual users as the product is built and tested, but the		additional data from actual users as the product is built and tested, but the
	promise of the final product is where everything starts.		promise of the final product is where everything starts.

			-from O'Reilly, WTF?

Marcin: Created page with "Work is done by small teams. (Amazon famously describes these as “two- pizza teams,” that is, teams small enough to be fed by two pizzas.) These teams work independently,..."

2018-01-15T05:55:20Z

Created page with "Work is done by small teams. (Amazon famously describes these as “two- pizza teams,” that is, teams small enough to be fed by two pizzas.) These teams work independently,..."

New page

Work is done by small teams. (Amazon famously describes these as “two-
pizza teams,” that is, teams small enough to be fed by two pizzas.) These teams
work independently, starting with a high-level description of what they are trying
to accomplish. Any project at Amazon is designed via a “working backwards”
process. That is, the company, famous for its focus on the customer, starts with a
press release that describes what the finished product does and why. (If it’s an
internal-only service or product, the “customer” might be another internal team.)
Then they write a “Frequently Asked Questions” document. They create mock-
ups and other ways of defining the customer experience. They go so far as to
write an actual user manual, describing how to use the product. Only then is the
actual product green-lighted. Development is still iterative, informed by
additional data from actual users as the product is built and tested, but the
promise of the final product is where everything starts.