1.7 Identify the basic aspects of the Agile methodology

Manifesto for Agile Software Development

- Individuals and interactions over processes and tools - Working software over comprehensive documentation - Customer collaboration over contract negotiation - Responding to change over following a plan

Scrum Artifacts

- Product Backlog - Sprint Backlog - Product Increment - Burndown Chart

Scrum Roles

- Product owner - Development Team - Scrum Master

Components of Agile Methodoloy

- Readily adapt to change - Just-in-time planning - Continuous requirements gathering - Sprints

Scrum Events

- Sprint Planning - Sprint - Daily Scrum - Sprint Review - Sprint Retrospective

Product Owner (Scrum)

- Vision for project - Authority to deiced what features are built and the order they should be done - Product backlog

What occurs in a sprint?

1. Spring Planning Meeting 2. Sprint Execution/Daily Scrum 3. Product Increment/Sprint Review 4. Retrospective Process starts all over again

Burndown Chart

A chart that shows the cumulative work remaining in a sprint on a day-by-day basis - Track progress during a Sprint

Cross-functional team

A team composed of employees from different functional areas of the organization Ex) UI Designer, Architect, Testers, Programmers

Agile Methodology

A way to manage projects by breaking them down into smaller chunks (iterations), while frequently inspecting and adapting - Readily adapt to change - Just-in-time planning - Continuous requirements gathering - Sprints Common in Software Development

User stories

Describes the features in terms of the benefits it's going to bring to the people actually using the products - Will change overtime Ex) "As a learner, I want to see a leader-board that displays all the members of my team, so that I can be motivated to train more and the most out of my CBTNuggets experiences"

Sprint Review

Discus the product and the features just completed in the sprint - Entire Scrum Team present along with Stakeholders

Sprint Execution

Do the work determined int he sprint - Perform Daily Scrum

Scrum Matster

Help everybody understand and follow the practices of the scrum framework - No managerial authority - Helps w/leadership of org. when it comes to promoting scrum values - Remove obstacles - The Facilitator

Sprint Retrospective

Lesson learned meeting - Look at sprint process (went well and what didn't) - What we can learn for the next sprint

Product backlog

List of functionality that we want the product to have (needed to be built) - Features written as user stories

Sprints

Produce a working version of a product after every sprint - Usually a couple of weeks - Everyone working simultaneously rather than separately - Continuous feedback - Change direction quickly

Sprint Planning Meeting

Step 1 Product owner brings product backlog into meeting w/development team - Agree on what to achieve in the sprint goal - Development breaks down each product backlog into specific tasks to product the Sprint Backlog - Scrum Master there to facilitate

Product Increment

Summation of overall backlog items finished during the Sprint and also the previous completed Sprints.

What is Agile? (Software)

The principle of software development based on iterative and incremental development

Scrum Development Team

Those who perform the work on the project - Cross-functional w/all the skills necessary to complete the work - Self-organizing & self-directing - 3-9 people

Self-organizing team

Up to the team who they do the job - Nobody assigns specific task stop individuals in this team - Sort it out themselves

Agile Methods are great in

fast changing and unpredictable environments - Just-in-time planning

Agile methods use

sprints instead of big sequential phases

Daily Scrum

stand-up meeting where team members update each other on w/progress, roadblocks, plan for the day