Technical Program Management Flashcards
Terms and concepts associated with Agile, Scrum, and program management
Agile Methodology
(Basic) A project management methodology characterized by the division of tasks into short phases of work and frequent reassessment and adaptation of plans. (Advanced) Agile methodology focuses on iterative development, where requirements and solutions evolve through collaboration. It’s well-suited for projects with rapidly changing or highly emergent requirements. Agile increases adaptability and customer satisfaction.
Scrum
(Basic) An Agile framework for developing, delivering, and sustaining complex products, with an emphasis on software development. (Advanced) Scrum is implemented in short ‘sprints’ or iterations to allow for rapid feedback and continuous improvement. It uses roles like Scrum Master and Product Owner and ceremonies like daily stand-ups and sprint reviews. Scrum enhances team productivity and responsiveness to changing project requirements.
Kanban
(Basic) A visual workflow management method used to visualize work, limit work-in-progress, and maximize efficiency (or flow). (Advanced) Kanban boards visually display work at various stages using cards and columns. It helps teams to manage work by balancing demands with available capacity and improving the handling of bottlenecks. Kanban is used widely in software development and manufacturing.
Waterfall Model
(Basic) A sequential (non-iterative) project management methodology where progress flows steadily downwards through phases. (Advanced) The Waterfall Model is a linear and sequential approach where each phase must be completed before the next begins. It’s best for projects with well-defined requirements and low uncertainty. Its structured nature makes it easy to understand and manage.
Lean Methodology
(Basic) A project management philosophy emphasizing the minimization of waste within a manufacturing system without sacrificing productivity. (Advanced) Lean methodology aims to deliver maximum value while minimizing waste. It involves continuous improvement, optimizing processes, and eliminating non-value-adding activities. Lean is popular in manufacturing but also applied in software development.
Six Sigma
(Basic) A set of techniques and tools for process improvement, focusing on reducing process variation and defects. (Advanced) Six Sigma aims for near perfection in performance. The methodology uses statistical methods for reducing defects and improving quality. It’s often combined with Lean principles (Lean Six Sigma) for efficiency and quality improvement.
Risk Management
(Basic) The process of identifying, assessing, and controlling threats to an organization’s capital and earnings. (Advanced) Risk management involves analyzing potential project risks and developing strategies to manage them. It’s crucial for minimizing potential negative impacts. Effective risk management contributes to the smooth execution and success of projects.
Stakeholder Management
(Basic) The process by which you organize, monitor and improve your relationships with your stakeholders. (Advanced) Stakeholder management involves identifying and analyzing stakeholder needs and expectations. It’s key in maintaining good relationships and ensuring project success. Regular communication and engagement are essential components.
Resource Allocation
(Basic) The process of assigning and managing assets in a manner that supports an organization’s strategic goals. (Advanced) Resource allocation involves distributing the right resources in the right amount to various projects. Effective allocation is crucial for project efficiency and success. It ensures that resources are used optimally and aligned with business objectives.
Critical Path Method (CPM)
(Basic) A project modeling technique used to estimate the minimum project duration and determine the amount of schedule flexibility. (Advanced) CPM identifies the longest stretch of dependent activities and measures the time required to complete them from start to finish. It’s used to predict project duration and manage deadlines. Understanding the critical path helps in prioritizing tasks for on-time project completion.
Types of Agile Frameworks
(Basic) Scrum, Lean, Kanban, Extreme Programming (Advanced) Different Agile frameworks include Scrum (iterative work in sprints), Lean (eliminating waste), Kanban (visual workflow management), and Extreme Programming (focusing on software quality and responsive to changing customer requirements).
Tools for Project Management
(Basic) Trello, Jira, Asana, Smartsheets, Monday (Advanced) These tools help in managing projects efficiently. Trello offers a card-based task management system. Jira is geared towards agile project management. Asana allows task assignments and tracking. Smartsheets provides spreadsheet-like project management, and Monday.com offers customizable workflow management.
Why is the Agile Framework Preferred to Waterfall by Technology Companies?
(Basic) Agile’s flexibility and adaptability to change. (Advanced) Agile is preferred due to its iterative nature, allowing for flexibility and adaptability to change, which is crucial in the fast-paced tech industry. It facilitates continuous feedback and incremental development, as opposed to Waterfall’s rigid linear approach.
Four Values of the Agile Manifesto
(Basic) Individuals and interactions, Working software, Customer collaboration, Responding to change (Advanced) The Agile Manifesto values individuals and interactions over processes and tools, working software over comprehensive documentation, customer collaboration over contract negotiation, and responding to change over following a plan.
DevOps
(Basic) A set of practices that combines software development and IT operations.
(Advanced) DevOps is about unifying development and operations teams to automate and standardize processes for infrastructure deployment. It’s vital for improving deployment frequency and ensuring high software quality.
Burndown Chart
(Basic) A graphical representation of work left to do versus time.
(Advanced) The burndown chart is a key Agile tool used to track the progress of work during a sprint. It helps teams visualize remaining work and supports sprint planning and review.
Retrospective Meeting
(Basic) A meeting to discuss successes and improvements after a project phase.
(Advanced) Held at the end of each sprint, it allows teams to reflect on their processes and identify areas for improvement, fostering a culture of continuous improvement.
Product Backlog
(Basic) The list of all desired work on the project.
(Advanced) The product backlog is a prioritized list of features and changes that provide guidance on what the development team should work on next, serving as the foundation of project planning in Agile.
Sprint Backlog
(Basic) A list of tasks to be completed during the Scrum sprint.
(Advanced) The sprint backlog is a detailed plan for development during an Agile sprint, often featuring user stories, tasks, and acceptance criteria for guidance.
Epic
(Basic) A large body of work in Agile frameworks that can be broken into smaller stories.
(Advanced) Epics are used to manage and track large, complex features that will be developed over multiple sprints, helping teams structure and plan extensive development work.
Velocity
(Basic) A measure of the amount of work a team can handle in a single sprint.
(Advanced) This metric is used to predict how quickly a team can work through the items in the product backlog, aiding in future sprint planning and scope management.
Gantt Chart
(Basic) A type of bar chart that illustrates a project schedule.
(Advanced) Gantt charts are instrumental in project management for outlining the project timeline, phases, milestones, and dependencies between tasks.
Scope Creep
(Basic) Uncontrolled changes or continuous growth in a project’s scope.
(Advanced) Scope creep can disrupt project timelines and budgets, making it essential for project managers to implement strong scope control measures.
Milestone
(Basic) A significant point or event in a project timeline.
(Advanced) Milestones are used to signify important achievements and transitions in project phases, serving as checkpoints that help gauge project progress.
Monte Carlo Simulation
(Basic) A mathematical technique that allows for risk and uncertainty in prediction and forecasting models. (Advanced) Monte Carlo Simulation uses random sampling and statistical modeling to estimate mathematical functions and mimic the operation of complex systems. It’s commonly used in project management for risk quantification and to predict project outcomes.
Earned Value Management (EVM)
(Basic) A project management technique for measuring project performance and progress in an objective manner. (Advanced) EVM combines measurements of project scope, schedule, and cost in a single integrated system. It provides accurate forecasts of project performance problems, which is essential for project planning and execution.
Stakeholder Analysis
(Basic) A process of systematically gathering and analyzing qualitative information to determine whose interests should be considered throughout the project. (Advanced) Stakeholder Analysis is crucial for identifying the interests, influence, and impact of various stakeholders. It helps in developing effective strategies for stakeholder engagement and communication.
Scope Statement
(Basic) A document that defines the project’s scope and establishes what will and will not be included in the project deliverables. (Advanced) The scope statement provides a detailed account of the project’s objectives, deliverables, and the work needed to complete the deliverables. It’s a critical component of the project management plan to avoid scope creep.
Quality Assurance (QA)
(Basic) A way of preventing mistakes and defects in manufactured products and avoiding problems when delivering solutions or services to customers. (Advanced) QA is a proactive process to ensure that the quality requirements will be fulfilled. It’s the part of quality management focused on providing confidence that quality requirements will be fulfilled in the product development.
RACI Matrix
(Basic) A responsibility assignment chart that maps out every task, milestone, or key decision involved in completing a project and assigns which roles are Responsible, Accountable, Consulted, and Informed. (Advanced) The RACI Matrix clarifies roles and responsibilities in cross-functional or departmental projects and processes. It helps to ensure that everyone knows what they should be doing and how their role contributes to the project success.
Project Sponsor
(Basic) A person or group who provides resources and support for the project and is accountable for enabling success. (Advanced) The project sponsor champions the project at the highest level, helping to secure funding, resolve issues, and provide overall guidance. They play a pivotal role in project governance.
Cost-Benefit Analysis
(Basic) A process businesses use to analyze decisions – the benefits of a given situation or business-related action are summed and then the costs associated with taking that action are subtracted. (Advanced) Cost-Benefit Analysis is a systematic approach to estimate the strengths and weaknesses of alternatives. It helps to evaluate options and make the best decision based on the benefits and savings that result from each option.
Iteration Retrospective
(Basic) An agile practice for inspecting and adapting the iteration process. (Advanced) Iteration Retrospective is a meeting held after a development iteration in Agile methodologies. The team reflects on the past iteration, discussing what went well and what could be improved for the next iteration.
Project Governance
(Basic) The framework for how project decisions are made. (Advanced) Project Governance involves the strategic framework for understanding, decision-making, and accountability in projects. It ensures that projects are aligned with the organization’s objectives and are delivered effectively.
Agile Manifesto Principles
(Basic) Twelve guiding principles for Agile software development that support the Agile Manifesto. (Advanced) The principles behind the Agile Manifesto include customer satisfaction through early and continuous delivery, welcoming changing requirements, frequent delivery, and collaboration between business stakeholders and developers.
Product Vision Statement
(Basic) A declarative statement that articulates the goals and aspirations of a product. (Advanced) The product vision statement provides a long-term direction for the product and sets the stage for product decision-making. It is essential for guiding the team and aligning stakeholders with the product’s intended direction.
Cross-Functional Teams
(Basic) Teams composed of people with different functional expertise working toward a common goal. (Advanced) Cross-functional teams are a hallmark of Agile and are critical for enhancing collaboration and innovation, as they bring together diverse perspectives and skills to solve complex problems.
Business Case
(Basic) A document that justifies the start of a project, including the expected benefits, risks, costs, and revenue. (Advanced) The business case provides the reasoning for initiating a project or task. It is a critical document during the project initiation phase and is reviewed throughout the project lifecycle to ensure the project remains aligned with business objectives.
Incremental Delivery
(Basic) A software development strategy where the product is designed, implemented, and tested incrementally until the product is finished. (Advanced) Incremental delivery allows for partial delivery of the product to users as soon as each functionality is complete. This strategy can provide early partial benefits while the product is still in the development process.
Agile Coaching
(Basic) The practice of guiding teams and organizations in the development and execution of Agile practices. (Advanced) Agile coaching is vital for teams transitioning to Agile methodologies. Coaches help teams understand Agile principles and practices, facilitate Agile ceremonies, and assist in the transformation of team dynamics.
Continuous Integration (CI)
(Basic) A development practice where developers integrate code into a shared repository several times a day. (Advanced) Continuous Integration is a key DevOps practice, aimed at detecting issues early by frequently merging code changes into a central repository where builds and tests are executed.
Continuous Deployment (CD)
(Basic) A software release process that uses automated testing to validate if changes to a codebase are correct and stable for immediate deployment to a production environment. (Advanced) Continuous Deployment goes one step beyond continuous integration by automatically releasing the code changes after the build and test phases pass. This practice allows for high velocity in delivering features, improvements, and fixes to customers.
Timeboxing
(Basic) A time management technique that involves allocating a fixed, maximum unit of time for an activity. (Advanced) Timeboxing is used in Agile to limit the amount of time spent on a particular activity, encouraging focus and efficiency. It is commonly used for sprints, meetings, and specific task completions.
Sprint Review
(Basic) A meeting at the end of a sprint where the team demonstrates what they shipped in the sprint. (Advanced) The sprint review is an informal meeting in the Scrum framework where the team presents their increment to stakeholders to gather feedback. It marks the end of the sprint and is essential for transparency and stakeholder engagement.
Scaled Agile Framework (SAFe)
(Basic) An agile software development framework designed for scaling agile practices to larger organizations. (Advanced) SAFe provides a structure for scaling agile across the enterprise, aligning teams under common goals. It’s important for complex projects that require coordination across multiple agile teams.
Product Increment
(Basic) The sum of all product backlog items completed during a sprint and all previous sprints. (Advanced) The product increment is a step towards the final product goal, reflecting the progress made in a sprint. It must be in a usable condition regardless of whether the Product Owner decides to release it.
WIP Limits
(Basic) Constraints placed on the number of work items in the ‘in-progress’ state. (Advanced) WIP Limits are used in Kanban to ensure that teams focus on finishing work at hand before starting new tasks, which helps to improve flow and reduce cycle time.
MoSCoW Method
(Basic) A prioritization technique used to reach a common understanding with stakeholders on the importance they place on the delivery of each requirement. (Advanced) MoSCoW stands for Must have, Should have, Could have, and Won’t have. It’s used to prioritize requirements by providing a framework for stakeholders to categorize them based on their necessity.
Project Handover
(Basic) The process of transferring project control from one team to another. (Advanced) A project handover ensures that all the relevant information about the project is passed on to a new team or client after a project or phase is completed. It’s essential for the continuity and success of ongoing operations.
Change Control Board (CCB)
(Basic) A group of stakeholders responsible for reviewing, evaluating, approving, delaying, or rejecting changes to the project. (Advanced) The CCB is an integral part of the change management process and ensures that changes are made with oversight and alignment with project goals.
