Science Computer Science Software Engineering
Agile Product Management Course
Save
Students also studied
Flashcard sets Study guides
APM Exam SAFe Agile Product Management (A... Section 4: Quiz 40 -
56 terms 84 terms Teacher 28 terms
ashleybrim Preview John_Fletcher784 Preview educator004
Practice questions for this set
Learn 1 /7 Study with Learn
high level requirement used by developers to produce a high
level estimate
User Story - used to document a products functional requirement
1/2 day and 2 days to develop.. anything longer is a feature or an
epic and needs to be split into mult stories
starts with the end user then what they want to do and the value
Brief description (of user story)
to the customer (the user role)
Parts of a user story card Title, brief description, story points, can add note at the bottom
before writing your story ask:
who is the user and their role?
what they are trying to achieve?
User Story Structure why they want to achieve it?
"As a <user type> I want to <do something> so that I can <derive a
benefit>"
INVEST independent, negotiable, valuable, estimable, small, testable
Acceptance Criteria satisfaction criteria, <7
, - WHOLE team responsibility
- not complete and cant be assigned to sprint without the
criteria
Acceptance Testing
- can be added at anytime by any team member
- PO sits down with engineering and QA to define the
acceptance criteria
Given, When, Then
ex: given the customer is logged in, when they click on the
Acceptance Test Structure
account management link, then they are taken to the edit
account management page.
(remain true across iterations)
Non functional requirements
browser support, tech decisions, interface standards, number of
and constraint cards
users, response time
product visions and roadmaps
project charters
business case
market needs MRD
List of Documentation's Product description PRD
problem scenarios
use cases
functional and technical specs
user interface guidelines
the time period prior to the beginning of the project when all
prep work is done. Can take longer than one sprints worth of
Iteration 0
time. Often set said for initial UX research, grow customer bench
for user validation to support continual testing
work flows, task analysis, prototyping, usability, personas are also
Examples of Iteration 0
important tools and artifacts for success in agile
T/F Agile "Value working True
software over comprehensive
documentation"
Background of LEAN from manufacturing and the Toyota production system
when can be applied to entire organization where projects cant
When does LEAN work better
be predictably time boxed
Manufacturing - eliminating waste
Purpose of LEAN for
Software - optimizing flow
Manufacturing and Software
BOTH - reducing unfinished work or code
Focus on the Customer Value
Systems thinking to optimize the whole
Empowered teams
LEAN Principles
Respect for people
Reliable delivery
Continuous improvement
fast, flexible flow
- minimize queues
- small batched
Goals of LEAN
- WIP constraints
- Short cycle times
- Single piece flow
Agile Product Management Course
Save
Students also studied
Flashcard sets Study guides
APM Exam SAFe Agile Product Management (A... Section 4: Quiz 40 -
56 terms 84 terms Teacher 28 terms
ashleybrim Preview John_Fletcher784 Preview educator004
Practice questions for this set
Learn 1 /7 Study with Learn
high level requirement used by developers to produce a high
level estimate
User Story - used to document a products functional requirement
1/2 day and 2 days to develop.. anything longer is a feature or an
epic and needs to be split into mult stories
starts with the end user then what they want to do and the value
Brief description (of user story)
to the customer (the user role)
Parts of a user story card Title, brief description, story points, can add note at the bottom
before writing your story ask:
who is the user and their role?
what they are trying to achieve?
User Story Structure why they want to achieve it?
"As a <user type> I want to <do something> so that I can <derive a
benefit>"
INVEST independent, negotiable, valuable, estimable, small, testable
Acceptance Criteria satisfaction criteria, <7
, - WHOLE team responsibility
- not complete and cant be assigned to sprint without the
criteria
Acceptance Testing
- can be added at anytime by any team member
- PO sits down with engineering and QA to define the
acceptance criteria
Given, When, Then
ex: given the customer is logged in, when they click on the
Acceptance Test Structure
account management link, then they are taken to the edit
account management page.
(remain true across iterations)
Non functional requirements
browser support, tech decisions, interface standards, number of
and constraint cards
users, response time
product visions and roadmaps
project charters
business case
market needs MRD
List of Documentation's Product description PRD
problem scenarios
use cases
functional and technical specs
user interface guidelines
the time period prior to the beginning of the project when all
prep work is done. Can take longer than one sprints worth of
Iteration 0
time. Often set said for initial UX research, grow customer bench
for user validation to support continual testing
work flows, task analysis, prototyping, usability, personas are also
Examples of Iteration 0
important tools and artifacts for success in agile
T/F Agile "Value working True
software over comprehensive
documentation"
Background of LEAN from manufacturing and the Toyota production system
when can be applied to entire organization where projects cant
When does LEAN work better
be predictably time boxed
Manufacturing - eliminating waste
Purpose of LEAN for
Software - optimizing flow
Manufacturing and Software
BOTH - reducing unfinished work or code
Focus on the Customer Value
Systems thinking to optimize the whole
Empowered teams
LEAN Principles
Respect for people
Reliable delivery
Continuous improvement
fast, flexible flow
- minimize queues
- small batched
Goals of LEAN
- WIP constraints
- Short cycle times
- Single piece flow
