![ Exploration Commitment
Sorts the stories
according to
necessity
Sorts the stories
according to risk
[Task is chosen by
the business and
carried out by
development.]
Steering
Reviews Progress
[Both the team
adjust a new plan ]
Business
Development
Writes a Story card
according to
necessity of the
system
Provides an estimate
from their own
perspective](https://image.slidesharecdn.com/agilemethodology-190805032241/85/Agile-methodology-7-320.jpg)
Agile methodology
- 1. Agile methodology for requirement determination in system analysis BY: NIRUSHA MANANDHAR CE(3RD YEAR/2ND SEM) ROLL. NO :31
- 2. Background Objectives of system analysis phase is requirement determination and requirement structuring Traditional methods like interviewing, direct observation for requirement determination Enhanced methods include JAD, Prototyping One of the prevalent method is Agile methodology.
- 3. Requirement Determination Using Agile Methodologies Continual User Involvement Agile Usage-Centered Design eXtreme Programming-planning game
- 4. Continual User Involvement Removes user involvement stereotype of Waterfall model Involve user in entire analysis and design phase Analysis-design-code-test cycle Feedback from user Iterative process User must be in a position to give up his/her normal responsibilities to involve entirely on system’s development. Useful only for small development projects
- 5. Agile Usage-Centered Design Adapted by Jeff Patton for agile methodologies in 9 steps: 1. Gather group of IS developing team including analysts, users, programmers, testers etc. 2. Record the suggestions and complaints from each of them called venting session. 3. Determine what tasks requires user roles and develop a role model of users on a 3*5 cards. 4. Sort the cards in terms of priority and similarity 5. Group the task card based on the similarity and grab a stack of card. This is called interaction context. 6. For each interaction context, write the task description directly on the card. 7. Treat each task as a tentative set of tasks to be supported by a single aspect of user interface and develop a paper prototype for that interface. Hence prototyped screens of captured requirements are created. 8. Bring out the users and let users evaluate the prototype. 9. Refine requirements accordingly.
- 6. eXtreme Programming: The Planning Game Two-person programming teams coding parallelly A Customer on-site during development Planning, analysis, design and construction are fused into single phase Way of determining requirements and specifications is Planning Game The planning game includes 2 players: Business and Development Planning game has 3 phases: Exploration, Commitment and Steering.
- 7. Exploration Commitment Sorts the stories according to necessity Sorts the stories according to risk [Task is chosen by the business and carried out by development.] Steering Reviews Progress [Both the team adjust a new plan ] Business Development Writes a Story card according to necessity of the system Provides an estimate from their own perspective
- 8. System Requirement Specification Outcome of requirement determination phase Document that describes features and behavior of system Includes functional requirements, technical requirements, constraints, assumptions and acceptance criteria, business drivers, business model Non-functional requirements like security, training techniques are also included Cost, delivery schedules, product assurance plans like configuration management, verification and validation procedures are not included
- 9. Thank You!!