Docsity
Docsity
Prepare for your exams
Prepare for your exams

Study with the several resources on Docsity

Earn points to download
Earn points to download

Earn points by helping other students or get them with a premium plan

Guidelines and tips
Guidelines and tips
Sell on Docsity
Sell on Docsity
Docsity AI
Docsity AI
Log inSign up

Prepare for your exams

Study with the several resources on Docsity

Find documents

Prepare for your exams with the study notes shared by other students like you on Docsity

Search for your university

Find the specific documents for your university's exams

Docsity AINEW

Summarize your documents, ask them questions, convert them into quizzes and concept maps

Explore questions

Clear up your doubts by reading the answers to questions asked by your fellow students

Earn points to download

Earn points by helping other students or get them with a premium plan

Share documents
download point icon20 Points

For each uploaded document

Answer questions
download point icon5 Points

For each given answer (max 1 per day)

All the ways to get free points
Get points immediately

Choose a premium plan with all the points you need

Study Opportunities

Choose your next study program

Get in touch with the best universities in the world. Search through thousands of universities and official partners

Community

Ask the community

Ask the community for help and clear up your study doubts

Free resources

Our save-the-student-ebooks!

Download our free guides on studying techniques, anxiety management strategies, and thesis advice from Docsity tutors

Agile Methodology in Software Development, Exams of Nursing

Chamberlain College of NursingNursing

This document provides a comprehensive overview of the agile methodology, covering key concepts such as agile teams, backlogs, scrum roles, agile events, and the scaled agile framework (SAFe). It also discusses the roles and responsibilities of scrum masters, agile artifacts, and program-level concepts. The document aims to give a thorough understanding of agile methodology and its application in software development.

Typology: Exams

2023/2024

Available from 08/09/2024

TOPGradeBooster.
TOPGradeBooster. šŸ‡ŗšŸ‡ø

3.6

(63)

14K documents

1 / 6

Toggle sidebar

This page cannot be seen from the preview

Don't miss anything!

bg1
1 / 6
SSM Certification Exam Questions and Answers 2024
1. Agile Manifesto: Formal proclamation based on 4 core values and on 12 princi-
ples
2. Individual-Interaction: Over process and tools
3. Working software: Over comprehensive documentation
4. Agile team: Shows the dates matter and they meet their commitment
5. Scrum is built on three pillars what are they: Transparency, inspection, adap-
tation
6. Iteration length: 1 to 4 weeks
7. backlogs: Represents opportunities not commitment a list of what we want to do.
8. Backlogs: Comprised of NFRs
9. Backlogs are owned by?: Teams product owner
10. Backlogs: Created by agile team
11. Backlogs: Prioritize by product owners
12. Team increment: Thin vertical slice of functionality
13. Team increment: Backlog items must be defined as a vertical slices
14. Team increment: Each slice can be demonstrated and consumed
15. Team increment: Each slice represents and to and functionality.
16. Backlog refinement: Prepare requirements for iteration planning
17. Iteration planning: Team commit to a set of goals to be delivered in the iteration
18. Daily standup: Team member sync regarding the progress of the iteration goals
19. Iteration review: Deliverables reviewed with stakeholders providing feedback
20. Iteration retrospective: Team reviews and improve its process before the next
iteration
21. Scrum master: Coaches team improvement using values, principles, and best
practices
22. Scrum master: Facilitate scrum team events and protects the development
team
23. Scrum master: Helps to remove impediment and is a servant leader
24. Product owner - SCRUM: The single voice of the customer and stakeholders
in the team
25. Product owner - SCRUM: Owns and manages the team backlog and defines
an acceptance requirements
26. Product owner - SCRUM: Makes the hard calls on scope and content
27. The development team: Everyone who is needed to define build and test and
typically comprised of 3 to 9 people
28. The development team: Team members are only on this team and his self
organizing and accountable. Collaborative, cross functional and empowered.
29. Development team responsibilities: Listen and talk to people, see and except
pf3
pf4
pf5

Partial preview of the text

Download Agile Methodology in Software Development and more Exams Nursing in PDF only on Docsity!

SSM Certification Exam Questions and Answers 2024

  1. Agile Manifesto: Formal proclamation based on 4 core values and on 12 princi- ples
  2. Individual-Interaction: Over process and tools
  3. Working software: Over comprehensive documentation
  4. Agile team: Shows the dates matter and they meet their commitment
  5. Scrum is built on three pillars what are they: Transparency, inspection, adap- tation
  6. Iteration length: 1 to 4 weeks
  7. backlogs: Represents opportunities not commitment a list of what we want to do.
  8. Backlogs: Comprised of NFRs
  9. Backlogs are owned by?: Teams product owner
  10. Backlogs: Created by agile team
  11. Backlogs: Prioritize by product owners
  12. Team increment: Thin vertical slice of functionality
  13. Team increment: Backlog items must be defined as a vertical slices
  14. Team increment: Each slice can be demonstrated and consumed
  15. Team increment: Each slice represents and to and functionality.
  16. Backlog refinement: Prepare requirements for iteration planning
  17. Iteration planning: Team commit to a set of goals to be delivered in the iteration
  18. Daily standup: Team member sync regarding the progress of the iteration goals
  19. Iteration review: Deliverables reviewed with stakeholders providing feedback
  20. Iteration retrospective: Team reviews and improve its process before the next iteration
  21. Scrum master: Coaches team improvement using values, principles, and best practices
  22. Scrum master: Facilitate scrum team events and protects the development team
  23. Scrum master: Helps to remove impediment and is a servant leader
  24. Product owner - SCRUM: The single voice of the customer and stakeholders in the team
  25. Product owner - SCRUM: Owns and manages the team backlog and defines an acceptance requirements
  26. Product owner - SCRUM: Makes the hard calls on scope and content
  27. The development team: Everyone who is needed to define build and test and typically comprised of 3 to 9 people
  28. The development team: Team members are only on this team and his self organizing and accountable. Collaborative, cross functional and empowered.
  29. Development team responsibilities: Listen and talk to people, see and except

