Product Backlog in Agile Scrum

Description:
Product backlog is a list of features created by Product owner for the Development team to implement. Priorities are set in the Product backlog and it helps development team to implement them considering their importance. It takes place of requirement specification artifacts in the Agile methodology when we compare it to traditional methodology. Scope of the Project that may change or evolve. List of Epics and Stories owned by Product Owner. Continue reading “Product Backlog in Agile Scrum”

Definition of Done in Agile Scrum

Description:

Code does what I need to do. Definition of Done is a exremely important in the Agile Scrum. It is kind of a Checklist or Bulleted points on what is acceptable in terms of final outcome or in which condition we can conclude that implementation of a specific feature is “Done.”

Continue reading “Definition of Done in Agile Scrum”

Stories and Epics in Agile Scrum

Description:
In Simple English, we can consider User Story as description of a specific feature of an application which is being developed in Agile Scrum. It describes in details regarding who wants that feature, what they need and whey they need it. It is more of a simplified version of a requirement. Continue reading “Stories and Epics in Agile Scrum”

Documentation in Agile Scrum

Description:
Non Documentation but still there is some need of documentation which is required to keep track.
My Experiences:
In my experience, we did created a Reference Architecture document; There was no process document as such Design Specification and Test Specification and other stuff but we created “How to Guides” for different functions or automation stuff. Continue reading “Documentation in Agile Scrum”

Scrum Sprint Retrospective Meeting

Description:

Retrospectives are the meetings of all stakeholders to know about what worked and what didn’t. It is a part of every sprint and it helps to improve the Agile process. It is more about experience and how to use it to improve in coming sprints and decrease the errors.

My Experiences:

I must admit it was a real pain initially. There were too many teams involved from different technologies and everyone was passionate about the problems they faced and how their work was impacted because of it.

Continue reading “Scrum Sprint Retrospective Meeting”

Sprint Planning in Agile Scrum

Description:
Sprint Planning involves story selection based on highest priorities for a specific sprint. Capacity of team also taken into considerations. It involves Product Owner, Scrum Master, and Scrum team Members.
My Experiences:
As a Offshore team we used to be involved in the discussion and Sprint planning. Continue reading “Sprint Planning in Agile Scrum”

Agile Scrum Team Members

Description:

Teams of equals; Self-Organizing; No Egos; No PM No Leader; Willing to Analyze, design, code, test, and document.
My Experiences:

In a Team, we had members from different domains such as Infrastructure, Database, Development and Testing; There was a hybrid management where PM was introduced but it didn’t work out well as it doesn’t fit in Agile framework.

Continue reading “Agile Scrum Team Members”

What is Scrum Master

Description:
Agile Master or Master – Guide and support but NOT a Project Manager.
My Experiences:

For Onsite and Offshore team we had two different SCRUM Master. They played a good role but still believe It was important for the team to have good understanding of all concepts of Agile up front as few sessions created confusion and SCRUM master was not able to convince us. It was also about culture change. Another important thing was availability of SCRUM master. If he is with the team then it is easier for team to get the process. Geographical distance created communication issues.

Continue reading “What is Scrum Master”