Scrum : Agile Project Management - Overview

SCRUM is an agile, lightweight process for managing and controlling software and product development in rapidly changing environments.

• Iterative, incremental process
• Team-based approach
• developing systems/ products with rapidly changing requirements
• Controls the chaos of conflicting interest and needs
• Improve communication and maximize cooperation
• Protecting the team form disruptions and impediments
• A way to maximize productivity

Below is Scrum agile process to achieve the goals of determined in build release of a product:

>>> Appoint Product Owner, Scrum Master, Scrum Teams

•         Product Owner --- Who has better understanding of business perspective of product. Acts like one voice (in any case). Knows what needs to be build and in what sequence this should be done
•         Scrum Master --- Someone who can follow ups sprint deadlines, product backlog deadlines. Responsible for enacting scrum values and practices. Main job is to remove impediments
•       Scrum Teams: Android Team , iOS Team , CMS Team ,QA Team

>>> Create Product Backlog, which concludes which features, improvements and issues needs to be answered in this product release. Product Backlog release time 2-3 months. Attendee: Product Owner, Scrum Master, Scrum Team Leads

>>> Now take subset from product backlog and create Sprint Backlog. It consists of a subset of features, improvements and issues from product backlog. Ideally of Now establish sprint to achieve these sprint backlog goals. Sprint should of 1 week long only,

Attendee: Product Owner, Scrum Master, Scrum Team Leads

>>> Scrum Master will run Daily Scrums, in these scrum discuss what will delivered by end of day and what are the roadblock in achieving the daily scrums.

Attendee: Scrum Master, Product Owner, Scrum Teams

>>> Scrum Master will organize the mid weekly meeting to get the progress of sprint release estimate and discuss roadblock if any.

Attendee: Scrum Master, Product Owner, and Scrum Teams.

>>> At the End of sprint meet to discuss goals achieved and what will be scheduled for next sprint.

This basically iterative process and doing sprints in iterations we will achieve the product backlog completely.

Other suggestions:

1. Use 3 different branches of source code:

• Dev Branch: dev teams use this branch only.
• QA Branch: This branch is tested by QA Team and verified the stability of build release.
• Release Branch: This version of branch is live for the user. Does not do changes in this branch as it is live and used to release app without testing requirement as such.

2. Inform the concerned person /teams on emails about the work you have done if they are dependent on you. Proper communication channel should be established to improve work related communication between individuals and teams.