Emperical Process Control Flashcards
Scrum
Decisions are based on observation & experimentation rather detailed upfront planning.
What are the 3 main ideas of Emperical Process Control?
- Transparency
- Inspection
- Adaptation
What does Transparency do?
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.
Sprint Planning Meetings
Scrum team estimates effort needed to deliver top priority user stories for completion in the Sprint
Sprint Backlog
Used to list all tasks associated with committed User stories to be executed by Scrum Teaam in current Sprint
Sprint Review Meetings
Conducted during Demonstrate & Validate Sprint process, in which Scrum Team demonstrates potentially shippable Sprint Deliverables to Product Owner & Business Stakeholders
Retrospect Sprint Meetings
Conducted after Sprint Review Meetings on final day of Sprint, during which the Scrum Team discusses improvement opportunities for future Sprints
Release Planning Meeting
AKA Session is to enable Scrum Team to have an overview of planned releases & delivery schedule for product they are developing
Layers of Inspection
- Scrumboard
- Frequent Feedback
- Final Inspection
Frequent Feedback
- Develop Epics
- Create prioritized product backlog
- Conduct release planning
Final Inspection
Demonstrate & Validate Sprint
Adaptation
Happens as the Scrum Team & Stakeholders learn through transparency & inspection & then adapt by making improvements in the work they are doing.
Adaptation Factors
- Daily Standup meetings
- Constant requests
- Change requests
- Scrum Guidance Body
- Retrospect Sprint meetings
- Retrospect Release meetings
Daily Standup Meetings
- 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
Constant Risk Identification
- Performed & iterated throughout the project
- Identified Risks become inputs to multiple Scrum processes
Change Requests
- Discusses & approved during:
- Developed Epics
- Create Prioritized Product Backlog
Scrum Guidance Body
- 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
Retrospect Sprint Meetings
- Agreed actionable improvements are determined based on the outputs from the Demonstrate & validate Sprint process
- These adaptations are integrated into later sprints and projects
Retrospect Release Meeting
- 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
Challenges in Waterfall Project Mangaement
- 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
Sequential Approach
Incorrect inputs at initial stages translate to unsatifactory outputs towards final delivery.
