chapter 5 (agile modeling, prototyping, and scrum) Flashcards
1
Q
Prototyping
A
Prototyping is an information-gathering technique useful
in seeking
– User reactions
– Suggestions
– Innovations
– Revision plans
2
Q
Prototyping
A
- Patched-up
- Nonoperational
- First-of-a-series
- Selected features
3
Q
Patched-Up Prototype
A
- A system that works but is patched up or patched
together - A working model that has all the features but is inefficient
- Users can interact with the system
- Retrieval and storage of information may be inefficient
4
Q
Nonoperational Scale Model prototype
A
- A nonworking scale mode that is set up to test certain
aspects of the design - A nonworking scale model of an information system
might be produced when the coding required by the
application is too expensive to prototype but when a
useful idea of the system can be gained through
prototyping of the input and output only
5
Q
First-Of-A-Series Prototype
A
- Creating a pilot
- Prototype is completely operational
- Useful when many installations of the same information
system are planned - A full-scale prototype is installed in one or two locations
first, and if successful, duplicates are installed at all
locations based on customer usage patterns and other
key factors
6
Q
Selected Features Prototype
A
- Building an operational model that includes some, but not
all, of the features that the final system will have - Some, but not all, essential features are included
- Built in modules
- Part of the actual system
7
Q
Users’ Role in Prototyping
A
- Honest involvement
- Communicate the purpose of the prototype clearly
- Get suggestions for changing, expanding the prototype
and innovation
8
Q
Agile Modeling
A
Agile methods are a collection of innovative, user-centered approaches to systems development
9
Q
Values and Principles of Agile Modeling
A
- Communication
- Simplicity
- Feedback
- Courage
10
Q
The Basic Principles of Agile Modeling
A
- Satisfy the customer through delivery of working software
- Embrace change, even if introduced late in development
- Continue to deliver functioning software incrementally
and frequently - Encourage customers and analysts to work together daily
- Trust motivated individuals to get the job done
- Promote face-to-face conversation
- Concentrate on getting software to work
- Encourage continuous, regular, and sustainable
development - Adopt agility with attention to mindful design
- Support self-organizing teams
- Provide rapid feedback
- Encourage quality
- Review and adjust behavior occasionally
- Adopt simplicity
11
Q
Four Basic Activities of Agile Modeling
A
- Coding
- Testing
- Listening
- Designing
12
Q
Coding
A
- Coding is the one activity that it is not possible to do
without - The most valuable thing that we receive from code is
“learning” - Code can also be used to communicate ideas that would
otherwise remain fuzzy or unshaped
13
Q
testing
A
- Automated testing is critical
- Write tests to check coding, functionality, performance,
and conformance - Use automated tests
- Large libraries of tests exist for most programming
languages - These are updated as necessary during the project
- Testing in the short term gives extreme confidence in
what you are building - Testing in the long term keeps a system alive and allows
for changes longer than would be possible if no tests
were written or run
14
Q
listening
A
- Listening is done in the extreme
- Developers use active listening to hear their
programming partner - Because there is less reliance on formal, written
communication, listening becomes a paramount skill - A developer also uses active listening with the customer
- Developers assume that they know nothing about the
business so they must listen carefully to businesspeople
15
Q
designing
A
- Designing is a way of creating a structure to organize all
the logic in the system - Designing is evolutionary, and so systems are
conceptualized as evolving, always being designed - Good design is often simple
- Design should allow flexibility
- Effective design locates logic near the data on which it
will be operating - Design should be useful to all those who will need it as
the development effort proceeds
16
Q
Four Resource Control Variables of Agile Modeling
A
- Time
- Cost
- Quality
- Scope
17
Q
Four Core Agile Practices
A
- Short releases
- 40-hour work week
- Onsite customer
- Pair programming
18
Q
The Agile Development Process
A
- Listen for user stories
- Draw a logical workflow model
- Create new user stories based on the logical model
- Develop some display prototypes
- Create a physical data model using feedback from the
prototypes and logical workflow diagrams
19
Q
Writing User Stories
A
- Spoken interaction between developers and users
- Seeking first and foremost to identify valuable business
user requirements - The goal is prevention of misunderstandings or
misinterpretations of user requirements
20
Q
scrum
A
- Begin the project with a high-level plan that can be
changed on the fly - Success of the project is most important
- Individual success is secondary
- Project leader has some (not much) influence on the
detail - Systems team works within a strict time frame (two to
four weeks for development) - Product backlog
- Sprint backlog
- Sprint
- Daily scrum
- Demo
21
Q
There are three roles in Scrum:
A
– Product owner
– Scrum Master
– Team member
22
Q
Team members:
A
– Work to create and improve user stories
– Generate estimates
– Self-organize to complete the work
– Exhibit willingness to participate in any activity to help
the project
23
Q
Product Backlog
A
- Features and other deliverables designers intend for the
product based on user stories - The list of user stories is reorganized so that the most
important user stories appear on the top
24
Q
Sprint Cycle
A
- Stories are deliverables the team accomplishes
- Tasks are parts of the story or units of work that each
team members does - The sprint cycle can vary in length, but the usual is two
weeks - At the end of the cycle, determine whether the product
should be released
25
Two-Week Release Advantages
* Team spirit remains high
* Completing the product is more real to the team
* Continual feedback from customers
26
Lessons Learned from Agile Modeling
* Short releases allow the system to evolve
* Pair programming enhances the overall quality
* Onsite customers are mutually beneficial to the business
and the agile development team
* The 40-hour work week improves worker effectiveness
* Balanced resources and activities support project goals
* Agile values are crucial to success
27
Other Unique Scrum Features
* Scrum planning meeting
* Planning poker
* Daily meetings
* Sprint burndown chart
* Sprint review
28
Two parts to a Scrum planning meeting:
– Product owner presents the list of features on the
wish list of user stories
– Estimate the resources needed to complete all of the
features
▪ Common way to do this is to play planning poker
29
Planning Poker
* Planning poker is a way to help the team determine
estimates for completing the features from user stories
* There are rules for the game
30
Planning Poker Rules
* A moderator keeps the estimation meeting running
efficiently
* The product owner presents one of the user stories that
needs estimating
* Each team member chooses a card with a number on it
and lays it face down
* A lower numbered card means that a project can be
completed faster
* The numbers may represent the number of days it takes
to finish a feature, story points, or even difficulty in
abstract terms
* Team members turn over their cards at the same time
* The team members with the highest and lowest estimates
may defend their ratings
* The entire team can discuss the estimates
* A new hand is then played and so on
31
Daily Scrum Meetings
* Called a stand-up meeting because it lasts only a few
minutes
* Team members tell each other what tasks they’ve been
working on since the previous daily Scrum
* Tasks they expect to complete during the current daily
Scrum
* Obstacles might get in their way
32
Sprint Burndown Chart
* Way to keep track of performance
– Horizontal axis tracks the time that has elapsed
– Vertical axis may track the number of tasks remaining
or the number of hours to complete the remaining
tasks
– Red line shows hours of work remaining, and the
yellow bars show the number of tasks remaining
33
Sprint Review
* Team gets together in a meeting to review the work done
* Note any tasks that were not completed
* User stories completed are prominently documented
* User stories the team committed to that were not finished
are noted
34
Kanban
Key elements of the Kanban system as applied to
software development are:
– Visualize the workflow
– Keep work-in-process (WIP) as small as possible
– Reevaluate the workflow, reassigning priorities if need
be
– Strive for continual improvement
35
Scrum Advantages
– Quick product development
– Exercises a user-oriented approach
– Encourages teamwork
– Less confusing than more formal approaches
– Flexibility
– Satisfying to team members
– Rewards smaller but meaningful accomplishments
– Provides feedback
– Adaptability
36
Scrum Disadvantages
– Documenting features improperly
– Releasing products with errors
– Releasing products too soon for the user
– Completing the sprint backlog under pressure
– Working as a geographically dispersed team may be
difficult
– Working as a team when special skills are required may be
challenging
– Replacing team members who leave the team is difficult
37
Devops – Development Operations
* Decrease the deployment time for newly developed
applications and maximize profit by rapidly addressing
market opportunities and getting customer feedback in a
timely manner
* Development and operations are working in parallel
streams within a DevOps culture
38
Comparing Agile Modeling and Structured Methods
* Improving the efficiency of systems development
* Risks inherent in organizational innovation
39
risks in adopting organizational innovation
-organizational culture
-individual rights
-timing
-measuring impact
-cost
-clients' reactions
40
Risks When Adopting New Information
Systems
* Fit of development team culture
* Best time to innovate
* Training cost for analysts and programmers
* Client’s reaction to new methodology
* Impact of agile methodologies
* Programmers/analysts individual rights