help, embrace change, work on items in an order set by the product owner.

  1. Development team responsibilities: Be proactive and self-motivated. Be hon- est. Be passionate about what you do. Embrace all sink or all swim. Everyone involved has skin in the game.
  2. 4 Core values of SAFe: Built in quality, program execution, alignment, and transparency
  3. Safe lean agile principles: Take and economic view. Apply system thinking.
  4. Safe lean agile principles: Assume variability ; preserve options. Build incre- mentally with fast, integrated learning cycles
  5. Safe lean agile principles: Base milestones on objective evaluation of working systems. Visualize and limit work in progress, reduce batch sizes, and manage queue length.
  6. Safe lean agile principles: Apply cadence, synchronize with cross domain planning. Unlock the intrinsic motivation of knowledge workers. D centralized de- cision-making
  7. Agile release train: It's a virtual organization of 5 to 12 teams comprised of 50 to 125 individuals that plans, commits, and execute together
  8. Agile release train: Program increment is a fixed time box; default is 10 weeks
  9. Agile release train: Synchronized iterations and program increment. Aligned to a common mission via a single program backlog
  10. Agile release train: Operate under architectural and user experience guidance. Frequently produces valuable and evaluable system level solution
  11. Release train engineer: Acts as the chief scrum master for the train
  12. Product management or product owner: Owns, defines, and prioritizes the program backlog
  13. System architect/engineering: Provides architectural guidance and technical enablement to the teams on the train
  14. The system team: Provides processes and tools to integrate and evaluate assets early and often
  15. PI planning: Team commit to a set of objectives to be delivered in the program increment
  16. ART Sync: Train teams to synchronize regarding the progress of the program increment
  17. System demo: Deliverables reviewed with stakeholders providing feedback
  18. Inspect and adapt event: The train reviews and improve its process before the next program increment
  19. Solution train: Coordinates development of large solutions and synchronizes multiple ARTs and suppliers

Coaches the team on agile best practices

  1. Program level calendar: This type of calendar is comprised of program incre- ment planning, demos, inspect and at that workshops.
  2. Team level calendar: This type of calendar is comprised of iteration planning, iteration review, iteration retrospectives
  3. Feature: Is an industry standard term familiar to marketing and product man- agement
  4. Acceptance criteria: Is typically defined during program backlog refinement
  5. Benefits hypothesis: Justifies feature implementation cost and provides busi- ness perspective when making scope decisions
  6. Features: Have benefit hypotheses and acceptance criteria
  7. Features: Decompose into stories by the teams on the train
  8. CCC of user story guidelines: It's written on the card, details are in the conver- sation with the product owner, acceptance criteria confirms the story correctness
  9. Acceptance criteria: It provides the details of the story from a testing point of view and are created by the agile team
  10. Acceptance criteria: Expresses the conditions that need to be satisfied for the customer
  11. Acceptance criteria: Provides context for the team, more details of the story, and help the team know when they are done.
  12. Acceptance criteria: Is written by a customer/product owner and refined by the team during backlog grooming and iteration planning
  13. Advantages of acceptance criteria: Continue the conversation between the product owner and the team, helps solidify expectation for the story.
  14. Advantages of acceptance criteria: Spawns negotiation, trade-offs, and op- tions to split a large story into smaller stories. Establishes a high-level test plan. Provides a basis for solution design.
  15. A story: is independent, negotiable, valuable, estimable, small, testable
  16. Story point: Is singular number that represents volume, complexity, knowledge and uncertainty.
  17. Types of enablers: Spikes and refractors
  18. Estimating poker: Combines expert opinion, analogy, and disaggregation for quick but reliable estimates. All team member participate
  1. Velocity: Capacity =5 * 8 =40 puts / iteration
  2. Vision: It's a description of the future state of the solution under development. It reflects customer and stakeholder needs as well as the feature and capabilities proposed to meet those needs.
  3. Roadmap: Is a schedule of events and milestones that communicate planned solution deliverables over a timeline. It includes commitments for the planned, upcoming program increment and offers visibility into the deliverables forecasted for the next few program increments
  4. WSJF: Is a prioritization model used to sequence jobs to produce maximum economic benefit. In safe, is estimated as the cost of delay divided by job size
  5. Program level: This level contains the roles and activities needed to continu- ously deliver solutions via an agile release train.
  6. Program level: This is the level where development teams, stakeholders, and other resources are devoted to some important, Ongoing solution development mission.
  7. Value streams: It represent the series of steps that an organization uses to build solutions that provide a continuous flow of value to a customer.
  8. Epic: It's a container for solution development initiative large enough to require analysis, the definition of a minimum viable product and financial approval prior to implementation.
  9. Epic owners: They are responsible for coordinating portfolio Epic through the portfolio kanban system. They define the epic, it's minimum viable product, and lean business case, and when approve, facilitate implementation.
  10. System demo: It's a significant event that provides an integrated view of the new features for the most recent iteration delivered by all teams in the agile release training. Each demo gives agile release train stakeholders an objective measure of progress during a program increment.
  11. Architectural runway: It consists of existing code, components, and technical infrastructure needed to implement near term features without excessive redesign and delay.
  12. Enterprise architect: Promotes adaptive design, and engineering practices and drives architectural initiatives for the portfolio.