Term
|
Definition
| the idea that one phase of the SDLC can be completed in in its entirety and the project can progress, without backtracking, to the next phase of the SDLC. Projects seldom are that simple. |
|
|
Term
| system development life cycle (SDLC) is falling out of favor in development community because... |
|
Definition
| system requirements are always changing because it needs to be corrected, more is known, or they change their mind. |
|
|
Term
| principles of agile development |
|
Definition
expect changes in requirement
frequent deliver working version of the product
work closely with customers
design as you go
test as you go
team knows best/how to change
can be used for applications, information systems, and business process development |
|
|
Term
|
Definition
rapid application development
unified process
extreme programming
scrum.. |
|
|
Term
|
Definition
| development process that conforms to the principles and can be used for the management of many types of projects. |
|
|
Term
|
Definition
| fourth principle of Agile designing in portions only as needed to complete the current work it is constantly changing and revised. |
|
|
Term
|
Definition
| an agile development by Jeff Sutherland, Jeff McKenna, and John Scrumniotales for Easel Corp. as the gathering of a team as in a huddle to discuss progress. A 2-4 week period. |
|
|
Term
|
Definition
| 15 minute meeting in which each team member states what was done in the last day, what will be done in the coming day, and any factors blocking progress. |
|
|
Term
|
Definition
| team members work in pairs sharing the same computer program |
|
|
Term
|
Definition
| the customer is satisfied with the product created and accepts the work product or the project runs out of time or the project runs out of money |
|
|
Term
|
Definition
| business professional who provides the requirements and is available for clarification and testing |
|
|
Term
|
Definition
| an expert in scrum processes who helps to keep the process organized and operating |
|
|
Term
|
Definition
| programmers, system analyst, business analyst, data base designer, cloud engineers PQA testing personnel and any other staff needed; usually 5-9 members. |
|
|
Term
|
Definition
| daily approximately 10 minutes long self formatting teams stating what you will be responsible for (accountability) and discuss problems (if any) |
|
|
Term
|
Definition
| who and what they do aswell as the clause of the requirement is to set a context for the value that will be delivered by the requirement |
|
|
Term
|
Definition
| team assigns 1 point to the simplest task more based of difficulty, using past experience, team computes its velocity |
|
|
Term
|
Definition
| in scrum the total number of points of work that a team can accomplish in each scrum period |
|
|
Term
|
Definition
| 1-4 weeks moves back and forth from the requirements, designs, implementation, and testing |
|
|
Term
|
Definition
|
|
