Result #1340987006 ProQuiz Results
Name : Amandeep Singh Username : cyber_aman Current Rank : 18 Percentage : 53.85 % Current Percentile : 60.87 Total Question : 65 Total Correct Answers : 35 Total Time : 60 min Time Used : 48:39 min
Q.1 PMI-ACP
Which of the following may not be considered when prioritizing the development of new capabilities during release planning?
Financial Value of the feature The amount of risk removed by developing the feature Cost Involved in the development of the feature Availability of expert developer for that particular area , a developer who can implement this particular feature faster than other developers.
Q.2 PMI-ACP
Which of the following is not true about iteration planning ?
Iteration plan identifies who is going to work on which task An iteration plan can be as simple as a spreadsheet or a set of note cards with one task handwritten on each card
Iteration plan provides detail level view based on high level view provided by release plan Iteration plan provides tasks list against the stories
Q.3 PMI-ACP
Why are the tasks of an iteration plan estimated in hours but the stories of a release plan are estimated in story points or ideal days?
For the work involved in iteration team should have a reasonable level of insight. This allows them to credibly estimate the tasks of an iteration in hours During the release planning we may be working with assumed velocity but while planning iteration usually we have velocity information of previous iteration, which makes estimation in hours possible Because during the release planning it was not known who is working on which task but now we know who is working on which task , so person can estimate the duration in hours Information like people taking leave or attending training are known while planning iteration which makes estimation in hours possible.
Q.4 PMI-ACP
Which of the following task is not identified during iteration planning?
Task related to designing UI Interface Task related to attending organization level debriefing meeting Task related to user documentation update Time to attend a meeting to discuss feedback from users
Q.5 PMI-ACP
Which of the following task is not identified during iteration planning?
Code the user interface. Add new tables to database. Code the middle tier. Meet the agile consultant to discuss best practices of Iteration planning
Q.6 PMI-ACP
Team was working on iteration 3 and during the testing, tester identified bug in a story completed in iteration no 1, what should be team’s response?
Team should fix the bug in the current iteration itself, as the bugs are not acceptable in agile to remain open for long This bug is treated the same way as a user story. Fixing will prioritized into a subsequent iteration in the same way that any other user story would be. Fixing of this bug become part of iteration no 4, it must be taken in coming iteration The bug need to be logged in defect tracking system and iteration can not be closed till this bug gets closed.
Q.7 PMI-ACP
During the iteration planning meeting product owner is asking to take the view customer story in the coming iteration, on this developer remind to the product owner that we have not developed the create customer story yet, product owner still insists to have the view customer story in the coming iteration, what should agile team do about this situation ?
Agile team should make a rule that all dependant stories should be developed first, so in this case story to create customer should be developed first in the coming iteration
As the stories are being worked out of their natural order , the team needs to identify additional tasks which would have not been worked if the stories were developed in their natural order Only the GUI proto of view customer should be made so the Product owner can take feedback on proto Team should discuss the stories prioritization approach with product owner and explain why this is not possible.
Q.8 PMI-ACP
Which of the following is NOT true about Release Burn Down Chart?
The vertical axis shows the number of story points/ ideal days remaining in the project. Iterations are shown across the horizontal axis The burndown chart may show a burnup in some iteration because work has been added to the release Independent from change in scope release burn donw chart shows team’s rate of progress (velocity) Release Burn Down char is updated at every iteration end.
Q.9 PMI-ACP
Which missing information of release burn down chart gets captured by Release Burndown Bar Chart? Release burn down chart does not shows how much work is pending at the end of iteration. Release Burn down charts does not capture size change, this chart works based on initial project size only Release burndown chart doesw not show team’s velocity and the scope changes separately
Both these charts are same, no additional information is given in release burndown bar chart, only the format of display is different.
Q.10 PMI-ACP
Customer was reviewing the release Burn down Chart, and he raised a concern that he was unable to grasp completes information of broad level features, which of the following chart can help in this situation?
Parking Lot Chart Release Burn Up Chart Release Burn Down Bar Chart Iteration Burn down chart
Q.11 PMI-ACP
Agile team is working on a CRM system and they found that the story to manage customer data is too big and needs to be split in multiple stories, which of the following splitting approach is not appropriate
Story can be split based on amount of information it allows to manage, like one story only provides features to manage basic information ory can split based on operations , like the first story only allows create, other story provide feature for update Story can be spited based on splitting the cross cutting concerns , like the initial story may not include exception handling Story can be split based on type of tasks involved, like we can have only story which says design the customer page other says test the customer page
Q.12
PMI-ACP
Which of the following is true about the Release Plan?
A release plan is a plan which identified which stories need to be included in release and who will work on which story for the release duration Release plan is a plan which answers how much can be accomplished by what date. Release plan is the plan which identifies the sequence of activities need to be performed to produce the identified stories into a running product Release plan disaggregated user stories into engineering tasks
Q.13 PMI-ACP
Agile team is working on selecting iteration length. Which of the following does NOT play role in selecting iteration length?
The length of the release being worked on How long priorities can remain unchanged The amount of uncertainty Number of Pending Items in Product Backlog
Q.14 PMI-ACP
Which of the following statement talks about Feature Buffers?
The story point estimation should be done for most likely (50% probability ) and pessimistic (90% probability ) case, by this we identify the feature buffer We add more developers in the agile team to accommodate the variance in velocity
Product owner identifies the 100 story points as mandatory and then selects an additional 30% more work, identifying user stories worth an additional 30 story points. These are added as optional work to the project, the mandatory stories are planned in the initial iterations Budget is kept for adding more developers if required to meet the target dates.
Q.15 PMI-ACP
Which is true about the schedule buffer?
A schedule buffer is made by padding tasks in the schedule A schedule buffer is added to the sum of estimates from which local safety has been removed. A schedule buffer is added by adding story points with margin of safety , once applied all stories size get increased based on type of story A schedule buffer is made by increasing cost reserve for project by some percentage.
Q.16 PMI-ACP
Which of the following is NOT true about the feeding buffer?
A feeding buffer is an amount of time that prevents the late delivery by one team causing the late start of another do not add a feeding buffer if the second team will be able to start making progress with a partial deliverable from the first team In many cases, however, adding feeding buffers will extend the expected duration of a project it is always recommended to add Feeding buffer when there is dependencies between iterations and teams.
Q.17 PMI-ACP
Agile team is working on prioritizing the stories which are similar in size , the team is prioritizing the stories based on value and risks associated with these stories. Which story should be prioritized first out of following?
A story with low risk and high value A story with low risk and low value A story with high risk and high value A story with high risk and low value
Q.18 PMI-ACP
Acquiring new knowledge is important because at the start of a project, we never know everything that we’ll need to know by the end of the project. What team should do to know what will be developed?
Team should create detail feature lists of the product in the initial phase of the project and take approval on this from all stakeholders Team should identify top level needs and develop parts of the product , this product need to be shown to customers, feedback needs to be collected, opinions needs to be refined, and by this way team identified what will be developed. It may not be possible to have a detail feature list identified before the start of the project but team should make sure that they identify this before the start the development. It is not possible to identify what will be developed, that is why we need methodologies like agile, so team should not even try to know what will be developed, the flow of activity will give some product at the end.
Q.19 PMI-ACP
A training company developed solution to conduct online test, the test was very successful and company was earning good revenue from the test takers, the CEO of
this company realized that the same product should be enhanced so the same can be sold to universities, so the universities can conduct similar test for their students. This enhancement project is targeting which type of revenue
Incremental Revenue New Revenue Retained Revenue Operational Efficiencies
Q.20 PMI-ACP
A software company was facing problem in managing the service requests related to IT infrastructure, they realized with the growing manpower base this problem is going to be big in next six months, they initiated the project for a help desk system, which type of revenue this help desk system will generate for the organization
Incremental Revenue New Revenue Retained Revenue Operational Efficiencies
Q.21 PMI-ACP
Which of these is not a feature category as per Kano Model?
Threshold features Exciters features Linear features
Neutral features
Q.22 PMI-ACP
Which of the following factor is included in Karl Wiegers approach for relative weighting?
Relative Risk in developing the feature Revenue type added by the feature , Incremental , new etc Relative Penalty of the absence of the feature Deployment phase of the project
Q.23 PMI-ACP
Tom was trying to estimate amount of work team can do in the two week long iteration, Tom made list of scheduled meetings , and he also estimated the expected number of interruption one developer may face. Based on this he estimated that team can do 3 user stories. Tom shared his approach with fellow project manager Job, Job recommended to only estimate in ideal days but Tom is wondering how he will know , how many stories team will be able to deliver in two weeks time ? Which of the following Job can use to explain Tom about the elapsed time?
Ideal time estimate assume everything you need will be on hand when you start. As a Agile team we only need to focus on ideal time, elapsed time is beyond the control of agile team , only organization level methodology can calculate the elapsed time Ideal time differs from elapsed time because of the natural overhead we experience every day, the factor of natural overheads will be captured in Velocity, and team’s velocity will help us in deriving elapsed time. Sick time ,Meetings, Demonstrations, Personnel issues also impacts elapsed time
Q.24 PMI-ACP
One agile team have been estimating for two days and still they are not comfortable with what they have estimated, team wants to spend few more days to make the estimate perfect, knowing this their Agile coach said “are you aware about diminishing return on time spent estimating?”, what message coach was trying to communicate?
It’s always worth upfront effort in detailed estimation No matter how much effort you put into an estimate, an estimate is still an estimate. No amount of additional effort will make an estimate perfect Project success equates to on-time, on-budget delivery of an up-front, precisely planned set of features. Full team should be involved in estimation
Q.25 PMI-ACP
Team is discussion about the estimation scale should be used for estimating the user stories, which estimation scale would you recommend out of the following?
10, 20, 30, 50 , 80,130, 200, 400, and 1000 1, 2, 3, 4, 5, 6, 7, 8 and 9 5,7,9,10 ,12, 16, 20,25 and 50 5, 10, 20, 40 , 80, 160 , 320,640 and 1280
Q.26 PMI-ACP
You have made estimate of distance between your house and a famous Coffee shop in town and It may be twice as far as the Roots Restaurant, and you were very near to the real distance, but when you were asked to estimate the distance to moon you
were no where near the real distance. Because we are best within a single order of magnitude? What approach we should follow for estimating in agile projects?
We should estimate user stories whose sizes are within one order of magnitude for the complete project. All stories should be identified at this level so we can get good estimates. We should only estimate stories which are coming in next few iterations , rest of the stories should be left un-estimated as it is not possible to estimate epics User stories or other items that are likely to be more distant than a few iterations can be left as epics or themes. These items can be estimated in units beyond one order of magnitude We no need to estimate any story as estimate is always estimate.
Q.27 PMI-ACP
Who all estimates in planning poker?
Developer Product Manager / Owner Project Manager All
Q.28 PMI-ACP
What role Product Owner plays in planning poker ?
He has to ensure that developers are not estimating stories at the higher side The role of product owner is primarily to answers any questions that the estimators have about the story He needs to ensure that all stories are disaggregated at sufficient level so that provides team way to estimate at one order of magnitude
Product Owner has no role to play in planning poker
Q.29 PMI-ACP
Agile team is working on one story which was given 2 story points, and team expected this story to be done in 4 days, at the end of day 3 they faced a typical issue related to behaviour of one user control used in this story and because of that they end up changing the user control, as a result they end up spending 6 days for this story. What should agile team do to justify the extra time spent?
They should increase the story size from 2 points to 3 points because this story took more than estimated time even when team was working on this story on priority. Agile team should make details justification note for this and that should be sent to all stakeholders so at the end of iteration people understand the reason of delay. The team should do worry about this, they should keep the estimate same, such delay can happen and estimate is just estimate, the overall team velocity takes care of such cases. They should increase the story size of all pending stories because such issues are going to be continued.
Q.30 PMI-ACP
One agile team has been working on nine month long development project, initially all members were new to the technology and they were taking more time in developing pages, at the end of month 5 they were able to make 30% more pages per month, but they realized that their velocity is almost constant, what could be the possible reason?
With the passes of time more and more work is getting added to the project scope, and now even though they are developing fast still the left work is high , which makes velocity look constant.
As the product is getting demonstrated at iteration review they are getting quick feedbacks which is reducing the cycle time The team is estimating in ideal days, initially when they were new to the technology they were estimating more ideal days and as they became expert they started estimating less ideal days for same work The velocity is usually expected to remain constant through out the project , so this is a normal behaviour
Q.31 PMI-ACP
Which of the following is true about the agile planning ? In Agile Planning effort are high in initial iterations and they get reduced gradually as projects progress Planning is something which is not required in agile In agile planning effort follow S-Curve, efforts are less initially, high in between and again low towards the end Agile planning is spread more or less evenly across the duration of a project. Release planning sets the stage and is followed by a number of rounds of iteration planning
Q.32 PMI-ACP
Which of the following is NOT true about the agile planning ?
An agile plan is one that we are not only willing, but also eager to change Agile plan focus on managing iron triangle , Schedule , Cost and Scope, all of these three are non-negotiable Results in plans that are easily changed
The purpose of Agile planning is to find an optimal answer to the overall product development question of what to build
Q.33 PMI-ACP
Which of the following represents the weakness in traditional planning process?
It recommends usage of complex tools like Gantt Chart It recommends generating reports to identify the variance between plan and actual progress A traditionally managed project’s Gantt chart or work breakdown structure identifies the activities that will be performed and customers get no value from the completion of activities It recommends that project manager should take corrective and preventive action when variance against plan crosses the threshold units
Q.34 PMI-ACP
white tiger team was working on a project which will allow users to buy movie ticket online, the baseline schedule for this project was of 9 month duration, and end date is need to be met as it is very critical to business. The team has made detailed project plan and create WBS of all the activity, at the end of 8 months they are done with 90% of the features, but they realized that they won’t be able to finish the rest 10% in one month time, they called a review meeting and demonstrated the product to sales team, sales team said that the business needs the product in one month time and the features which are not yet developed are the one which gives the most value, many developed features were nice to have than must have. Which of the following was one of the planning error this team has done?
They should not have made WBS of project work, they should have started the project without creating the WBS
They should have made release without developing the remaining features , let sales team found about the missing features at later date They should not have called the early demo, they should have simply declared that project is delayed by one month and all features will be ready by end of 10 months. They should have prioritized the features implementation based on value it generates for business.
Q.35 PMI-ACP
Which of the following is NOT a characteristic of agile?
There are number of specific roles on the agile team Iterations are finish on time even if functionality planned in the iterations are not developed To make the project better managed agile team do up-front requirements phase followed by analysis followed by architectural design and so on Agile planning is spread across the complete project duration.
Q.36 PMI-ACP
Which of the following is NOT a recommended practice in agile
Many teams will not deliver the results of every iteration to their users Single iteration does not usually provide sufficient time to complete enough new functionality to satisfy user or customer desires It is essential to deliver feature by the end of each iteration, even if this requires extending iteration by one week. A release comprises one or more (usually more) iterations that build upon one another to complete a set of related functionality
Q.37 PMI-ACP
Which of the following statement represents agile approach to planning?
Agile planning acknowledge that the result is both somewhat unknown as well as unknowable in advance, planning is a process of setting and revising goals that lead to a longer-term objectives Agile planning gives top priority to engineering activities , activities like design and analysis should be planned in the initial iteration of the project Agile team baselines the plan for release and plants are not allowed to change before release, plan can only change once the release is made Agile planning recommends to execute many design iterations initially to achieve the High level design of complete product roadmap.
Q.38 PMI-ACP
Which of the following statement is NOT true for release planning?
Release planning considers the user stories or themes that will be developed for a new release of a product or system. Release planning occurs at the start of a project The goal of release planning is to determine an appropriate answer to the questions of scope, schedule, and resources for a project Release plan should not be updated during the project execution , it should be kept at original state so it shows the Gaps to the stakeholders
Q.39 PMI-ACP
Which of the following statement is true for iteration planning?
Based on the work accomplished in the just-finished iteration, the product owner identifies highpriority work the team should address in the new iteration Iteration planning is done on the basis of velocity assumed during the release planning , team is not allowed to change velocity assumption per iteration Iteration planning only takes release plan as an input for planning and it elaborates the release plan for the given iteration Iteration planning is very quick activity , as the release plan has already set the goals , iteration plan is just an elaboration of that which does not require much interaction and effort in doing.
Q.40 PMI-ACP
Which of the following statement is true about story points?
Story points represent the industry acceptable size of the user story, it communicates about the size of the project and make project comparable with other projects in term of size Agile has published guideline about when to give 2 points to story and when to give 8, just based on story description you can assign story point to it Story points are a unit of measure for expressing the overall size of a user story, feature, or other piece of work. The raw values assigned to story are unimportant, what matters are the relative values. We can identify the duration of the project based on size given in term of story points, no other input is required once we know the number of story points
Q.41 PMI-ACP
Agile Teams use Planning Poker for estimation. Which of the following is NOT true about Planning Poker?
It combines expert opinion, analogy, and disaggregation into an enjoyable approach to estimating that results in quick but reliable estimates.
The team for Planning Poker should not exceed more than 10 participants Participants include all of the developers on the team The highest estimate is considered the final estimate
Q.42 PMI-ACP
A story estimated at two story point actually took five days to complete. How much does it contribute to velocity when calculated at the end of the iteration?
Five Point Two Points Three Points Cannot be calculated
Q.43 PMI-ACP
During an estimating meeting three programmers are estimating a story. Individually they estimate the story at two, four and five story points. Which estimate should they use?
2 5 4 They should continue discussing the story until their estimates get closer
Q.44 PMI-ACP
What is the outcome of a Sprint Planning Meeting?
Sprint Backlog Product Road Map Product Backlog Product Vision
Q.45 PMI-ACP
How to we calculate / derive velocity in agile projects?
It is calculated by summing the number of story points assigned to each user story that the team completed during the iteration Its a fix number derived based on nature of project, factors like development tool , requirement complexity are taken in account It is calculated by summing the number of story points assigned to each user story that the developer completed during the iteration Its a fix number which is assigned at organization level and should be used for all projects
Q.46 PMI-ACP
A set of related user stories that may be combined together and treated as a single entity for either estimating or release planning is referred to as Story Theme Combined Story Epic
Q.47 PMI-ACP
Which of the following defines the splitting of a story or a feature into smaller, easier-to-estimate pieces? Decomposition Theme Disaggregation Epic
Q.48 PMI-ACP
Which of the following is NOT a Closed Story? A HR Staff can review resumes from applicants to one of her ads. A HR Staff can manage the ads she has placed A HR Staff can delete an application that is not a good match for a job. A HR Staff can change the expiration date of an ad
Q.49 PMI-ACP
During which project management phase are the product stories are written? Envision Explore Speculate Adapt
Q.50 PMI-ACP
Which of the following correctly defines the Complex Story? A User Story that comprises of multiple shorter stories
It is not a Story User story that is inherently large and cannot easily be disaggregated into a set of constituent stories. A story which is dependant on many stories for its completion
Q.51 PMI-ACP
when it is best to write Acceptance tests? As the story get identified in story writing workshop The acceptance tests for a story must be written before programming begins on that story, at the start of an iteration the customer should go through the stories and write any additional tests she can think of Once Developer is done with coding, customer should write the acceptance test cases Before the iteration demo
Q.52 PMI-ACP
Which story is NOT a good story? A Job Seeker can search for jobs. A Job Seeker can limit who can see her resume. A Recruitment company can post new job openings. The software will be written in C++.
Q.53 PMI-ACP
Which of the following is not true for User Stories? User stories emphasize verbal rather than written communication. User stories are the right size for planning.
User stories contain written requirement specification which developer can read and develop. User stories work for iterative development.
Q.54 PMI-ACP
Which story is not a good story? The user can run the system on Windows 2000 and Linux. The user can undo up to twenty commands. All charting will be done using a third-party library. The user will be prompted to save her work if she hasn't saved it for 10 minutes.
Q.55 PMI-ACP
Component story is A epic which comprises multiple shorter stories A research story A epic which can not be disaggregate A constraint story
Q.56 PMI-ACP
Which could be the best possible approach for Splitting epic Disaggregate based on development layer , say one story can cover presentation layer , other can cover business layer etc Its not advisable to split the epic Disaggregation can be done along the lines of create, edit, and delete. Epic can be divided based on people work on them, like we can have separate story for code, separate for design and separate for testing.
Q.57 PMI-ACP
What is a User Storie?
It’s a name of requirement specification document used in agile for requirement elicitation It’s a document which is used to ensure system tracability This is a document which makes customer responsible for what he has explained to development team It’s a reminder to discuss the feature
Q.58 PMI-ACP
Bill Wake’s acronym INVEST is used to define the six attribute of user Stories, what does N stands for? Non Negotiable Now Negotiable New
Q.59 PMI-ACP
When should we identify initial set of User Role? Once we have few stores developed Once we are done with one release of the product Before writing the user stories Anytime, it does not effect the quality of anything
Q.60
PMI-ACP
Which of the following is not true about user persona? Enough market and demographic research has been done so that personas chosen truly represent the product's target audience Persona is just give the name to the user role A persona should be described sufficiently that everyone on the team feels like they know the persona You should include a picture in the persona definition.
Q.61 PMI-ACP
What is the “Extreme Character” Persona? A user who expects too much from the system They are exaggerated personalities, their system needs are extremely different from the mass A user who does not care about usage instruction of the system This is a user group which is does not need attention
Q.62 PMI-ACP
Who writes the User Stories ? Project Manager Customer Developer Tester
Q.63 PMI-ACP
Who makes the good User Proxies?
User’s Manager Salespersons Development Manager Business or System Analyst
Q.64 PMI-ACP
Why we write acceptance tests? It is required by the process so the results can be mapped back to the test Its is written to catch the boundary conditions like , is system accepting dates like 30 Feb 2012 Tests are used to fill in the details of a user story, it captures the assumption made by the customer while writing the user stories It is not important to write acceptance tests
Q.65 PMI-ACP
Who specifies Acceptance Tests in an Agile Project? Programmer with the help of testers Project Manager with the help of programmer Customer and tester help them in writing it Technical Architects © All Rights Reserved 2012 | Web Exams Powered by - Softon Technologies
