By business value
By whichever means the Product Owner determines will yield the greatest value in the next release
By development cohesion
By technical necessity
The Scrum Team and any key stakeholders invited by the Product Owner
The Product Owner and key stakeholders invited by the Product Owner
The Development Team and the Product Owner
The Scrum Team and key stakeholders invited by the Product Owner
Due to the nature of an agile project, the expected time cannot be projected
Inspection, projection, transparency
Inspection, adaption, projection
Inspection, adaption, transparency
Projection, adaption, transparency
Fixed date, variable scope
Allowing both the date and the scope of the project to be variable
Fixing both the scope of the project as well as the date
Fixed scope, variable date
The Product Backlog is adapted to reflect any newly discovered changes in the direction of the product.
The stakeholders of the product receive an opportunity to provide early feedback and influence the direction of the product.
The stakeholders of the product receive an opportunity to select the items the Scrum Team will be working on in the next Sprint.
The Product Owner receives validation on the direction of the product.
Each team's individual Product Increment will be integrated into a single Product Increment in a final hardening Sprint prior to release.
Each team's individual Product Increment should be integrated into a single Product Increment before the conclusion of each Sprint.
All teams will collaborate to integrate their respective Product Increments in an integration Sprint that occurs every three Sprints.
Each team should create their own Definition of Done but make their definition visible to other teams so that differences can easily be identified and planned for.
A single Definition of Done for all work will be defined by the Integration Team. All Scrum Teams must adhere to this definition in order for their work to be integrated.
Separate Definitions of Done should be created for the server related code and the user interface related code. Teams should adhere to the Definition of Done that's most appropriate for the type of code they are working on.
All teams should create and agree on a shared Definition of Done that represents the criteria necessary for their combined Product Increment to be considered releasable.
To ensure that the Development Team holds the event and that the Sprint Burndown chart is updated accurately.
To provide an update of what the Scrum Master did yesterday, what he will be doing today, and what is in his way.
To ensure that the Development Team holds the event and adheres to the 15 minute timebox.
To record the status update of each individual team member so it can be discussed in the Sprint Review.
Two Product Backlogs should be created, one for user interface items and one for server items. Teams should pull from the Product Backlog that best represents the type of work they are doing during that Sprint.
The master Product Backlog should be split into three evenly sized child Product Backlogs. Each team should pull the top item from each child Product Backlog in turn to ensure even coverage.
Each team should create their own Product Backlog that can be managed independently of the other teams.
All teams should work from a shared Product Backlog.
4 hours for a one month Sprint, proportionately shorter for shorter Sprints.
5 minutes per Product Backlog item scheduled for review
4 hours for a 1 month Sprint, proportionately shorter for shorter Sprints
8 hours for a 1 month Sprint, proportionately shorter for shorter Sprints
A Sprint ends only once the Sprint Goal has been achieved.
Up to one calendar month.
No more than 6 weeks for a project with an annual release cycle, proportionately shorter for projects with shorter release cycles.
As long as is necessary for the team deliver all work forecasted for that Sprint.
Forming, Storming, Norming
Forming, Storming, Norming, Performing
Forming, Storming, Conforming, Performing
Forming, Norming, Storming, Performing
Rapid Application Development
너는 정확하게 대답했다.
당신이 잘못 대답했습니다.
너는 시간이 없어.
점수 또는 평점을 저장하려면 로그인하거나 등록해야합니다.
텍스트에 적합한 오디오 언어를 설정하십시오.
단어를 강조 표시하여 학습을 향상시킵니다.
로그인 할 필요없이 퀴즈, 코스 및 플래시 카드를 재생할 수 있습니다. 그러나 점수를 저장하고 퀴즈, 코스 및 플래시 카드를 만들려면 로그인해야합니다. 오디오를 재생하려면 전문 계정에 로그인해야합니다.
학습을 한 차원 높여보십시오. 프로페셔널 계정으로 업그레이드하면 질문을 큰소리로 듣고 다른 많은 혜택을 누릴 수 있습니다.
귀하가 작성한 질문이나 답변에 대한 오디오가 생성됩니다.
많은 사람들이 그들이 배운 것을 듣고 더 잘 배웁니다. 외국어 학습을 위해 우리는 18 개 이상의 언어를 지원했습니다.
지원 언어로는 덴마크어, 네덜란드어, 영어, 프랑스어, 독일어, 아이슬란드 어, 이탈리아어, 일본어, 한국어, 노르웨이어, 폴란드어, 포르투갈어, 루마니아어, 러시아어, 스페인어, 스웨덴어, 터키어, 웨일스 어 등이 있습니다.
또한 단어를 소리내어 읽음으로써 자동 단어 단위 강조 기능을 지원합니다.
Apple App Store에서 볼 Topgrade 응용 프로그램을 선택하십시오.
Google Play에서 볼 수있는 Topgrade 앱을 선택합니다.