development process. User Story – Description of functionality a user wants, small enough to complete in a single sprint Epic – A large user story often defined for a release that spans multiple sprints the size of the stories to determine the team's velocity: the number of story points the team can complete in a sprint. This enables the team to plan the amount of work to accomplish in the next sprint comprises the highest priority epics and user stories from the program backlog that the team can complete within the established timeframe. The product owner maintains the release backlog with input from

is performed. 2. Examples of ineffective quality controls include: a. Requiring another team to complete tedious, error-prone, and manual tasks that could be easily automated and run as needed by the generated or received. iii. Key metrics in value stream 1. Lead Time 2. Process time 3. Percent Complete & Accurate (%C/A) c. CREATE A DEDICATED TRANSFORMATION TEAM i. Organizations use processes, specialization

clear goals and process 2. Must have clear and immediate feedback 3. Confidence in ability to complete the task  The power of Agile frameworks (Scrum, Kanban) is that they create/sustain these conditions

that a program meets its specification, the hardest part of the software task is arriving at a complete and consistent specificationEnvironments and tools • How much more gain can be expected from the

Jez Humble, “The most inefficient way to test a business model or product idea is to build the complete product to see whether the predicted demand actually exists.” ii. How to build a feature: 1.