The ScrumMaster manages the Team’s process True False.
The Sprint Review is the meeting in which the Product Owner accepts or
rejects the completed Sprint PBIs. True False.
The Daily Scrum is a time for detailed problem solving. True False.
The ideal size for the Development Team is 5 to 9 people. True False.
The primary purpose of the Sprint Retrospective is to identify process
improvements.
True False.
The Development Team chooses which PBIs in the Product Backlog will go in
the Sprint Backlog. True False.
The Sprint is extended when the work takes longer than expected. True False.
The primary responsibility of the Scrum Master is to observe, guide and coach
the Scrum Team to continuously improve at delivering valuable product. True False.
PBI priorities are decided by the Product Owner True False.
Stakeholders are encouraged to request changes directly to the Development
Team to save time for the Product Owner. True False.
Periodic testing Sprints are the preferred mechanism for ensuring high quality.
True False.
All PBIs are written by the Product Owner. True False.
The Development Team needs full details of each PBI in order to estimate the
size or complexity of the item. True False.
The Development Team can change their process to improve efficiency. True False.
Estimates are made for the Development Team by Technical Leads, Managers
or Architects. True False.
An unfinished PBI is automatically carried over to the next Sprint. True False.
Only one Sprint is planned at a time. True False.
The ScrumMaster manages the Development Team. True False.
A detailed Product Requirements Document will improve the Scrum Team’s
ability to respond to customer needs True False.
The Scrum Master is a member of the Scrum Team. True False.
The main purpose of the Sprint Review is to get Product feedback from the
Stakeholders.
True False.
When Product delivery is constrained by a deadline, the primary control
variable is scope. True False.
The ScrumMaster can make priority decisions on behalf of the Product Owner. True False.
The Scrum Team can request an Abnormal Termination if the Sprint Plan is
significantly invalidated or interrupted by external factors True False.
Management can replace one PBI in the Sprint Backlog with another during the
Sprint. True False.
The ScrumMaster assigns tasks to Team members True False.
For most efficient flow, the Development Team should route all Product Owner
questions through the ScrumMaster. True False.
The ScrumMaster is responsible for protecting the Development Team from
both internal and external distractions True False.
The Scrum Team can adjust the Sprint Backlog during the Sprint by adding or
removing PBIs to fill the available time as long as a sustainable pace is
maintained. True False.
A ScrumMaster who works with more than one Development Team will be a
bottleneck True False.
Which of the following best describes the approach for determining the iteration (timebox)
length? Iterations (timeboxes) should always be 30 days The team determines iteration (timebox) length by dividing the total number of story
points by the average velocity of the team
Iterations (timeboxes) should always be two weeks The team should agree on the length of the iteration (timebox), taking the size and
complexity of the project into consideration.
. Which of the following is a characteristic of an Agile leader? Task focused Process oriented Supportive Disengaged.
Who is responsible for prioritizing the product backlog? Product Owner Project Manager Lead Developer Business Analyst.
What are the advantages of maintaining consistent iteration (timebox) length throughout the
project? It helps to establish a consistent pattern of delivery It helps the team to objectively measure progress It providea a consistent means of measuring team velocity All of the above.
Tracking project issues in an Agile project is the primary responsibility of the… Tester Project Leader Functional Manager Develope.
Why is it important to trust the team? High trust teams do not have to be accountable to each other High trust teams do not require a user representative The Project Manager does not then have to keep a project schedule
The presence of trust is positively correlated with the team performance
.
An effective workshop facilitator will always ... Involve the whole project team in all project workshops
Agree the process and participants of the workshop with the workshop owner before the
workshop Involve only those team members who will commit to doing further work after the
workshop
Act as a proxy for any invited participant who is unable to attend the workshop on the day
.
Which of the following best represents the Agile approach to planning? Planning is not part of an Agile approach, because Agile is exploratory Planning should be done in detail at the outset of a project and not revisited Planning should involve the whole team, not just the Project Manager Planning should all be done by the Project Manager.
Who should define the business value of a Feature within an Agile project? The individual end-users The Product Owner The Business Analyst The Business Sponsor.
. If a timebox (iteration) plan needs to be reprioritised in a hurry, who should re-prioritise? The developers alone (they know what the customer wants) The Product Owner (the developers would only choose the easy things as top priority)
The Project Leader (they can give an independent, pragmatic view) The whole team including Product Owner and developers (together they can consider
both business value and practicality).
What is the effect of having a large visible project plan on a wall? It removes the need to create any other reports for management It continuously communicates progress within the team and to other stakeholders It allows the Project Manager to allocate tasks to specific team members It is restrictive, as it does not allow the team to innovate and change.
. How should work be allocated to the team in an Agile project? The Team Leader (Scrum Master) should allocate specific tasks to individuals Tasks should be randomly allocated to team members, using Planning Poker Team members should self-select tasks appropriate to their skills The most complex tasks should be allocated by the Team Leader (Scrum Master)
.
What should the developers do if the customer representative is repeatedly too busy to be
available? Continue the work, record the assumptions and ask the customer later for input Send the customer a written warning that the end product will be completed on time, but
may not meet their needs Allow the Business Analyst to take on the role of Proxy Customer Representative Draw the problem to the attention of the Scrum Master (Team Leader)
.
Which one of the following is a key feature of documentation that you would expect to find in
an Agile project? System documentation created at the end of each increment, at the start of the
deployment
User Stories held in a spreadsheet or specialist database, where full details of user
conversations are recorded for future purposes, like handover to maintenance or support User Story cards containing only enough detail for planning and development, which will
need to be supplemented by further face-to-face conversations No written documentation, as all good communication is face-to-face.
When handling team dynamics, the Agile Leader should … Empower the team members, within appropriate limits Encourage an environment of competition and personal advantage Give clear directives to the team about what they should do and how Expect team members to be proactive and each work to their own priorities and objectives.
Which one of the following statements is correct regarding acceptance of any deliverables on
an Agile Project? The team should allow only senior managers to sign off deliverables The team should get acceptance of project deliverables from the appropriate
stakeholders at least at the end of every timebox / iteration The team should get acceptance of project deliverables from the users during a UAT phase
at the end of the project
Acceptance of any particular deliverable on the project is gained from all stakeholders at
the same time.
Which one of the following statements is correct regarding quality of deliverables from an Agile
Project? The products produced by an Agile project should be cheaper than those produced by any
other approach, but quality will suffer The products will be more expensive than by any other approach but will be top quality The products will be fit for purpose, but may not do what the customer wanted The products will be of appropriate quality, as guided by the customer representative
involved throughout the development process.
What is the Agile approach to doing design early in a project? A big design up front is always a good idea Just enough design up front gives a good foundation to start from and helps to mitigate
risk, without wasting unnecessarily time No design up front is the best approach as most of the fun of a project is in discovery of the
unexpected
Design has no place in an Agile project.
An Agile approach advocates which of the following approaches? Get something “quick and dirty” delivered, to save time Get something simple released as quickly as possible Get something business-valuable delivered as quickly as possible, consistent with the
right level of quality Get something delivered once it has been fully documented and the documentation has
been signed off as complete.
Which of these best describes the Agile approach to team-working? The team should plan to work a small amount of overtime regularly throughout the
project The team should expect to work longer hours towards the end of the sprint (timebox), in
order to deliver all that was committed to The team should strive for a sustainable pace and a normal working week The team will “burn out” if they have to work overtime for more than two sprints
(timeboxes, iterations) in a row.
Which one of the following statements about workshops is true for Agile projects? All project stakeholders should attend requirements workshops Retrospectives are only run at the end of a project It is best if the Project Manager facilitates the project’s workshops An independent facilitator will manage the structure of a facilitated workshop but not
input to the content.
Which one of the following is an important feature of the daily stand-up / wash up / Scrum
meeting? Everyone is expected to stand for the whole time, to keep the meeting short The meeting must be kept short and well structured The meeting should ensure that it is clear to all which team members are not performing No-one is allowed to leave the stand-up meeting until all problems raised have been solved.
. Who should attend the stand-up meetings? Sponsor and Executive Management only Project Manager and Technical Leads only Project Leader and Customer Representatives only The entire team
.
One of the development stages you would expect to see a team go through is: Storming Warming Cloning Yawning
.
When estimating is done for a project, the developers should Be fully involved in the estimating process Be in total control of the estimating process
Be consulted after the Team Leader (Scrum Master) has made the estimates for the team’s
work
Not make estimates unless velocity is already known
.
During an iteration (sprint) (timebox) the developers should be: Able to contact the customer to clarify aspects of the work Completely uninterrupted by the customer In twice-daily contact with the customer Able to work without needing to disturb the customer.
The end result of an Agile development is: A product of a professional quality which fits the business need A product of almost as good a quality as a Waterfall development
A product which is barely sufficient for its purpose and deliberately not maintainable A technically-perfect, re-factored solution.
An Agile customer … Must have a thorough understanding of Agile techniques, for Agile to work Will always receive lower-quality products than their non-Agile counterparts Will typically get business value delivered early and often Will need to understand the technical aspects of development, to contribute effectively.
An Agile team … Is self-organizing, with each member having the same technical skills Collaborates and supports its team members Ensures that weak members of the team are allocated the simpler tasks Ensures blame is allocated fairly
.
The Agile process … Encourages the team to meet regularly Has no meetings Has lengthy reporting requirements Has no reporting requirements.
The Agile Leader … Should allocate tasks to the team members each day at the stand-up meeting Should involve the team in their own work-allocation
Should give detailed work-plans to the team each day Should direct the work of the team, if they are inexperienced.
What is Kan Ban? A list of activities banned by the team, in relation to Team Norms The set of Can Have stories for a project
A visible chart of work to do, work in progress and work done A graph of tasks partially-completed by the team.
What is meant by “Yesterday’s Weather” in an Agile project? Teams work less well when it rains Keeping metrics of earlier work to help with future estimates Retrospectives should include less important topics, such as the weather, as ice-breakers Estimating is as futile as predicting the weather.
In Agile projects, we plan to “learn as we go” because… It creates a better relationship between the developers and customer representatives Many projects are evolutionary, and a better solution emerges this way It is time-consuming to analyse everything at the beginning of a project
It prevents late delivery of the project.
The recommended approach to design in an Agile project is: No design up front Big design up front
Just enough design up front Use a previous design – it will be “good enough”.
What is the personal risk that an Agile Leader takes in empowering the team? The Agile Leader might lose their job, as the team is doing all the work If the team fails, the Agile leader will not get a performance bonus The Agile Leader has less direct control over the team’s work, but still has the
responsibility for their outcomes The Agile Leader cannot share the glory of team success.
The Agile approach to documentation is:
Do no documentation because it is a waste of time Do sufficient documentation to prove you have done a good job
Do the necessary documentation to support the development and use of the product Do more documentation than usual, because Agile is risky
.
The Agile way is To produce working product of the right quality, early and incrementally To produce working product after documentation has been signed off To produce simple prototypes early, but no finished product until the end of the project
To produce products without technical integrity, but re-engineer later.
The customer in an Agile project ….
Has no control over the prioritization of delivered features Has total control over the prioritization of features
Collaborates with the developers over prioritization of features, but the developers have
the final decision Collaborates with the developers over prioritization of features, but the business has the
final decision.
In the popular prioritization technique called “MoSCoW”, the “M” stands for ... May have Major Must Have Mandatory.
The working culture of an Agile team is … Collective Collaborative Connective Contemplative.
The leadership style of an Agile Leader is … Directive Assertive Facilitative Feature-based.
. The Agile Manifesto states the following values: People are more important than contracts Working software should have priority over comprehensive documentation Plans should have priority over ability to respond
Contracts should be negotiated which allow control over the people.
Which of the following are attributes of an Agile team? Courage to change and adapt Trust of fellow team members to do the work Responsiveness to change All of these.
A sustainable pace means … If the team members work long hours regularly they will get used to it, and be able to
sustain it A 40 hour week is only for the weaker members of the team. Others can do more The team should establish a velocity which can be sustained within normal working
hours Working long hours is the only way to deliver on time.
A burn-down chart shows … The energy level and velocity of the team The remaining work (effort, points) to complete before the iteration (timebox) end The number of hours worked by each team member during the iteration (timebox)
The rate of spending of the budget for a project.
The reason for holding regular Retrospectives is: It allows the team to take a necessary break from work It gives management information to use in team members’ performance reviews It allows learning which can be used to improve team performance during the project It prevents deviation from the process which the team has been following.
Once a project is underway, the approach to planning is: Plans should never be changed It is normal to need to plan and re-plan as the project progresses
Plans should only be changed with full approval of all stakeholders Plans are not required as Agile is incremental.
An Agile project … Should have no control over its progress Should be able to demonstrate control of its progress Is always out of control Is controlled by the velocity of the most junior team member.
An Agile project should have ...
Occasional early deliveries, if the business is prepared to accept lower quality A regular pattern of delivery of developer-focused products A regular pattern of delivery of business-valued increments An irregular and unpredictable delivery of products.
When an Agile team is successful … It should be encouraged to celebrate success only when the project is over It should be encouraged to celebrate even small successes immediately It should not celebrate success, as this wastes project budget
It should not celebrate success, as this makes less successful teams feel bad.
. In order to communicate well, the Agile project should ... Keep team-size large, to avoid stakeholders feeling left out
Break the project into small, mixed-skill, self-organising teams
Operate with one team of less than 10 people
Operate with separate customer, developer and test teams
.
If a new requirement emerges once an Agile project is running, it should be: Automatically included in the work of the project Automatically excluded and left until a later project or increment Assessed for importance and, if sufficiently important to the business, included in the
project, displacing less important requirements Put on the backlog for consideration by the wider group of stakeholders after the project
has been completed
.
You have been engaged as the Technical Coordinator in a product development team. The
customer (Product Owner) and Team Leader (Scrum Master) are happy because the team
always delivers business value on time. However, you worry that the technical debt is
increasing. What would be your primary goal to ensure the right quality? Ensure testers define their entry criteria for quality, which they impose on the
development team Nothing. Prescribed roles such as technical coordinators are not part of an Agile team
Make sure that the maintainability quality attribute is addressed On time delivery and happy end users are the only quality measures in Agile development.
How could maintainability of the developing product be improved in a development team? Apply standard design patterns All of these Make refactoring a common practice Ensure unit testing is included in the “done” criteria.
Agile methods are described as “adaptive” because… Agile teams have the empowerment to frequently respond to change and to learn on a
project by changing the plan The rate of development progress on an Agile project is constantly tracked to allow
adaptation Project Managers are not needed in Agile methods because teams are self-organising Workshops held at the beginning and the end of every iteration (timebox) allow the team
to adapt the product specification.
What do all Agile approaches have in common? A prescribed, fixed iteration (timebox) length Iterative development and incremental delivery A strict focus on on-time delivery A large set of clearly defined roles.
What is one difference in responsibility between a Project Manager and a Scrum Master (Team
Leader) in an Agile project? None. It's basically the same. Scrum Master (or Team Leader) is just a better term than
Project Manager in an Agile project The Project Manager creates the detailed delivery plans while the Team Leader monitors
execution within the team Project Manager communicates with project governance authorities when necessary
The Project Manager monitors the realisation of benefits in the business case. .
How could you benefit from having an End User Representative in your development team? End users should NOT be in the development team. Requirements are always
communicated to the developers by the Product Owner, who is part of the customer team The End User Representative will be solely responsible for acceptance tests within the
team The End User Representative assures that user stories are documented properly
The End User Representative will be able to clearly tell the developers what will work for
an end user
.
The responsibilities of a Product Owner will include … Business processes diagramming Prioritizing requirements Managing the project budget All of these.
What often-false assumption does the waterfall model made about requirements specifications? Specifications are predictable Specifications are stable Specifications have low change rates
All of the above None of the above.
True or false? It is better to discover defects later in the development process. That way, you can have
more of the system finished before you worry about fixing things. True False.
An empirical process model iterates between… … feedback and adaptation … design and implementation … requirements gathering and design … user studies and testing None of the above.
True or false? In iterative software development, it is recommended that iterations be 3 to 6 months in
length. True False.
If your project has unstable requirements (i.e., that are prone to change), you should use a waterfall
process model. True False.
In iterative development, how long should an iteration generally be? 1 week 2–6 weeks 2–4 months 6 months to a year None of the above.
Which of the following is meant by a software development process? A running instance of a program; for example, a UNIX process is a softw. devel. process Something developers do to accomplish a goal during a project; for example, planning poker
is a softw. devel. process for estimation Something developers use to accomplish a goal during a project; for example, Subversion is a
softw. devel. process for configuration management A structure imposed on the development of a software product; for example, developing iteratively and incorporating best practices might be ingredients in a softw. devel. process . None of the above.
Which one of the these is a bad length for an iteration? 1 week 2 weeks 4 weeks 6 weeks All of the above.
Which one of these is appropriate in an agile and iterative development process? Gather a complete set of requirements before designing/building anything. Implement the backend of the system first—that is, before implementing the frontend functionality with which users interact. Generate and maintain complete, detailed design documents, which comprehensively model
all aspects of the design. Implement the system incrementally, building it up bit by bit Test the code at the end, after the system has been completely implemented.
Which of the following is not an agile value? Individuals and interactions over processes and tools Working software over comprehensive documentation Customer collaboration over contract negotiation Responding to change over following a plan None of the above (i.e., all are agile values).
Which of the following problems does iterative development directly address? Design erosion Unstable requirements Program comprehension
All of the above None of the above.
Which type of process control model is appropriate for software development? A “defined” process control model An “empirical” process control model A “remote” process control model A “parallel” process control model None of the above.
In the _____ development process, the various phases of development are completed sequentially,
one after the other (e.g., gather all the requirements, then design the whole system, then implement
the whole system, and so on). iterative waterfall agile spiral None of the above.
True or false? In iterative software development, iterations should be 2 to 6 days in length True False.
In software engineering, defects that are discovered ______ are ______ to fix. earlier; more expensive later; more expensive by customers; more difficult by developers; more difficult None of the above.
Which of the following is meant by a software engineering process? Tools, such as Git, that developers use to accomplish their software engineering goals
An organization or structure imposed on the tasks and activities involved in developing a
software product
A thread of control in a multithreaded computing system, such as the Rails web server All of the above None of the above.
Which term is best defined by the following text?
Development of a system through repeated cycles and in smaller portions at a time, allowing software
developers to take advantage of what was learned during development of earlier parts or versions of
the system Configuration management Iterative development process Waterfall development process Verification and validation None of the above.
Which term is best defined by the following text?
Development of a system whereby progress is seen as flowing steadily downwards through the phases
of conception, analysis, design, construction, testing, production, and maintenance, and wherein one
should move to a phase only when its preceding phase is reviewed and verified Configuration management Iterative development process . Waterfall development process Verification and validation None of the above.
Which of the following is an issue associated with the waterfall development process? Falsely assumes that requirements are stable and can be known from the start System defects are often discovered late in the development process Can lead to “analysis paralysis” wherein a considerable investment of time and effort is put
into a project before any code is written All of the above None of the above.
Tracking project impediments in a Scrum project is whoes primary responsibility? Tester ScrumMaster Functional Manager Developer.
-Which concept of the following is NOT defined in the Scrum Framework? ScrumMaster Project Manager Scrum Product Owner Daily Scrum.
Which of the following main events are defined by Scrum Framework?
A) Sprint Planning Meeting
B) Sprint Retrospective Meeting
C) Sprint Review Meeting
D) Mid-Sprint Status Review Meeting
E) Daily Scrum Meeting
A, B, C, D, E A, B, C, D A, B, C, E A, C, D, E
.
4-What are the disadvantages of the classical waterfall model? (Select the best alternative)
A) End-Product has to be fully anticipated beforehand
B) Some requirements are implemented as defined in the beginning of the project, and yet
they are not really needed by the customer
C) Each phase is strictly separated
Mark one answer: A A,B C,B A,B, C
.
What is the effect of having a large visible Story board on a wall? It removes the need to create any other reports for management
It continuously communicates progress within the team and to other stakeholders It allows the Project Manager to allocate tasks to specific team members It is restrictive, as it does not allow the team to innovate and change.
What does NOT belong to the agile manifesto's main pillars? Individuals and interactions over processes and tools Working software over comprehensive documentation
Processes over people Customer collaboration over contract negotiation.
-Which of the following is NOT a typical artifact of the Scrum framework? Product Backlog Sprint Backlog Burn down char Gantt chart
.
How should work be allocated to the team in an Agile project? The Team Leader (ScrumMaster) should allocate specific tasks to individuals Tasks should be randomly allocated to team members, using Planning Poker Team members should self-select tasks appropriate to their skills The most complex tasks should be allocated by the Team Leader (ScrumMaster)
.
-Where are the customer requirements stored? In the Product Backlog
In the Sprint Backlog In a database In a Scrum Product Requirement Specification
.
-Which of the following best describes the approach for determining the Sprint length? Sprint should always be 30 days The team determines Sprint length by dividing the total number of story points by the average
velocity of the team Sprint should always be two weeks The team should agree on the length of the Sprint, taking the size and complexity of the project
into consideration.
Which of the following are roles in the Scrum framework? Product Owner Project Manager Lead Developer Business Analyst
.
What should the developers do if the product owner is repeatedly too busy to be
available? Continue the work, record the assumptions and ask the customer later for input Send the customer a written warning that the end product will be completed on time, but may
not meet their needs Allow the Business Analyst to take on the role of Proxy Customer Representative Draw the problem to the attention of the ScrumMaster.
Which of the following responsibilities is NOT one of the Scrum Master's Removing impediments Facilitating meetings Reminding the team of the process
Assigning tasks to team members.
-Who ultimately decides when the team has enough work for the sprint in planning? The ScrumMaster The product owner The team The product owner, ScrumMaster and team vote to determine when the sprint backlog is full.
-What are the two main artifacts of a sprint planning meeting? A sprint goal and a sprint backlog A requirements documents and a Gantt chart A requirements documents and a test plan A test plan and a Gantt chart
.
Who should define the business value of a Feature within the Scrum Project? The individual end-users The Product Owner The Business Analyst The Business Sponsor.
-What are the advantages of maintaining consistent Sprint length throughout the
project? It helps to establish a consistent pattern of delivery It helps the team to objectively measure progress It provide a consistent means of measuring team velocity All of the above
.
Where are the customer requirements stored? In the Product Backlog
In the Sprint Backlog In a database
In a Scrum Product Requirement Specification
.
Who is responsible for prioritizing the product backlog? Product Owner Project Manager Lead Developer Business Analyst
.
Which one of the following statements is correct regarding acceptance of any
deliverables on a Scrum Project? The team should allow only senior managers to sign off deliverables The team should get acceptance of project deliverables from the appropriate stakeholders at
least at the end of every Sprint
The team should get acceptance of project deliverables from the users during a UAT phase at
the end of the project Acceptance of any particular deliverable on the project is gained from all stakeholders at the
same time.
What is mainly defined by the Scrum Framework?
A) Rules & Roles
B) Document guidelines
C) Artifacts and events
Mark one answer: A B B,C A C.
How should work be allocated to the team in an Agile project? The Team Leader (ScrumMaster) should allocate specific tasks to individuals Tasks should be randomly allocated to team members, using Planning Poker Team members should self-select tasks appropriate to their skills The most complex tasks should be allocated by the Team Leader (ScrumMaster).
Which of the following are roles in the Scrum framework? Scrum Master Product Owner Team All of the above.
Which one of the following is a key feature that you would expect to find in an Agile
project? System documentation created at the end of each increment, at the start of the deployment
User Stories held in a spreadsheet or specialist database, where full details of user
conversations are recorded for future purposes, like handover to maintenance or support User Story cards containing only enough detail for planning and development, which will need
to be supplemented by further face-to-face conversations
No written documentation, as all good communication is face-to-face.
The end result of a Sprint is A product of almost as good a quality as a Waterfall development
A product of a professional quality which fits the business need A product which is barely sufficient for its purpose and deliberately not maintainable A technically-perfect, re-factored solution
.
A Scrum Master .... Should allocate tasks to the team members each day at the stand-up meeting Should involve the team in their own work-allocation Should give detailed work-plans to the team each day
Should direct the work of the team, if they are inexperienced.
A major theme in Scrum is "inspect and adapt." What does it mean? Scrum insists on auditors who frequently inspect the work of the team and suggest ways to
adapt the process in order to improve quality Scrum recommends that upper management inspect the Burndown charts and notes from the
daily scrums to find ways in which the team should adapt their practices to be more productive. Scrum emphasizes taking a short step of development, inspecting both the resulting product
and the efficacy of current practices, and then adapting the product goals and process practices Inspect and adapt refers to the ScrumMasters role in inspecting the work and writing stories
designed to help the team produce higher quality software.
Which one of the following statements is correct regarding quality of deliverables from
a Scrum Project? The products produced by a scrum project should be cheaper than those produced by any
other approach, but quality will suffer The products will be more expensive than by any other approach but will be top quality The products will be fit for purpose, but may not do what the customer wanted
The products will be of appropriate quality, as the guidanceof the product owneris involved
throughout the development process.
The Scrum approach to documentation is: Do no documentation because it is a waste of time Do the necessary documentation to support the development and use of the product Do sufficient documentation to prove you have done a good job Do more documentation than usual, because Agile is risky.
In Scrum projects, we plan to "learn as we go" becauseÊu It creates a better relationship between the developers and customer representatives Many projects are evolutionary, and a better solution emerges this way
It is time-consuming to analyze everything at the beginning of a project It prevents late delivery of the project.
5-What is meant by Kan Ban? A list of activities banned by the team, in relation to Team Norms The set of Can Have stories for a project A visible chart of work to do, work in progress and work done A graph of tasks partially-completed by the team.
-Which of the following choices is a key reason to adopt an agile process like Scrum? To be up to date on the latest process To shake things up in the organization To hold programmers and tests accountable for their work To be better able to respond to change
.
-During a sprint the developers should be: In twice-daily contact with the product owner Completely be uninterrupted by the product owner Able to contact the product owner to clarify aspects of the work
Able to work without needing to disturb the product owner.
The primary purpose of the daily scrum (daily stand-up) is To give a status report to the ScrumMaster To give a status report to the product owner To share as a team what each member is working on and uncover obstacles standing in the
way of completing the work To give team members a chance to take a break from their tasks.
-What is the Scrum approach to doing design early in a project?
A big design up front is always a good idea Just enough design up front gives a good foundation to start from and helps to mitigate risk,
without wasting unnecessarily time No design up front is the best approach as most of the fun of a project is in discovery of the
unexpected Design has no place in an Agile project.
|
