- Kano Model
- Relative Weighing
- Project financials;
- Status reporting;
- Project governance;
- Identification of missing roles and/or resources;
- Business stakeholder communication;
- Risk communication and management;
- Project planning;
- Change management.
POINTS to KEEP in MIND DURING AGILE ESTIMATION – Planning Poker
All developers in the team should participate in planning poker.
Each person involved in estimation should be given a deck of cards at beginning of planning poker estimation meeting. Each card should have valid estimates. Cards can have serial number ( 1,2,3,4,5,..etc ) or Fibonacci numbers ( 1,2,3,5,8,13..etc) or Tshirt sizing ( S,M,L,XL,XLL )
Prepared card can be reused in other planning poker estimation meeting.
Product owner or business analyst or user story creator reads out user story.
Product owner or business analyst or user story creator answers any questions that developers asks.
There might be disagreement among estimators on user story points.So, people having such disagreements explain their points. Then estimators are asked to estimate again.
1. Better Productivity
2. Low Cost
3. Bring product or changes to product to market faster
4. High degree of customer satisfaction
6. Better visibilty to development process
Agile Manifesto uncovers better way of developing software by doing it and helping others to do it. Through this work we value below :
Individuals and interactions over processes and tools
Working software over comprehensive documentation
Customer collaboration over contract negotiation
Responding to change over following a plan
Who are part of Scrum Team ?
Scrum Team consists of :
Other Scrum Interview Questions :
What is role and responsibility of Dev Team in Scrum ?
Dev Team us responsible for doing the work
What is role and responsibility of Product Owner ?
Product Owner is responsible for maximizing value of work done by Dev Team
Product Owner owns vision and goals / Return of Investment of work done
Product Owner is final decision maker of list of items in Product Backlog
Product Owner owns date and scope of release