Agile Development Academic Research Report Summary
|
Topic Summary (from en.wikipedia.org): Pair programming is an agile software development technique in which two programmers work together at one workstation. One, the driver , writes code while the other, the observer or navigator ,
Major Themes:
- Pair programming is an agile software development technique in which two programmers work together at one workstation (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)
- It is a collection of values and principles, that can be applied on an ( agile ) software development project (from en.wikipedia.org)
- According to Jean-Loup Richet (Research Fellow at ESSEC Institute for Strategic Innovation & Services) ‘this approach can be leveraged effectively for non-software products and for project management in general, especially in areas of innovation and uncertainty (from en.wikipedia.org)
- Both iterative and agile methods were developed as a reaction to various obstacles that developed in more sequential forms of project organization (from en.wikipedia.org)
- Many of extreme programming practices have been around for some time; the methodology takes ‘ best practices ‘ to extreme levels (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)
- 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)
- 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)
- The Poppendiecks’ involvement in the Agile Software development community, including talks at several Agile conferences (from en.wikipedia.org)
- The book presents the traditional lean principles in a modified form, as well as a set of 22 tools and compares the tools to Agile practices (from en.wikipedia.org)
- Agile modeling (AM) is a methodology for modeling and documenting software systems based on best practices (from en.wikipedia.org)
|
agile software development
|
90% |
|
software development
|
70% |
|
agile development
|
60% |
|
Agile Project Management
|
50% |
|
project management
|
50% |
|
Software development process
|
50% |
|
agile methods
|
30% |
|
Software Quality
|
30% |
|
extreme programming
|
30% |
|
sprint planning
|
30% |
|
development team
|
30% |
|
product development
|
30% |
|
Agile management
|
20% |
|
project life cycle
|
20% |
|
Product owner
|
20% |
|
Scrum master
|
20% |
|
Daily scrum
|
20% |
|
Product backlog
|
20% |
|
Sprint backlog
|
20% |
|
New Product Development
|
20% |
|
scrum team
|
20% |
|
scrum process
|
20% |
|
product backlog items
|
20% |
|
backlog items
|
20% |
|
business value
|
20% |
|
scrum backlog
|
20% |
|
Work items
|
20% |
|
scrum approach
|
20% |
|
product management
|
20% |
|
Agile Software
|
20% |
|
development process
|
20% |
|
Agile practices
|
10% |
|
software development methods
|
10% |
|
development methods
|
10% |
|
extreme programming practices
|
10% |
|
Agile modeling
|
10% |
|
best practices
|
10% |
|
Agile Model
|
10% |
|
Pair programming
|
10% |
|
Lean principles
|
10% |
|
agile development
Agile management
agile methods
Agile Model
Agile modeling
Agile practices
Agile Project Management
Agile Software
agile software development
backlog items
best practices
business value
Daily scrum
development methods
development process
development team
extreme programming
extreme programming practices
Lean principles
New Product Development
Pair programming
Product backlog
product backlog items
product development
product management
Product owner
project life cycle
project management
scrum approach
scrum backlog
Scrum master
scrum process
scrum team
software development
software development methods
Software development process
Software Quality
Sprint backlog
sprint planning
Work items
|