Domain V: Adaptive planning
Adaptive planning key knowledge are discussed below,
Time, cost and functionality are key factors for traditional project.
In agile project, resources, time and functionality are the key factors for project management.
Agile project phases are envisioning, speculating, exploring, adaption and closing
Agile project are non plan-driven. Initial planning, it has the balance between balancing risks and project. Re-planning and midcourse with good knowledge are executed from project. In rolling wave planning, plans are broken down into different stages. Progressive elaboration explains about product and requirement clearer as the time rolls.
Agile planning stages are
• Product vision is created by product owner states the reason why, what and how the product supports company strategy.
• Project roadmap document created by product owner explains about high level product requirement and timeline deliverables. Story maps are used to represent sequences of backbone, walking skeleton and optional features released overtime.
• Release plan describing high-level timeline for product releases.
• Sprint plan/Iteration plan describes sprint goal, tasks and requirement on the whole. Iteration 0 is the initial requirements into backlog. Iteration H represents hardening iteration to test and prepare the launch software.
• Daily stand-up/Daily scrum is s meeting plan attended by project team stakeholders to discuss about project completion, task given for that day and roadblocks.
• Sprint review is the type of meeting scheduled at the end of each sprint for demonstration of working product or increment for feedback or acceptance.
• Sprint retrospective scheduled at the end of each sprint by team members to improve product and process to enhance efficiency and effectively.
Agile planning artifacts and meetings
Product vision and roadmap discuss about purpose and cost of the project. Personas are the tool used for collection and testing by product owners and users. Wireframes is the graphical representation of requirements fulfills the requirement documentation. Release plan responsible by customer to help the project team changes depending on actual progress or change requests.
Agile planning terms
• Agile theme represents iteration function grouped to be done to maintain focus on them. Epic story explains large block functionality for estimation and implementation. User story describes the requirements in real worlds which is independent and negotiable. Story maps are the overview of user stories to fulfill user story, tasks for self-organization.
• Agile modeling refers various modeling techniques commonly used on agile projects. Agile modeling is the practice-based method for effective modeling and documentation.
Adaption changes to the project, product and processes to deliver best customer value and special circumstances of project environment. Agile framework and process are tailored for next iteration in the project. Process tailoring is to understand better values of standard method and relationship between different processes. Shu-Ha-Ri model is followed for agile adaption.
Agile adaption terms
• Velocity is the unit of measure the speed of the team.
• Cycle time is the amount of time for feature from start to finish the project.
• Burn rate is the measure of amount of cost estimated over given period of time.
• Escaped defects are not discovered by team but the customer identifies the defects
• Agile smells are the term used to depicts “symptoms of a problem”
• Verification and validation ensures functionality meets requirements described and deliverable work s intended.
• Refactoring is the technique used for project programming to review codes and re-organize.
• Kaizen is the Japanese method where the process and project are continuously improved for better value delivery.
Kaizen (New 2015)
Kaizen is defined as the continuous improvement practiced for organization’s long-term strategy. Kaizen board show the current position of the task done within this iteration. It helps to know how the project flows and the team is self-directing.
Agile project artifacts
• Product backlog is the process where prioritized list of all features for the projects are used. Grooming is the method to add items based on new user and delete old stories. Iteration backlog is responsible by the team where tasks are allotted by self-organizing teams.
• Burn-down charts shows task remaining in the current project over project life. Kanban board shows the progress of task through project process. Cumulative flow diagram depicts the status of the project process, where widen band shows agile smells in the particular process.
• Little’s law is the cycle time is proportionally to the size of queue. Large WIP depicts lengthy cycle time and it the way to improve efficiency to limit WIP.
• Agile sizing and estimation
• Relative sizing is used to precise unit like money and time in traditional project management for agile project estimation.
• Ideal time is the unit for measuring agile task without any distractions
• Wideband Delphi estimating is the Delphi method to understand the scope of task and estimate user stories
• Planning poker is used to estimate story points for user story.
• Affinity estimating is the method to assign user stories for estimation of story point for user stories.
Control limits (New 2015)
Control limits are also called as natural process limits which is drawn on statistical control chart at the distance of +_ 3 SD of plotted statistic from statistic’s mean used in control charts.
Agile Adaptive planning