Agile Scrum Flow

By ahughes, 20 March, 2012
Agile Scrum Flow
Audio file


We switched from waterfall and now we using agile

My projects never stall even if the scope is fragile

Because we in a sprint, with plenty conversation

Change what you meant with no hesitation

We gone get your site up and running way faster

You the Product Owner, I'm the right ScrumMaster

What you wanna do may be harder than it seems

Some people in development forming up a team

We gone get together everyday on a call

Saying what we did and gonna do to move the ball

And every few weeks lets sit down and plan

What’s our next moves and try to understand

Did we learn a lesson? No need for stressin

When we work together then we moving towards progression

During all our sessions you should come with user stories

Authenticated users want to search for new employees

See i wanna keep it clear, no need for the fog

Prioritize your requirements in your backlog

We gone repeat the process in each iterration

Until the projects complete thanks to your consideration

Waterfall is a project management approach where a project is completed in distinct stages and moved step by step toward ultimate release. You make a big plan upfront and then execute in a linear fashion, hoping there won’t be any changes in the plan.

Agile software development refers to a group of software development methodologies based on iterative development, where requirements and solutions evolve through collaboration between self-organizing cross-functional teams.

Sprint is a short, time-boxed period when a scrum team works to complete a set amount of work.

Product Owner provides the “single source of truth” for the Team regarding requirements and their planned order of implementation.

ScrumMaster is responsible for making the process run smoothly, for removing obstacles that impact productivity, and for organizing and facilitating the critical meetings. 

Team is a self-organizing and cross-functional group of people who do the hands-on work of developing and testing the product.

Sprint planning is an event in scrum that kicks off the sprint. The purpose of sprint planning is to define what can be delivered in the sprint and how that work will be achieved. Sprint planning is done in collaboration with the whole scrum team.

Retrospective is anytime your team reflects on the past to improve the future.

Daily Scrum is a 15-minute time-boxed event for the Development Team to synchronize activities and create a plan for the next 24 hours. The Daily Scrum is held every day of the Sprint.

User Story describes a desired feature (functional requirement) in narrative form. User Stories are usually written by the Product Owner, and are the Product Owner’s responsibility

Product Backlog is a prioritized list of work for the development team that is derived from the roadmap and its requirements.