chapter 5.2.1 Flashcards
what are the steps to plan project iterations?
-define scope
-create prioritized backlog (all features/requirements)
-define iteration length
-select work for iteration
-breakdown work into smaller units
-estimate effort required
-plan iteration
-execute iteration
-review/retrospect iteration
what are epics?
-highest level of logical units
-often describe large complex features that require significant effort
-broken down into user stories to facilitate iterative development
what are user stories?
-common method for breaking down epics
-define requirements from end user perspective
-represent specific feature or function
-small enough to be completed in one iteration
-typically include acceptance criteria, which define when a story is considered complete
what are tasks?
-smallest unit of work in an iteration
-represent individual activities to deliver user story
-estimated in hours, typically assigned to specific team member
what are the pros of using iterations in agile project planning?
-early and continuous delivery of value (delivering incrementally allows for feedback, room for adjustment)
-adaptability and flexibility
-improved visibility and predictability (progress measured at end of each iteration)
-continuous improvement
-increased collaboration
what are the cons of using iterations in agile framework?
-increased planning overhead (require more planning and coordination than traditional. can increase administrative burden on project)
-risk of scope creep
-dependency management (require effective mgmt of dependencies between work items)
-inflexibility (if work items are not well defined or estimated. lead to delays and missed deadlines)
what is the WBS typically replaced with in agile framework? how does it work?
-product backlog
-prioritized list of features or user stories that describe functionality product should have
what are some inputs for defining and refining scope in an adaptive project?
-stakeholder requirements
-project objectives
-business case
-constraints
-lessons learned
-change requests
-project team expertise
name some reasons why adaptive project tracking is important?
-flexibility (allows for greater flexibility in managing project)
-focus on value (focus on delivering value to stakeholders as quickly as possible)
-continuous improvement (encourages this through frequent retrospectives/willing to adjust approach)
-collaboration (promotes this between team members and stakeholders)
-early detection of issues (frequent checkpoints and opportunities for feedback)
what are story points?
-in agile, used as relative estimation tool rather than absolute measurement of time/effort
-allows for greater flexibility/adaptability
-measure complexity, effort, and uncertainty of a task
-story points are assigned to user stories in relation to size of user story
-story points are combined to determine velocity that can be delivered during an iteration
-during sprint, team tracks progress of each user story or task by updating status and number of story points completed.
-helps id any delays/bottlenecks in sprint
what is velocity?
-rate at which team completes tasks in an agile project
-measured by number of story points completed in sprint or iteration
-if velocity does not match expected number, then review is done to id the cause
-may ID user stories were not defined well enough
-progress to completion of story points within iteration usually shown on velocity chart
what is the kanban board?
-visual tool used to manage work and workflow
-allows team to see status/id any bottlenecks
-emphasis on JIT/limiting WIP
what is burnup? what is burndown?
-visual tools used to track progress against set of goals or targets, typically toward a release
-burnup shows work completed over time
-ideal for any time you want to show the accumulation of something rather than the completion of an item
-use for sprint backlog, product backlog, or tracking the item
-burndown shows remaining work to be completed
-burndown is used when you have a long list of items, such as features in product backlog, and by completing each item, the list is “burned down”
what is a cumulative flow diagram?
-stack diagram showing number of tasks in each kanban diagram
-example: software development project can have a Kanban board with four columns (backlog development, testing, deployed) chart will show how many items are in each column of the kanban board
-what is earned value analysis? what is needed to complete it?
-pm technique used to track progress of project and assess performance in schedule/cost
-provides insight into efficiency and effectiveness of project
-used as tool to monitor and control progress of work within iterations or sprints
-actual cost of release (anticipated cost per release, not just cost for entire project. predict by cost of each story point in iteration and velocity of team)
-estimated product backlog (represents remaining project scope)
-product release plan (when increments will be released and expected number of iterations)
-assumed velocity (number of user story points team will do per iteration)
what are the base formulas for agile EVA? not the math, just the actual variables?
-PV (planned value)
-EV (Earned value)
-AC (Actual Cost)
-BAC (budget at completion)
documenting project controls for an adaptive project typically includes what but is not limited to?
-define project objectives and goals (SMART: specific, measurable, achievable, relevant, time bound)
-develop project plan (flexible and responsive to changing requirements)
-define project roles and responsibilities (resource mgmt plan outlines how resources will be managed and allocated)
-document change control
-establish communication protocols
-document project progress
-conduct regular project reviews
what are some common artifacts that are used in an adaptive project?
-product backlog
-sprint backlog
-user stories
-burndown chart
-definition of done (DOD)(what constitutes completed task or feature)
-Minimum Viable Product (MVP)
-Minimum business increment
-Retrospective
-Continuous integration/continuous deployment (CI/CD) pipeline (series of automated processes to build, test, and deploy software updates. used to ensure changes are delivered quickly)
-agile release plan (outlines release schedule for project. roadmap for team and stakeholders)
-velocity chart (graph to track progress of team work. shows amount of work completed over period of time, usually a sprint. vertical axis=work completed, usually in story points. horizontal axis=time
what is a minimum business increment (MBI)
-smallest possible deliverable unit
-provides some value to customer
-independently deployed, tested, and validated
-often break down larger features or projects into smaller pieces completed and delivered more effeciently
define an adaptive plan? what are its components?
-adjust to changing circumstances or new info
-goals and objectives (SMART)
-key performance indicators (KPI)
-risk management
-resource allocation
-communication plan
-evaluation and feedback mechanisms
what three common actions do adaptive methodologies share (based on agile manifesto)
-TIA
-transparency (requires trust, agreement, and open communication)
-inspection (review artifacts, progress, and quality of work)
-adaptation (when issues arise)
what are the key aspects of Lean that are incorporated in various agile frameworks?
-delivering value
-respect for people
-minimizing waste
-being transparent
-adapting to change
-continuously improving
what is the acronym SAFe
Scaled Agile Framework
what is the most well known agile framework?
Scrum