Agile & SCRUM Basics

Scrum Teams are self-organizing, meaning they have the autonomy and responsibility to determine how they will accomplish their work. This allows the team to collaborate and make decisions collectively, fostering a sense of ownership and accountability. Additionally, Scrum Teams are cross-functional, meaning they have all the necessary skills and expertise within the team to deliver a complete product increment. This enables the team to be versatile and adaptable, as they can handle various tasks and roles without relying on external resources.

The Agile Manifesto emphasizes the importance of individuals and interactions over processes and tools, working software over comprehensive documentation, customer collaboration over contract negotiation, and responding to change over following a plan. Therefore, all of the options listed (1,2,3,4) are correct as they accurately reflect the principles outlined in the Agile Manifesto.

The correct answer signifies that a user story should be independent, negotiable, valuable, estimable, small, and testable. This means that a user story should be able to stand alone and not depend on other stories, it should be open to discussion and negotiation, it should provide value to the customer, it should be able to be estimated in terms of effort and time, it should be small enough to be completed within a single iteration, and it should be testable to ensure that it meets the desired outcomes.

Each team member in the Daily Scrum Meeting answers the following main questions: What did you do yesterday? Are there impediments in your way? What will you do today?

The correct answer is 1,2,3,4. This is because all four principles are mentioned in the explanation. The first principle emphasizes the importance of simplicity in maximizing work done. The second principle emphasizes the frequent delivery of working software within shorter timescales. The third principle prioritizes customer satisfaction through early and continuous delivery of valuable software. The fourth principle encourages welcoming changing requirements to leverage customer advantage.

The correct answer is "A narrative text(s) that describe an interaction of the user and the system, focusing on the value a user gains from the system." This answer accurately describes a user story as a narrative text that highlights the interaction between the user and the system, emphasizing the value that the user derives from using the system. It captures the essence of a user story by emphasizing the user's perspective and the value they expect to receive from the system.

The correct answer is 3,4,1,2,5. The Scrum events are important time-boxed activities that occur during a Sprint. Sprint Planning is the event where the team plans the work to be done in the upcoming Sprint. Sprint Review is the event where the team presents the completed work to stakeholders. Sprint Retrospective is the event where the team reflects on their performance and identifies improvements. Daily Scrum is the event where the team synchronizes their work and plans for the day. Sprint is not an event, but rather the time-boxed period in which the team completes the work.

The correct answer is 1,4,3. This is because the three phases of Scrum are: 1) Pre-game, which includes activities such as project initiation, planning, and team formation; 2) Game, which involves the actual execution of the project, including daily stand-ups, sprint planning, and sprint reviews; and 3) Post-game, which includes activities such as retrospective meetings, project closure, and lessons learned. Therefore, the correct sequence of phases is 1,4,3.

The levels of planning in an agile model are identified as follows: 4-Product Level, 2-Release Level, 3-Sprint Level, and 1-Iteration Level. The planning process starts at the iteration level, where the team plans and executes an iteration. The iteration level planning is then rolled up to the sprint level, where multiple iterations are planned and executed. The sprint level planning is further rolled up to the release level, where multiple sprints are planned and executed. Finally, the release level planning is rolled up to the product level, where the overall product roadmap and strategy are defined.

The correct answer includes all four options: expert opinion, analogy, disaggregation, and planning poker. Agile estimating techniques often involve gathering input and insights from experts in the field, using analogies to compare the current project with similar past projects, breaking down tasks into smaller components for more accurate estimation, and using planning poker as a collaborative technique to reach a consensus on estimates among team members. Therefore, the correct answer is 1,2,3,4.

The three Scrum Pillars are Adaptation, Transparency, and Inspection. These pillars form the foundation of the Scrum framework and are essential for its successful implementation. Adaptation refers to the ability to adjust and make changes based on feedback and new information. Transparency ensures that all aspects of the project are visible and accessible to everyone involved. Inspection involves regularly reviewing the progress and outcomes of the project to identify areas for improvement. Therefore, the correct answer is 1,3,4.

The different Agile Processes include Extreme Programming, Crystal Methods, Lean Development, and DSDM (Dynamic System Development Model). The correct answer, 1,3,4,2, lists these processes in the correct order.

The artifacts of Sprint Planning Meeting are the Sprint Goal and the Sprint Backlog. The Sprint Goal is a concise statement that describes what the team aims to achieve in the upcoming sprint. The Sprint Backlog is a list of the product backlog items selected for the sprint, along with a plan for delivering the product increment and realizing the Sprint Goal. The Sprint Retrospective and Sprint Review Meeting are not artifacts of the Sprint Planning Meeting.

Disaggregation is the correct answer because it involves breaking down a story or feature into smaller, more manageable parts. This technique helps in estimating the effort required for each individual piece, making the overall estimation more accurate. By breaking down the task into smaller components, it becomes easier to understand and estimate the work involved in each part, leading to better planning and allocation of resources.

Agile delivers business value incrementally by breaking down work into small, manageable chunks and delivering them in iterations. This allows for early and continuous feedback from stakeholders, ensuring that the product meets their needs. By delivering value iteratively, Agile teams can continuously improve and adapt based on feedback received, resulting in a more successful end product.

Agile is applicable mostly to projects that have characteristics such as urgency, complexity, and uniqueness. Urgent projects require quick and flexible responses, which is a key aspect of agile methodology. Complex projects often involve multiple teams and require constant adaptation, making agile a suitable approach. Unique projects, which are different from previous ones, benefit from the iterative and collaborative nature of agile. Therefore, the combination of urgency, complexity, and uniqueness makes 1,2,4 the correct answer.

The correct answer is "As a I want to so that ,As a I want to so that ". These user story formats are considered the best because they clearly define the user, their goal, and the desired outcome or benefit. The inclusion of acceptance criteria ensures that the user story is specific and measurable, while the mention of benefits highlights the value that the user expects to gain from the goal.

Planning poker is a collaborative estimation technique that combines the use of expert opinions, triangulation, analogy, and disaggregation. Expert opinions are gathered from team members with relevant expertise to provide input on the estimated effort or complexity of a task. Triangulation involves comparing the task to similar past tasks to estimate its size. Analogy is used to compare the task to a similar one that has already been completed to estimate effort. Disaggregation involves breaking down the task into smaller, more manageable parts to estimate effort accurately. By incorporating these techniques, planning poker allows for a more accurate and collaborative estimation process in Scrum methodology.