PSPO Questions And Answers Graded A+
Agile Methodology
Aims for customer satisfaction through early and continuous delivery of useful software components
developed by an iterative process using the bare minimum requirements
waterfall methodology
a sequential, activity-based process or sequence of phases in which the output of each phase
becomes the input for the next phase
Agile Manifesto Principles (Frist 6)
1. Our highest priority is to satisfy the customer through early and continuous delivery of valuable
software.
2. Welcome changing requirements , even late in development. Agile processes harness change for
the customer's competitive advantage.
3. Deliver working software frequently, from a couple of weeks to a couple of months, with a
preference for the shorter timescale
4. Business people and developers must work together daily throughout the project.
5. Build projects around motivated individuals. Give them the environment and support they need,
and trust them to get the job done.
6. The most efficient and effective method of conveying information to and within a development
team is face-to-face conversation.
Agile Manifesto (last 6)
7. Working software is the primary measure of progress.
8. Agile processes promote sustainable development. The sponsors , developers, and users should be
able to maintain a constant pace indefinitely.
9. Continuous attention to technical excellence and good design enhances agility.
10. Simplicity-the art of maximizing the amount of work not done-is essential.
11. The best architectures, requirements, and designs emerge from self-organizing teams.
12. At regular intervals , the team reflects on how to become more effective, then tunes and adjusts
its behavior accordingly.
Scrum
Uses small teams to produce small pieces of deliverable software using sprints, or 30-day intervals, to
achieve an appointed goal
Scrum (heavy focus)
on continuous improvement of the product, the team and the working environment.
Scrum Team
1. Product Owner
2. Development Team
3. Scrum Master
cross-functional, which is a fancy way of saying that the different members of the organization
User Story
is a tool used in Agile software development to capture a description of a software feature from an
end-user perspective
, Is User Story a fundamental part of Agile? T/F
False it is not a fundamental part it is just a tool .
If you see questions asking about user story in the test most likely those answers are wrong as its not
essential.
Spike
is a user story that the team cannot estimate the effort.
Label in Jira
SPIKE - "User Story Title"
Sprint Zero
don't do this that is bad practice, all Sprints should start with 1. If you see something in the test about
sprint zero that is most likely wrong.
Story Points
Though helpful are not a part of the scrum guide so if you see that you can most likey know it is wrong
Backlog Items need the following
Description
Order
Estimate
Value
Dependecies are not essential but if you do they do need to be made and made transparent
Risk Register
risk exposure = likelihood of it happening x impact if it does happen. Value to red, amber green (RAG)
Discovery
The correct product for the correct problem
1. Define the problem
2. Find Solutions
3. Choose solution to build
4. Plan how to build the solution
5. Create a prototype of MVP
6. Test solution
7. Evaluate
8. Refine and repeat
Product vision
High level strategy of the goals of your product (not focused to a specific release)
Good product vision will have the following:
1. What the product will do
2. Who is the product for
3. Why the product will do what it does
Agile Methodology
Aims for customer satisfaction through early and continuous delivery of useful software components
developed by an iterative process using the bare minimum requirements
waterfall methodology
a sequential, activity-based process or sequence of phases in which the output of each phase
becomes the input for the next phase
Agile Manifesto Principles (Frist 6)
1. Our highest priority is to satisfy the customer through early and continuous delivery of valuable
software.
2. Welcome changing requirements , even late in development. Agile processes harness change for
the customer's competitive advantage.
3. Deliver working software frequently, from a couple of weeks to a couple of months, with a
preference for the shorter timescale
4. Business people and developers must work together daily throughout the project.
5. Build projects around motivated individuals. Give them the environment and support they need,
and trust them to get the job done.
6. The most efficient and effective method of conveying information to and within a development
team is face-to-face conversation.
Agile Manifesto (last 6)
7. Working software is the primary measure of progress.
8. Agile processes promote sustainable development. The sponsors , developers, and users should be
able to maintain a constant pace indefinitely.
9. Continuous attention to technical excellence and good design enhances agility.
10. Simplicity-the art of maximizing the amount of work not done-is essential.
11. The best architectures, requirements, and designs emerge from self-organizing teams.
12. At regular intervals , the team reflects on how to become more effective, then tunes and adjusts
its behavior accordingly.
Scrum
Uses small teams to produce small pieces of deliverable software using sprints, or 30-day intervals, to
achieve an appointed goal
Scrum (heavy focus)
on continuous improvement of the product, the team and the working environment.
Scrum Team
1. Product Owner
2. Development Team
3. Scrum Master
cross-functional, which is a fancy way of saying that the different members of the organization
User Story
is a tool used in Agile software development to capture a description of a software feature from an
end-user perspective
, Is User Story a fundamental part of Agile? T/F
False it is not a fundamental part it is just a tool .
If you see questions asking about user story in the test most likely those answers are wrong as its not
essential.
Spike
is a user story that the team cannot estimate the effort.
Label in Jira
SPIKE - "User Story Title"
Sprint Zero
don't do this that is bad practice, all Sprints should start with 1. If you see something in the test about
sprint zero that is most likely wrong.
Story Points
Though helpful are not a part of the scrum guide so if you see that you can most likey know it is wrong
Backlog Items need the following
Description
Order
Estimate
Value
Dependecies are not essential but if you do they do need to be made and made transparent
Risk Register
risk exposure = likelihood of it happening x impact if it does happen. Value to red, amber green (RAG)
Discovery
The correct product for the correct problem
1. Define the problem
2. Find Solutions
3. Choose solution to build
4. Plan how to build the solution
5. Create a prototype of MVP
6. Test solution
7. Evaluate
8. Refine and repeat
Product vision
High level strategy of the goals of your product (not focused to a specific release)
Good product vision will have the following:
1. What the product will do
2. Who is the product for
3. Why the product will do what it does
