DCSIMG
Scrum and eScrum - SRL Group

SRL Group

This blog is about Team System, QA and Development methodologies and more...

VSTS Resources

Team System Bloggers

Scrum and eScrum

hello,this is the first, and 1of 4 blogs about eScrum.

Scrum is an agile software development method for project management, it’s a set of interrelated practices and rules that optimize the development environment.
A Scrum project is a monthly process and useful product functionality is delivered as requirements, architecture, and design to the customer.

EScrum confirm all scrum rules and methodology .with eScrum you can create products, product backlog, manage sprints, sprint backlogs, view and investigate reports, update the process every day. All of this and more ensure that eScrum provide scrum platform.
 
A Product is a combination of a Product Backlog, a Product Owner, and a list of Team Members who will participate in the Sprints.
Each product divided to product backlog, which is a single prioritized feature with a baseline cost estimate.

A Product Owner is the single person in charge of keeping the Product Backlog complete and up to date. The Team Members added to a Product will show up in the Owner drop down for Product Backlog Items.
Each sprint is time limited, the default is 30 days. The Product Team selects a set of Product Backlog Items which they think they can deliver on in the given period of time and works on those features, producing a working product at the end of the Sprint. A Scrum Master is assigned to a sprint to facilitate the Scrum process and to remove any impediments to the team.
 A Sprint Backlog is a breakdown of the specific tasks necessary to implement all of the functionality of a set of Product Backlog Items. Because only those features accepted by the Sprint Team will be worked on, all Tasks generated for the Sprint must be directly associated with a Product Backlog Item.
To be able to properly track Sprint status and have a valid Sprint Burn down graph, Sprint Team Members should daily update the actual hours worked on tasks in the “Daily Scrum”.

 

3

Comments

No Comments

Leave a Comment

(required) 

(required) 

(optional)

(required) 


Enter the numbers above: