Postby alpaupa » Fri Mar 16, 2012 1:56 am

5. What do you do at the end of each sprint?
6. What is planning poker?
7. How do you help the product owner?
8. Do you work with a product backlog?
9. What is a product backlog?
Posts: 1
Joined: Tue Mar 06, 2012 3:09 am

Re: Agile

Postby jinideveloper » Wed Mar 21, 2012 1:51 am

>>What do you do at the end of each sprint?

At the end of a sprint cycle, two meetings are held: the “Sprint Review Meeting” and the “Sprint Retrospective”
Sprint Review Meeting is held and in sprint review meeting stakeholders and team members review the work that was completed and not completed. A demo of the completed work is presented to the stakeholders usually by testers. Incomplete work is not demonstrated. It has four hour time limit.

Then Sprint retrospective meeting is held where all team members reflect on the past sprint. Two main questions are asked in the sprint retrospective: What went well during the sprint? What could be improved in the next sprint?
It has a three-hour time limit

9. What is a product backlog?

The product backlog is an ordered list of "requirements" that is maintained for a product. It contains Product Backlog Items that are ordered by the Product Owner based on considerations like risk, business value, dependencies, date needed, etc. The features added to the backlog are commonly written in story format (See terminology below). The product backlog is the “What” that will be built, sorted in the relative order it should be built in. It is open and editable by anyone, but the Product Owner is ultimately responsible for ordering the stories on the backlog for the Development Team. The product backlog contains rough estimates of both business value and development effort, these values are often stated in story points using a rounded Fibonacci sequence. Those estimates help the Product Owner to gauge the timeline and may influence ordering of backlog items. For example, if the “add spellcheck” and “add table support” features have the same business value, the one with the smallest development effort will probably have higher priority, because the ROI (Return on Investment) is higher.
The Product Backlog, and business value of each listed item is the responsibility of the Product Owner. The estimated effort to complete each backlog item is, however, determined by the Development Team.
Posts: 5
Joined: Wed Mar 07, 2012 2:41 am

Re: Agile

Postby siri4321 » Mon Aug 18, 2014 11:20 pm

Planing Poker
. To start a poker planning session, the product owner or customer reads a agile user story or describes a feature to the estimators. 
The estimators discuss the feature, asking questions of the product owner as needed. When the feature has been fully discussed, each estimator privately selects one card to represent his or her estimate. All cards are then revealed at the same time.If all estimators selected the same value, that becomes the estimate. If not, the estimators discuss their estimates. The high and low estimators should especially share their reasons. After further discussion, each estimator reselects an estimate card, and all cards are again revealed at the same time.The poker planning process is repeated until consensus is achieved or until the estimators decide that agile estimating and planning of a particular item needs to be deferred until additional information can be acquired.
Posts: 1
Joined: Wed Nov 06, 2013 12:57 am

Return to AGILE Methodology

Who is online

Users browsing this forum: No registered users and 1 guest