often translate requirements into epics and user stories to concisely define the desired system functions and provide the foundation for Agile estimation and planning. They describe what the users want developers, testers, and other stakeholders have a clear and agreed-upon understanding of the desired functions. They offer a far more dynamic approach to managing requirements than large requirements documents objective of creating a prototype might be to assess whether a COTS product can perform a particular function. In other cases, a prototype can evolve into the final product or be used in a future release.

iteration in establishing software requirements • Growing software organically, adding more and more functions to systems as they are run, used, and tested”Who said it?Frederick Brooks Jr. • Joined IBM in single part of building a software system is deciding precisely what to build • The most important function that software builders do for their clients is the iterative extraction and refinement of the

the next six-month release.  DO epics and user stories to concisely define the desired system functions and provide the foundation for Agile estimation and planning. o They describe what the users want developers, testers, and other stakeholders have a clear and agreed-upon understanding of the desired functions. They offer a far more dynamic approach to managing requirements than large requirements documents

 The practice team wasn’t the same as the game time team.  Segregated technical and business functions  Development  Operations (Operational Waterfall)  Infrastructure Ops  Product Ops  Product

work flow streamline interdepartmental communications, and effectively serve the other business functions at Parts Unlimited. Key Concepts The Three Ways [2] The First Way emphasizes the performance

OF DAILY WORK i. Create infrastructure to make it easy for Dev or Ops to create telemetry for functions built ii. Generate graphs with overlays of production changes iii. Tools – StatsD, JMX, codahale

developing the application iii. QA – team responsible for ensuring feedback loop exists to ensure functions as desired iv. Operations – the team responsible for maintaing the production environment and

how modern IT leaders succeed by driving business outcomes rather than operating an order-taking function. This shift in organizational mindset is critical to any successful technology transformation but

sizes compound effort needed to identify causes ii. Unit tests – test a single method, class, or function in isolation to ensure operates as designed iii. Acceptance tests – test application as a whole