Emperical Process Control

Question 1

Scrum

Answer 1

Decisions are based on observation & experimentation rather detailed upfront planning.

Question 2

What are the 3 main ideas of Emperical Process Control?

Answer 2

• Transparency
• Inspection
• Adaptation

Question 3

What does Transparency do?

Answer 3

Allows all facets of any Scrum process to be observed by anyone
- Promotes an easy & transparent flow of info throughout the organization & creates an open work culture.

Question 4

Sprint Planning Meetings

Answer 4

Scrum team estimates effort needed to deliver top priority user stories for completion in the Sprint

Question 5

Sprint Backlog

Answer 5

Used to list all tasks associated with committed User stories to be executed by Scrum Teaam in current Sprint

Question 6

Sprint Review Meetings

Answer 6

Conducted during Demonstrate & Validate Sprint process, in which Scrum Team demonstrates potentially shippable Sprint Deliverables to Product Owner & Business Stakeholders

Question 7

Retrospect Sprint Meetings

Answer 7

Conducted after Sprint Review Meetings on final day of Sprint, during which the Scrum Team discusses improvement opportunities for future Sprints

Question 8

Release Planning Meeting

Answer 8

AKA Session is to enable Scrum Team to have an overview of planned releases & delivery schedule for product they are developing

Question 9

Layers of Inspection

Answer 9

• Scrumboard
• Frequent Feedback
• Final Inspection

Question 10

Frequent Feedback

Answer 10

• Develop Epics
• Create prioritized product backlog
• Conduct release planning

Question 11

Final Inspection

Answer 11

Demonstrate & Validate Sprint

Question 12

Adaptation

Answer 12

Happens as the Scrum Team & Stakeholders learn through transparency & inspection & then adapt by making improvements in the work they are doing.

Question 13

Adaptation Factors

Answer 13

• Daily Standup meetings
• Constant requests
• Change requests
• Scrum Guidance Body
• Retrospect Sprint meetings
• Retrospect Release meetings

Question 14

Daily Standup Meetings

Answer 14

• Scrum team members discuss impediments to completing their tasks
• After the meeting, the Scrum master coordinate help from other teaam members
• More experienced members, mentor those with less experience in knowledge of project or tech
• When the needed resource does not reside within team, the Scrum master will acquire it externally

Question 15

Constant Risk Identification

Answer 15

• Performed & iterated throughout the project
• Identified Risks become inputs to multiple Scrum processes

Question 16

Change Requests

Answer 16

• Discusses & approved during:
  
  • Developed Epics
  • Create Prioritized Product Backlog

Question 17

Scrum Guidance Body

Answer 17

• Interacts with Scrum team members during the:
  
  • Create user stories
  • Estimate Tasks
  • Create Deliverables
  • Groom prioritized product backlog processes
• Guidance and also provide expertise as required for the team to adapt to necessary changes & challenges

Question 18

Retrospect Sprint Meetings

Answer 18

• Agreed actionable improvements are determined based on the outputs from the Demonstrate & validate Sprint process
• These adaptations are integrated into later sprints and projects

Question 19

Retrospect Release Meeting

Answer 19

• Participants document lessons learned & perform reviews looking for opportunities to improve processes and address inefficiencies
• Within the processes, practices, and activities of Scrum are numerous opportunities for adapting to changing requirements & business realities
• Sequential Approach
• Considerable planning needs to be done well in advance of production
• Customer generally does not review product components until near the end of the A phase
• Presents huge risk to project’s success
• Customer’s interpretation/understanding of the finished product may be very different from what was actually understood & produced by the team

Question 20

Challenges in Waterfall Project Mangaement

Answer 20

• How the customer explained it
• How project leaders understood it
• How engineers designed it
• How construction built it
• How the business consultant described it
• How the project was documented
• What was operational
• How the customer was billed
• How it was supported
• What the customer really needed

Question 21

Sequential Approach

Answer 21

Incorrect inputs at initial stages translate to unsatifactory outputs towards final delivery.