Use LEFT and RIGHT arrow keys to navigate between flashcards;
Use UP and DOWN arrow keys to flip the card;
H to show hint;
A reads text to speech;
20 Cards in this Set
- Front
- Back
|
C3P59 common characteristics of agile methods |
1. the processes of specification, design, and implementation are interleaved 2. the system is developed as a series of increments; end-users and other system stakeholders are involved in specifying and evaluating each increment 3. extensive tool support is used to support the development process |
|
|
C3P62 the principles of agile methods |
1. customer involvement
2. embrace chance 3. incremental delivery 4. maintain simplicity 5. people, not process |
|
|
C3P62 agile methods have been successful for two kinds of system development |
1. product development where a software company is developing a small or medium-sized product for sale
2. custom system development within an organization, where there is a clear commitment from the customer to become involved in the development process and where there are few external stakeholders and regulations that affect the software |
|
|
C3P63 XP (extreme programming) release cycle
|
1. select user stories for this release 2. break down stories to tasks 3. plan release 4. develop/integrate/test software 5. release software 6. evaluate system |
|
|
C3P64 XP practices |
1. collective ownership 2. continuous integration 3. incremental planning 4. on-site customer 5. pair programming 6. refactoring 7. simple design 8. small releases 9. sustainable pace 10. test first development |
|
|
C3P65 user stories definition |
a user story is a scenario of use that might be experienced by a system user |
|
|
C3P67 refactoring definition |
it means that the programming team look for possible improvements to the software and implements them immediately, even in situations where there is no immediate need for them |
|
|
C3P67 key features of testing in XP |
1. test-first development 2. incremental test development from scenarios 3. user involvement in the test development and validation 4. the use of automated testing frameworks |
|
|
C3P69 pair programming |
programmers work in pair to develop the software; pairs are created dynamically |
|
|
C3P69 pair programming advantages |
1. it supports the idea of collective ownership and responsibility for the system 2. it acts as an informal review process because each line of code is looked at by at least two people 3. it encourages refactoring to improve the software structure |
|
|
C3P71 scrum terminology - development team |
self-organizing group of of software developers of no more than 7 people; they are responsible for developing the software and other essential project documents
|
|
|
C3P71 scrum terminology - potentially shippable product increment |
the software increment that is delivered from a sprint
|
|
|
C3P71 scrum terminology - product backlog |
a list of "to do" items that the Scrum team must tackle
|
|
|
C3P71 scrum terminology - product owner |
an individual (or small group) whose job is to identify product features or requirements, prioritize these for development, and continuously review the product backlog to ensure that the project continues to meet critical business needs; can be a customer, a product manager in a software company, or other stakeholder representative
|
|
|
C3P71 scrum terminology - scrum |
daily meeting of the Scrum team that reviews progress and prioritizes work to be done that day
|
|
|
C3P71 scrum terminology - ScrumMaster |
is responsible for ensuring that the Scrum process is followed and guides the team in the effective use of Scrum
|
|
|
C3P71 scrum terminology - sprint |
a development iteration; usually 2 to 4 weeks long
|
|
|
C3P71 - velocity |
an estimate of how much product backlog effort a team can cover in a single sprint |
|
|
C3P75 practical problems with agile methods |
1. the informality of agile development is incompatible with the legal approach to contract definition that is commonly used in large companies 2. agile methods are most appropriate for new software development rather than for software maintenance; yet the majority of software costs in large companies comes from maintaining their existing software systems 3. agile methods are designed for small co-located teams, yet much software development now involves worldwide distributed systems |
|
|
C3P77 agile principles and organizational practice |
1. customer involvement 2. embrace change 3. incremental delivery 4. maintain simplicity 5. people, not process |
