Agile Scrum Academic Report Summary
|
Topic Summary (from en.wikipedia.org): In software development and product management , a user story is a description consisting of one or more sentences in the everyday or business language of the end user or user of a system that captures what a user does or needs to do as part of his or her job function. User stories are used with agile software development methodologies as the basis for defining the functions a business system must provide, and to facilitate requirements management . It captures the ‘who’, ‘what’ and ‘why’ of a requirement in a simple, concise way, often limited in detail by what can be hand-written on a small paper notecard.
Major Themes:
- In software development and product management , a user story is a description consisting of one or more sentences in the everyday or business language of the end user or user of a system that captures what a user does or needs to do as part of his or her job function (from en.wikipedia.org)
- It is most commonly used in agile software development , in particular in scrum and Extreme Programming . (from en.wikipedia.org)
- User stories are used with agile software development methodologies as the basis for defining the functions a business system must provide, and to facilitate requirements management (from en.wikipedia.org)
- The stand-up has particular value in Agile Software development processes, (from en.wikipedia.org)
- The product owner should be on the business side of the project, and should never interfere or interact with team members on the technical aspects of the development task. (from en.wikipedia.org)
- Some software development methodologies envision daily team – meetings to make commitments to team members (from en.wikipedia.org)
- The Product owner represents the stakeholders and is the voice of the customer , who is accountable for ensuring that the team delivers value to the business (from en.wikipedia.org)
- Scrum teams should have one product owner, this role should not be combined with that of the Scrum master (from en.wikipedia.org)
- Zweck des Daily scrum ist der Informationsaustausch (from de.wikipedia.org)
- The Product owner writes (or has the team write) customer-centric items (typically user stories ), ranks and prioritizes them, and adds them to the Product backlog (from en.wikipedia.org)
- Dazu hat sich bewährt, dass jedes Teammitglied mit Hilfe des Taskboards sagt, was es seit dem letzten Daily scrum erreicht hat, was es bis zum nächsten Daily scrum erreichen möchte, und was dabei im Weg steht. (from de.wikipedia.org)
- It was developed to provide a more cohesive approach to Agile Software development; one that fills in the process gaps that are (purposely) ignored by Scrum, and one that is capable of enterprise-level scale (from en.wikipedia.org)
- The User stories are then added to the board and the team completes them, the team working on as few User stories at a time as practical (the work-in-progress, or WIP, limit) (from en.wikipedia.org)
- Scott Ambler developed the disciplined agile development process during his time as chief methodologist for IT at IBM Rational (Summer 2006 to Summer 2012) (from en.wikipedia.org)
- Holistic Thought in Social Science (from en.wikipedia.org)
- Stanford University Press (from en.wikipedia.org)
- Planning poker is a variation of the Wideband Delphi method (from en.wikipedia.org)
- Situation-appropriateness can be considered as a distinguishing characteristic between Agile methods and traditional software development methods , with the latter being relatively much more rigid and prescriptive (from en.wikipedia.org)
- According to Ambler, ‘Many Agile Methodologies — including Scrum, XP, AM, Agile Data, Kanban, and more — focus on a subset of the activities required to deliver a solution from project initiation to delivery (from en.wikipedia.org)
- To keep iterations short, WIP limits are thus used, and a planning trigger is set in place for the team to know when to plan next – when WIP falls below a predetermined level (from en.wikipedia.org)
|
software development
|
80% |
|
agile scrum
|
80% |
|
agile software development
|
70% |
|
Software development process
|
40% |
|
Project management
|
40% |
|
product development
|
30% |
|
development team
|
30% |
|
sprint planning
|
30% |
|
Software Quality
|
20% |
|
Product owner
|
20% |
|
Scrum master
|
20% |
|
Daily scrum
|
20% |
|
Product backlog
|
20% |
|
Sprint backlog
|
20% |
|
scrum team
|
20% |
|
Agile Project Management
|
20% |
|
Agile Software
|
20% |
|
User story
|
20% |
|
User stories
|
20% |
|
Extreme Programming
|
20% |
|
Software engineering
|
20% |
|
agile development
|
20% |
|
team members
|
20% |
|
product management
|
10% |
|
Social Science
|
10% |
|
University Press
|
10% |
|
Planning poker
|
10% |
|
Scott Ambler
|
10% |
|
Agile methods
|
10% |
|
software development methods
|
10% |
|
development methods
|
10% |
|
Agile Methodologies
|
10% |
|
Product Owner häufig
|
10% |
|
Scrum Teams
|
10% |
|
next iteration
|
10% |
|
WIP limits
|
10% |
|
planning trigger
|
10% |
|
agile development
Agile Methodologies
Agile methods
Agile Project Management
agile scrum
Agile Software
agile software development
Daily scrum
development methods
development team
Extreme Programming
next iteration
Planning poker
planning trigger
Product backlog
product development
product management
Product owner
Product Owner häufig
Project management
Scott Ambler
Scrum master
scrum team
Scrum Teams
Social Science
software development
software development methods
Software development process
Software engineering
Software Quality
Sprint backlog
sprint planning
team members
University Press
User stories
User story
WIP limits
|