Well-organized, respected by the team, extremely technically savvy.
Well-organized, respected by the team, respected by the broader organization.
Strong Project Management discipline, extremely technically savvy, respected by the team.
Well-organized, strong Project Management discipline, respected by the team.
To allow the Product Owner to validate a recent product decision.
To reduce the level of unknown of an upcoming Product Backlog item.
To implement to a particularly risky Product Backlog item.
To explore a technology the Development Team has shown a recent interest in.
Offer to meet with the Product Owner each morning following the Daily Scrum to provide an in-person summary of the team's plans for the day.
Ask the Development Team to conduct their Daily Scrum in the organization's instant messaging client so the Product Owner can review each morning's message thread at her convenience.
Invite the Product Owner to occasionally attend the Daily Scrum as an observer.
Invite the Product Owner to regularly attend the Daily Scrum as a participant providing her own status update alongside the rest of the Development Team.
As many members as necessary to deliver a Product Increment at the completion of the Sprint
5 to 7 members
3 to 9 members
5 plus or minus 2 members
All teams should work from a shared Sprint Backlog that has been filtered to allow each team to only view the items that are relevant to that team.
All teams should work from a shared Sprint Backlog.
Each team should create their own Sprint Backlog from a Product Backlog shared across all teams.
4 hours for a one month Sprint, proportionately shorter for shorter Sprints.
As long as is necessary to forecast the work expected to deliver the Sprint Goal.
8 hours for a one month Sprint, proportionately shorter for shorter Sprints.
Sprint Planning continues until all members of the Development Team have selected an appropriate amount of work.
The Scrum Team
The organization sponsoring the Scrum Team
The Product Owner
The most appropriate approach is clearly stated in the Scrum Guide
Cumulative flow diagram
Release burn-up chart
The Development Team
The Scrum Master, the Product Owner, and the Development Team
The Scrum Master, the Development Team, and any stakeholders who have a vested interest in the current work
The Scrum Master and the Development Team
As much as is required to ensure the items selected for the next Sprint are adequately prepared
No more than 10% of the team's capacity
2 hours for a 1 month Sprint, proportionately less for shorter Sprints
A description and an estimate of complexity.
A description, an order, an estimate of complexity, and an estimate of business value.
A description, an order, and an estimate of complexity.
The members of the Scrum Team and each of their immediate managers
The Scrum Team and any key stakeholders invited by the Product Owner
The Development Team and Scrum Master
The Scrum Master and Product Owner of each Scrum Team.
All members of every Scrum Team.
The Product Owner of each Scrum Team.
The Scrum Master of each Scrum Team.
It gives guidance on what types of engineering practices a team may find valuable, but leaves it up to each team to select the practices most helpful for their specific situation.
It prescribes a specific set of engineering practices which must be adhered to by all teams.
It prescribes no specific engineering practices.
너는 정확하게 대답했다.
당신이 잘못 대답했습니다.
너는 시간이 없어.
점수 또는 평점을 저장하려면 로그인하거나 등록해야합니다.
텍스트에 적합한 오디오 언어를 설정하십시오.
단어를 강조 표시하여 학습을 향상시킵니다.
로그인 할 필요없이 퀴즈, 코스 및 플래시 카드를 재생할 수 있습니다. 그러나 점수를 저장하고 퀴즈, 코스 및 플래시 카드를 만들려면 로그인해야합니다. 오디오를 재생하려면 전문 계정에 로그인해야합니다.
학습을 한 차원 높여보십시오. 프로페셔널 계정으로 업그레이드하면 질문을 큰소리로 듣고 다른 많은 혜택을 누릴 수 있습니다.
귀하가 작성한 질문이나 답변에 대한 오디오가 생성됩니다.
많은 사람들이 그들이 배운 것을 듣고 더 잘 배웁니다. 외국어 학습을 위해 우리는 18 개 이상의 언어를 지원했습니다.
지원 언어로는 덴마크어, 네덜란드어, 영어, 프랑스어, 독일어, 아이슬란드 어, 이탈리아어, 일본어, 한국어, 노르웨이어, 폴란드어, 포르투갈어, 루마니아어, 러시아어, 스페인어, 스웨덴어, 터키어, 웨일스 어 등이 있습니다.
또한 단어를 소리내어 읽음으로써 자동 단어 단위 강조 기능을 지원합니다.
Apple App Store에서 볼 Topgrade 응용 프로그램을 선택하십시오.
Google Play에서 볼 수있는 Topgrade 앱을 선택합니다.