Uncertainty in agile projects
•
1 like•777 views
This document discusses the importance of accounting for uncertainty in agile projects. It provides examples of sources of uncertainty like changing requirements, over or under estimation of tasks, and lack of technical knowledge. It recommends involving customers throughout the project, estimating uncertainty without being precise, and allocating time and resources to address defects and non-iteration work as a way to mitigate uncertainty. Estimating uncertainty helps deliver promised functionality on time and builds customer trust.
Report
Share
Report
Share
![Agile is a two way effort ,[object Object]](data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7)
Recommended
Predictability at Axial
Given at Axial HQ for the New York chapter of Venwise, this talk details how Axial approaches building products predictably through a combination of focus, objectives, prioritization and forecasting. We call it stack.
Check out more of what we're building over at: axialcorps.com
Batting Averages and Slugging %s
This document discusses alternatives to using team velocity as a metric for software development teams. It proposes measuring the frequency of delivering value to users through high value releases, prioritizing work that provides the best value for effort, and recognizing individuals who consistently deliver high value features. Specific metrics proposed include an L value batting average measuring weeks with high value releases, slugging percentage measuring value delivered, and a silver slugger award for top performers.
Finance Presentation
The document discusses accounting and finance processes and systems at WGUK. It identifies several key issues: data accuracy problems across systems from meter points to invoices; a lack of validation processes between integrated systems; and a need for proper testing before new systems go live. It recommends: understanding problems fully before taking action; introducing validation and testing rigorously; focusing initially on fixing meter point and data accuracy issues; training staff; and establishing accurate budgets and processes for long-term improvement.
Getting To Product Market Fit Quickly
This 1-hour workshop marries the best practices from product strategy with those of fast and efficient technology teamwork and delivery. You’ll learn how to get your product organization working as a single cohesive, well-oiled machine to deliver the right product to market as quickly as possible. We will cover how to use both qualitative and quantitative measures to ensure that your product is solving the right problem; how to optimize and streamline the way your team designs, builds, and deploys software to your customers; and, how to beat the competition in strategy and execution.
Range estimation in Scrum
Presentation by OpenSource Connections consultant Arin Sime at Agile2010 conference on how to incorporate range estimation techniques into Scrum.
Operational Performance Management PowerPoint Presentation Slides
Operational performance management is a key factor in successfully achieving the business target. Analyze the performance of your business with our content ready Operational Performance Management PowerPoint Presentation Slides. Evaluate business activities to meet organizational goals with the help of business operations management PPT slides. Assess regularly the performance of your business. you can also use performance measures PowerPoint template to showcase the level of operational performance, optimization of production factors, use of available resources, structure cost control and optimization. This deck is a guide for your business team. You can easily impart your information with this operational efficiency presentation graphics. These templates are designed in communicating way by our team of experts having in-depth knowledge of the subject. All the slides given in operational performance evaluation presentation are editable, users can change font size, color and text to make it more attractive. Acquaint folks with their great culture through our Operational Performance Management Powerpoint Presentation Slides. Inform them of their inheritance.
Flow Efficiency, the most powerful improvement driver - Scrum Australia 2018
The document discusses flow efficiency, which is a measure of how much time is spent on valuable work versus waiting. It defines flow efficiency and explains why organizations should focus on improving it. Flow efficiency is calculated by dividing touch time by lead time. The document provides tips for how to measure, analyze sources of delay, and improve an organization's flow efficiency through principles like limiting work-in-progress and reducing dependencies. The biggest leverage for improving productivity is reducing delays rather than improving individual performance.
Stop using spreadsheets to monitor quality in your call centre!
The document describes a quality assessment solution called Scorebuddy that delivers real results, makes the job easier, and helps impress bosses. It provides rapid return on investment, improves agent and team performance, and allows managers and supervisors to make decisions using reports and analytics. Scorebuddy is easy to use, gives all information in one place, and saves time.
Recommended
Predictability at Axial
Given at Axial HQ for the New York chapter of Venwise, this talk details how Axial approaches building products predictably through a combination of focus, objectives, prioritization and forecasting. We call it stack.
Check out more of what we're building over at: axialcorps.com
Batting Averages and Slugging %s
This document discusses alternatives to using team velocity as a metric for software development teams. It proposes measuring the frequency of delivering value to users through high value releases, prioritizing work that provides the best value for effort, and recognizing individuals who consistently deliver high value features. Specific metrics proposed include an L value batting average measuring weeks with high value releases, slugging percentage measuring value delivered, and a silver slugger award for top performers.
Finance Presentation
The document discusses accounting and finance processes and systems at WGUK. It identifies several key issues: data accuracy problems across systems from meter points to invoices; a lack of validation processes between integrated systems; and a need for proper testing before new systems go live. It recommends: understanding problems fully before taking action; introducing validation and testing rigorously; focusing initially on fixing meter point and data accuracy issues; training staff; and establishing accurate budgets and processes for long-term improvement.
Getting To Product Market Fit Quickly
This 1-hour workshop marries the best practices from product strategy with those of fast and efficient technology teamwork and delivery. You’ll learn how to get your product organization working as a single cohesive, well-oiled machine to deliver the right product to market as quickly as possible. We will cover how to use both qualitative and quantitative measures to ensure that your product is solving the right problem; how to optimize and streamline the way your team designs, builds, and deploys software to your customers; and, how to beat the competition in strategy and execution.
Range estimation in Scrum
Presentation by OpenSource Connections consultant Arin Sime at Agile2010 conference on how to incorporate range estimation techniques into Scrum.
Operational Performance Management PowerPoint Presentation Slides
Operational performance management is a key factor in successfully achieving the business target. Analyze the performance of your business with our content ready Operational Performance Management PowerPoint Presentation Slides. Evaluate business activities to meet organizational goals with the help of business operations management PPT slides. Assess regularly the performance of your business. you can also use performance measures PowerPoint template to showcase the level of operational performance, optimization of production factors, use of available resources, structure cost control and optimization. This deck is a guide for your business team. You can easily impart your information with this operational efficiency presentation graphics. These templates are designed in communicating way by our team of experts having in-depth knowledge of the subject. All the slides given in operational performance evaluation presentation are editable, users can change font size, color and text to make it more attractive. Acquaint folks with their great culture through our Operational Performance Management Powerpoint Presentation Slides. Inform them of their inheritance.
Flow Efficiency, the most powerful improvement driver - Scrum Australia 2018
The document discusses flow efficiency, which is a measure of how much time is spent on valuable work versus waiting. It defines flow efficiency and explains why organizations should focus on improving it. Flow efficiency is calculated by dividing touch time by lead time. The document provides tips for how to measure, analyze sources of delay, and improve an organization's flow efficiency through principles like limiting work-in-progress and reducing dependencies. The biggest leverage for improving productivity is reducing delays rather than improving individual performance.
Stop using spreadsheets to monitor quality in your call centre!
The document describes a quality assessment solution called Scorebuddy that delivers real results, makes the job easier, and helps impress bosses. It provides rapid return on investment, improves agent and team performance, and allows managers and supervisors to make decisions using reports and analytics. Scorebuddy is easy to use, gives all information in one place, and saves time.
Process Evolution and Product Maturity
PROFES 2018, Wolfsburg: Talk by Tilman Seifert (Principal IT Consultant at QAware)
=== Please download slides if blurred! ===
Abstract: Processes cannot just be judged as ``good'' or ``efficient''---they must be appropriate for the type of project. As the type of a project changes over time,
the processes must adjust in order to stay efficient and appropriate.
We accompanied the transformation of a large and fast-growing project, using agile development methods and cloud-native technologies, from the very first steps of a prototype to the development of a customer-ready product.
This experience report shows patterns we found on the way.
It argues that systematic process evolution can be done without documentation overhead or relying on questionable process KPIs.
We only used information which is available anyway; this includes our archive of sprint retro boards which allows to create a clear picture of the project's evolution, regarding both the process and the product quality.
The SOLUTION Model
A model to help design any ideas, solutions or countermeasures wishing to implement to close performance gaps. Use as a tool or a checklist.
Time Doctor Review: A Freelancer’s Perspective
A productivity Q&A between TimeDoctor and USource on how time tracking creates and curates reports for dedicated virtual assistants.
One trunk one pipeline one truth
The document discusses deploying code changes quickly through continuous integration, delivery, and deployment practices. It advocates for having a single code repository ("one trunk"), automated builds and testing on every commit, deploying to staging frequently, and aiming to deploy changes within hours or less. This allows for early feedback, catching issues early, and responding quickly to change requests from customers through incremental and frequent deliveries.
Relationship Business-Projects-Operations
This presentation discusses good practices for successful project management. It recommends 1) defining success criteria at the start, 2) identifying drivers, constraints and flexibility, 3) defining release criteria during planning, and 4) negotiating achievable commitments. Additional tips include writing detailed plans, estimating efforts not time, tracking progress openly and honestly, and conducting retrospectives. The presentation notes that requirements will constantly change and the key is to simplify change management.
agile_flow
The document outlines the Scrum process for managing product development, including estimating story points, prioritizing stories, committing to a sprint backlog, tracking progress daily, and meeting at the end of each sprint to review outcomes and plan improvements. Key steps involve breaking down features into user stories with acceptance criteria, estimating story effort, committing to complete specific stories each sprint, tracking task progress, addressing any issues that arise, demoing completed work, and retrospecting on lessons learned.
Linkedin Resource Focus
The document discusses resource allocation and project prioritization at a development organization. It notes that during normal operations, projects account for 80% of resources while sustaining work accounts for 15% and other tasks 10%. During crises, development drops to one project per engineer with sustaining work at 15%, project management at 5%, and other tasks at 10%. It proposes shifting more time to core competency work, offloading project management tasks, and dedicating resources to sustaining work to reduce project switching.
Software management...for people who just want to get stuff done
This document discusses concepts and techniques for software project management, including planning, estimation, execution, and retrospectives. It covers these concepts at the level of projects, milestones within projects, sprints, and individual stories. Key points emphasized include breaking work into small chunks, using techniques like planning poker and burndown charts, being honest about estimates, and using retrospectives to improve.
Implementing infinity hr (katie cuthriell)
This document outlines the key steps for successfully implementing the InfinityHR system. It discusses (1) planning and preparing by understanding needs, setting goals, and building a timeline, (2) designing an optimal solution by focusing on priorities and recommendations, (3) building by providing clean data and consistent communication, and (4) testing and training through engaging sessions and practicing tasks to ensure expertise before (5) deploying the system and scheduling follow up meetings for ongoing success.
Agile estimation and planning peter saddington
The document discusses several techniques for estimating the size and complexity of features in agile development projects, including planning poker, decomposition, and using ideal time vs elapsed time. It emphasizes that estimation in agile focuses on relative sizing rather than durations, and that estimates are intentionally vague at first and improve over time based on measuring team velocity. Key goals of iteration planning meetings are to set commitments and arrive at a prioritized backlog for the upcoming sprint.
Implementing InfinityHR
The document outlines the key steps for implementing a new HR system called InfinityHR, including plan and prepare, design, build, testing and training, and deployment. Plan and prepare involves setting goals, organizing teams, documenting requirements, and preparing clients. Design focuses on optimizing business processes. Build requires clean data and consistent communication. Testing and training dedicates time to thoroughly test the system and make training engaging. Deployment ensures clients control the system and receive check-ins for ongoing success.
Continuous deployment
Continuous development allows for smaller code deployments more frequently, which provides developers better opportunities to innovate and experiment. Working in smaller batches keeps the development process dynamic and fast by allowing features to be deployed before being fully complete. It also reduces errors and makes issue resolution quicker by providing more regular feedback compared to large, infrequent deployments where problems are found later in the integration process.
How to Achieve Per-Project Profitability
This document outlines steps to achieve per-project profitability through accurate project cost tracking and data analysis. It recommends: 1) Evaluating past project data to improve estimates; 2) Tracking hours and expenses per project for early problem detection; 3) Adding labor rates for a full cost view; 4) Allocating indirect costs fairly across projects; and 5) Calculating per-project profitability to focus on profitable work. Accurate cost data allows problems to be found and addressed early, improving project outcomes and overall profitability.
Problem Solving A3 Approach
This document provides guidance for using the A3 problem solving methodology. It outlines the key sections of an A3 report, including: (1) clarifying the problem; (2) breaking down the problem; (3) setting targets; (4) analyzing root causes; (5) developing countermeasures and a plan; (6) monitoring and reviewing progress; and (7) standardizing and sharing lessons learned. The document emphasizes thoroughly investigating the problem, asking why it occurs, prioritizing issues, developing countermeasures, and periodically updating the report to track results.
NECS Sustain Tools
- The document discusses the NECS methodology for helping small businesses grow and achieve their highest potential.
- The methodology involves a nine-step problem identification and solving process to address challenges small businesses face. This includes forming a team, analyzing current processes, identifying root causes, testing and implementing solutions.
- Key tools used in the methodology include value stream mapping, line charts, and Pareto diagrams to analyze current and future states, identify improvements, and ensure changes lead to results. The methodology aims to deliver results within 3 to 14 days.
Kaizen presentation to management meeting
The document discusses the Kaizen philosophy of continuous improvement. Kaizen focuses on making small, incremental changes over time to optimize processes and quality. It is a collaborative approach that involves all stakeholders. The 10 step Kaizen process identifies problems, plans and implements solutions, then measures results to identify areas for further improvement. The goal is to empower teams to continuously enhance their work through data-driven experiments and adjustments.
Experiences from building a global scale learning service
The document provides advice for building a web 2.0 platform based on experiences. It recommends aiming for 90% completion to balance functionality and time, getting used to iterative development and change, keeping things simple, picking the right tools, being honest, and persisting through challenges without giving up. Building a community and "wrapper" elements like documentation takes significant time and effort. Different people have different skills so a mix is needed, but extraordinary members are key to leading the process.
How to play project management simulation
This document provides instructions for a project management simulation. It explains how to log in, view project details like activities and team members, make work delegation and scheduling decisions each week, and monitor the project's progress. The simulation puts the user in charge of a project with activities, a budget, and timeline. Each week, the user assigns team members to activities, sets the schedule including overtime, and holds meetings. Progress is tracked through dashboards with activity summaries and cost reports. The goal is to complete all activities within budget and deadline.
The on-call survival guide - how to be confident on-call
Is being a developer on-call making you burned out? Are there a lack of systems in place to support you when there's a major outage? This slide deck will go though how to create an on-call system that works.
Improving Estimates
This document provides guidance on improving estimates. It discusses expanding one's comfort zone to better understand related processes and people. Common estimation methods are outlined, including analogy, expert judgment, and task breakdown. The document emphasizes the importance of holistic, continuous estimation that considers risks, assumptions, and dependencies. It advises committing to estimates only when requirements are clear and risks are addressed, and avoiding arbitrary padding or unrealistic deadlines. Signs of poor estimates, like unreasonable assumptions or lack of deliverable definition, are identified as "estimate smells" to avoid.
Agile estimates - Insights about the basic
This is a presentation I made in the beginning of this year to explain the basics of agile Estimates. Although the presentation doesn't cover exceptions and some special cases (like in the case of hours estimates) it's a good starting point. A text to understand better the presentation will come on my channel on Medium soon.
How to Best Develop a Product by PlateRate Founder
This presentation is your guide on how to Best Develop a Product from scratch. Learn the best methodology on how to succeed in developing a product.
More Related Content
What's hot
Process Evolution and Product Maturity
PROFES 2018, Wolfsburg: Talk by Tilman Seifert (Principal IT Consultant at QAware)
=== Please download slides if blurred! ===
Abstract: Processes cannot just be judged as ``good'' or ``efficient''---they must be appropriate for the type of project. As the type of a project changes over time,
the processes must adjust in order to stay efficient and appropriate.
We accompanied the transformation of a large and fast-growing project, using agile development methods and cloud-native technologies, from the very first steps of a prototype to the development of a customer-ready product.
This experience report shows patterns we found on the way.
It argues that systematic process evolution can be done without documentation overhead or relying on questionable process KPIs.
We only used information which is available anyway; this includes our archive of sprint retro boards which allows to create a clear picture of the project's evolution, regarding both the process and the product quality.
The SOLUTION Model
A model to help design any ideas, solutions or countermeasures wishing to implement to close performance gaps. Use as a tool or a checklist.
Time Doctor Review: A Freelancer’s Perspective
A productivity Q&A between TimeDoctor and USource on how time tracking creates and curates reports for dedicated virtual assistants.
One trunk one pipeline one truth
The document discusses deploying code changes quickly through continuous integration, delivery, and deployment practices. It advocates for having a single code repository ("one trunk"), automated builds and testing on every commit, deploying to staging frequently, and aiming to deploy changes within hours or less. This allows for early feedback, catching issues early, and responding quickly to change requests from customers through incremental and frequent deliveries.
Relationship Business-Projects-Operations
This presentation discusses good practices for successful project management. It recommends 1) defining success criteria at the start, 2) identifying drivers, constraints and flexibility, 3) defining release criteria during planning, and 4) negotiating achievable commitments. Additional tips include writing detailed plans, estimating efforts not time, tracking progress openly and honestly, and conducting retrospectives. The presentation notes that requirements will constantly change and the key is to simplify change management.
agile_flow
The document outlines the Scrum process for managing product development, including estimating story points, prioritizing stories, committing to a sprint backlog, tracking progress daily, and meeting at the end of each sprint to review outcomes and plan improvements. Key steps involve breaking down features into user stories with acceptance criteria, estimating story effort, committing to complete specific stories each sprint, tracking task progress, addressing any issues that arise, demoing completed work, and retrospecting on lessons learned.
Linkedin Resource Focus
The document discusses resource allocation and project prioritization at a development organization. It notes that during normal operations, projects account for 80% of resources while sustaining work accounts for 15% and other tasks 10%. During crises, development drops to one project per engineer with sustaining work at 15%, project management at 5%, and other tasks at 10%. It proposes shifting more time to core competency work, offloading project management tasks, and dedicating resources to sustaining work to reduce project switching.
Software management...for people who just want to get stuff done
This document discusses concepts and techniques for software project management, including planning, estimation, execution, and retrospectives. It covers these concepts at the level of projects, milestones within projects, sprints, and individual stories. Key points emphasized include breaking work into small chunks, using techniques like planning poker and burndown charts, being honest about estimates, and using retrospectives to improve.
Implementing infinity hr (katie cuthriell)
This document outlines the key steps for successfully implementing the InfinityHR system. It discusses (1) planning and preparing by understanding needs, setting goals, and building a timeline, (2) designing an optimal solution by focusing on priorities and recommendations, (3) building by providing clean data and consistent communication, and (4) testing and training through engaging sessions and practicing tasks to ensure expertise before (5) deploying the system and scheduling follow up meetings for ongoing success.
Agile estimation and planning peter saddington
The document discusses several techniques for estimating the size and complexity of features in agile development projects, including planning poker, decomposition, and using ideal time vs elapsed time. It emphasizes that estimation in agile focuses on relative sizing rather than durations, and that estimates are intentionally vague at first and improve over time based on measuring team velocity. Key goals of iteration planning meetings are to set commitments and arrive at a prioritized backlog for the upcoming sprint.
Implementing InfinityHR
The document outlines the key steps for implementing a new HR system called InfinityHR, including plan and prepare, design, build, testing and training, and deployment. Plan and prepare involves setting goals, organizing teams, documenting requirements, and preparing clients. Design focuses on optimizing business processes. Build requires clean data and consistent communication. Testing and training dedicates time to thoroughly test the system and make training engaging. Deployment ensures clients control the system and receive check-ins for ongoing success.
Continuous deployment
Continuous development allows for smaller code deployments more frequently, which provides developers better opportunities to innovate and experiment. Working in smaller batches keeps the development process dynamic and fast by allowing features to be deployed before being fully complete. It also reduces errors and makes issue resolution quicker by providing more regular feedback compared to large, infrequent deployments where problems are found later in the integration process.
How to Achieve Per-Project Profitability
This document outlines steps to achieve per-project profitability through accurate project cost tracking and data analysis. It recommends: 1) Evaluating past project data to improve estimates; 2) Tracking hours and expenses per project for early problem detection; 3) Adding labor rates for a full cost view; 4) Allocating indirect costs fairly across projects; and 5) Calculating per-project profitability to focus on profitable work. Accurate cost data allows problems to be found and addressed early, improving project outcomes and overall profitability.
Problem Solving A3 Approach
This document provides guidance for using the A3 problem solving methodology. It outlines the key sections of an A3 report, including: (1) clarifying the problem; (2) breaking down the problem; (3) setting targets; (4) analyzing root causes; (5) developing countermeasures and a plan; (6) monitoring and reviewing progress; and (7) standardizing and sharing lessons learned. The document emphasizes thoroughly investigating the problem, asking why it occurs, prioritizing issues, developing countermeasures, and periodically updating the report to track results.
NECS Sustain Tools
- The document discusses the NECS methodology for helping small businesses grow and achieve their highest potential.
- The methodology involves a nine-step problem identification and solving process to address challenges small businesses face. This includes forming a team, analyzing current processes, identifying root causes, testing and implementing solutions.
- Key tools used in the methodology include value stream mapping, line charts, and Pareto diagrams to analyze current and future states, identify improvements, and ensure changes lead to results. The methodology aims to deliver results within 3 to 14 days.
Kaizen presentation to management meeting
The document discusses the Kaizen philosophy of continuous improvement. Kaizen focuses on making small, incremental changes over time to optimize processes and quality. It is a collaborative approach that involves all stakeholders. The 10 step Kaizen process identifies problems, plans and implements solutions, then measures results to identify areas for further improvement. The goal is to empower teams to continuously enhance their work through data-driven experiments and adjustments.
Experiences from building a global scale learning service
The document provides advice for building a web 2.0 platform based on experiences. It recommends aiming for 90% completion to balance functionality and time, getting used to iterative development and change, keeping things simple, picking the right tools, being honest, and persisting through challenges without giving up. Building a community and "wrapper" elements like documentation takes significant time and effort. Different people have different skills so a mix is needed, but extraordinary members are key to leading the process.
How to play project management simulation
This document provides instructions for a project management simulation. It explains how to log in, view project details like activities and team members, make work delegation and scheduling decisions each week, and monitor the project's progress. The simulation puts the user in charge of a project with activities, a budget, and timeline. Each week, the user assigns team members to activities, sets the schedule including overtime, and holds meetings. Progress is tracked through dashboards with activity summaries and cost reports. The goal is to complete all activities within budget and deadline.
The on-call survival guide - how to be confident on-call
Is being a developer on-call making you burned out? Are there a lack of systems in place to support you when there's a major outage? This slide deck will go though how to create an on-call system that works.
What's hot (19)
Software management...for people who just want to get stuff done
Software management...for people who just want to get stuff done
Experiences from building a global scale learning service
Experiences from building a global scale learning service
The on-call survival guide - how to be confident on-call
The on-call survival guide - how to be confident on-call
Similar to Uncertainty in agile projects
Improving Estimates
This document provides guidance on improving estimates. It discusses expanding one's comfort zone to better understand related processes and people. Common estimation methods are outlined, including analogy, expert judgment, and task breakdown. The document emphasizes the importance of holistic, continuous estimation that considers risks, assumptions, and dependencies. It advises committing to estimates only when requirements are clear and risks are addressed, and avoiding arbitrary padding or unrealistic deadlines. Signs of poor estimates, like unreasonable assumptions or lack of deliverable definition, are identified as "estimate smells" to avoid.
Agile estimates - Insights about the basic
This is a presentation I made in the beginning of this year to explain the basics of agile Estimates. Although the presentation doesn't cover exceptions and some special cases (like in the case of hours estimates) it's a good starting point. A text to understand better the presentation will come on my channel on Medium soon.
How to Best Develop a Product by PlateRate Founder
This presentation is your guide on how to Best Develop a Product from scratch. Learn the best methodology on how to succeed in developing a product.
Why all deadlines are bad for quality
In this article I will explore why I think that deadlines should never be communicated to the development teams, and why all deadlines are basically meaningless anyway.
Estimation is dead - long live sizing, by John Coleman 13June2023.pdf
A talk by John Coleman on the InfoQ article on sizing and forecasting in Scrum at https://www.infoq.com/articles/sizing-forecasting-scrum/
Assurance of Agile Delivery - Wellingtone | FuturePMO
In today’s fast-paced and ever-changing business landscape, organisations are increasingly turning to Agile methodologies to enhance their project delivery capabilities. Agile offers flexibility, adaptability, and customer-centricity, but ensuring the successful delivery of Agile projects requires a unique set of strategies and practices.
This session will uncover what is unique about assurance of Agile Delivery, and come find out why to assure, what to assure, when and how. Trust us, Agile delivery needs assurance, too!
This was presented by Marisa Silva, Senior Consultant from
Wellingtone at FuturePMO, on the 26th of October.
FuturePMO is a 1-day PMO event for practitioners at all levels. The conference brings extraordinary speakers from across industries to challenge your PMO and PPM thinking, helping you work smarter.
The next one takes place on the 3rd of October 2024 in London. To learn more and book on to the next conference, visit www.FuturePMO.com
LinkedIn - https://www.linkedin.com/showcase/11120292
Twitter - https://twitter.com/FuturePMO
Facebook - https://www.facebook.com/futurepmoevent/
YouTube - https://www.youtube.com/channel/UCHi8w5ACqsloXxBEA9t9pfA
Agile Features
This document contains an introduction to agile principles compared to traditional plan-driven development. It discusses key concepts of agile such as iterative development, rapid feedback loops, transparency, and adapting to change. The document emphasizes delivering customer value through working software over comprehensive documentation. It advocates for minimizing waste and focusing on eliminating bottlenecks rather than keeping all workers fully utilized.
What is agile and why should you care?
I´d like to share this presentation I created to give awareness of that is Agile, the scrum framework and why we should consider that in our daily basis, personal and proffessional level.
Software Project Estimation Survival Guide
Software Project Estimation Survival Guide.
A practical approach to making estimates that both you and your clients can live with.
Agile Kolkata 2022 - Vaibhav Sharma | One Metric that your Agile Team will ev...
Agile Kolkata 2022
One Metric that your Agile Team will ever Need
Vaibhav Sharma
Principal Consultant
StatusNeo
Successfully delivering an engagement
General pointers for consideration, in a engagement based delivery model. Applicable for Design, Development and customer facing teams.
Fixed price scrum - Patrick Vine
Fixed price contracts are often used by customers to control costs and reduce risk, but they can lead to scope wars between the customer and supplier as each tries to maximize their own interests. While estimates are educated guesses, scrum helps manage a fixed price project by prioritizing and sizing the backlog, having frequent reviews to catch misunderstandings early, and managing expectations and delivery dates. On one project, using scrum allowed the team to deliver an initial release on time with reduced scope and a second release for the remaining work, satisfying the customer's needs within the fixed budget. Scrum can work for fixed price projects if expectations are managed openly and the process is not abandoned.
10 critical factors for success of a project
The document outlines 10 critical factors for project success: 1) Keeping projects simple through clear objectives and communication. 2) The project manager is ultimately responsible for delivery. 3) Reinforcing focus through organizational prioritization and strong support. 4) Setting specific and quantifiable objectives. 5) Developing a clear and detailed project plan. 6) Maintaining the project scope. 7) Building an inspired project team. 8) Effective issue management. 9) Risk planning and mitigation. 10) Agreeing on a point of closure for the project. The key is transparent communication with all stakeholders.
5W2H Implementation Project.pptx
This document outlines a project proposal template that uses a 5W2H (five W's and two H's) method to structure the key elements of a project. The 5W2H sections are What, Why, When, Where, Who, How, and How Much. The document provides examples and descriptions for how to complete each section of the 5W2H template to define the objectives, resources, activities, timeline, and solutions for a proposed project in a clear and concise manner.
Agile planning
This presentation covers basics of agile planning. This includes, release planning, iteration planning, predicting velocity and using buffers.
Is your ladder leaning against the right wall?
Measurements and KPIs are crucial for our ability to improve. Used in the right way, they provide a vital ability for us to ‘see’ where we are, they enable feedback and allow us to make adjustments to ourselves, teams and businesses. The right measures can even be inspiring and unifying.
However, picking the wrong measures or applying them without consideration can limit performance and promote behaviours you don’t want (or more commonly, didn’t expect).
Estimating value through the lens of cost of delay
This document discusses estimating value through the lens of cost of delay. It provides tools and frameworks for estimating value in an agile manner based on imperfect information and assumptions. Key points include:
- Estimating value requires shifting to a mindset of making decisions based on assumptions rather than precise measurements.
- Value types (increase revenue, reduce costs, etc.) and urgency profiles (expedite, standard, fixed date, intangible) provide simple frameworks for assessing economic impact and risk of delay.
- Cost of delay estimates the financial impact of delaying work and helps prioritize features based on their time-sensitive value rather than effort.
- Exercises are provided to estimate lead time, delay
Pm For Fun And Profit
The document provides tips and best practices for project management of websites built with Drupal. It discusses the importance of planning, communication with clients, using an appropriate development process (agile vs waterfall), estimating timelines, scheduling tasks, prioritizing design, managing client expectations, and Drupal-specific considerations.
Project Management for Fun and Profit
A very brief overview of Project Management needs and pains from an individual or small firm Open Source Viewpoint.
Estimation is dead - long live sizing, by John Coleman 24Nov22.pdf
Estimation is dead - long live sizing, by John Coleman 24 Nov 22 to Agile Azerbaijan in person and Pozitive Technologies online
As per https://www.infoq.com/articles/sizing-forecasting-scrum/
Similar to Uncertainty in agile projects (20)
How to Best Develop a Product by PlateRate Founder
How to Best Develop a Product by PlateRate Founder
Estimation is dead - long live sizing, by John Coleman 13June2023.pdf
Estimation is dead - long live sizing, by John Coleman 13June2023.pdf
Assurance of Agile Delivery - Wellingtone | FuturePMO
Assurance of Agile Delivery - Wellingtone | FuturePMO
Agile Kolkata 2022 - Vaibhav Sharma | One Metric that your Agile Team will ev...
Agile Kolkata 2022 - Vaibhav Sharma | One Metric that your Agile Team will ev...
Estimating value through the lens of cost of delay
Estimating value through the lens of cost of delay
Estimation is dead - long live sizing, by John Coleman 24Nov22.pdf
Estimation is dead - long live sizing, by John Coleman 24Nov22.pdf
More from Skills Matter
5 things cucumber is bad at by Richard Lawrence
This talk will look at 5 things Cucumber’s bad at, why that’s a good thing, and what it tells us about Cucumber’s sweet spot in a team’s toolkit.
Many times, when people complain about something Cucumber’s not good at, they’re unwittingly describing something Cucumber shouldn't be good at. They’re revealing that they don’t quite understand BDD and Cucumber’s role in it.
Cucumber is the world's most misunderstood collaboration tool and people need to hear this over and over again.
Patterns for slick database applications
Slick is Typesafe's open source database access library for Scala. It features a collection-style API, compact syntax, type-safe, compositional queries and explicit execution control. Community feedback helped us to identify common problems developers are facing when writing Slick applications. This talk suggests particular solutions to these problems. We will be looking at reducing boiler-plate, re-using code between queries, efficiently modeling object references and more.
Scala e xchange 2013 haoyi li on metascala a tiny diy jvm
Metascala is a tiny metacircular Java Virtual Machine (JVM) written in the Scala programming language. Metascala is barely 3000 lines of Scala, and is complete enough that it is able to interpret itself metacircularly. Being written in Scala and compiled to Java bytecode, the Metascala JVM requires a host JVM in order to run.
The goal of Metascala is to create a platform to experiment with the JVM: a 3000 line JVM written in Scala is probably much more approachable than the 1,000,000 lines of C/C++ which make up HotSpot, the standard implementation, and more amenable to implementing fun features like continuations, isolates or value classes. The 3000 lines of code gives you:
The bytecode interpreter, together with all the run-time data structures
A stack-machine to SSA register-machine bytecode translator
A custom heap, complete with a stop-the-world, copying garbage collector
Implementations of parts of the JVM's native interface
Although it is far from a complete implementation, Metascala already provides the ability to run untrusted bytecode securely (albeit slowly), since every operation which could potentially cause harm (including memory allocations and CPU usage) is virtualized and can be controlled. Ongoing work includes tightening of the security guarantees, improving compatibility and increasing performance.
ENJOYIN
Oscar reiken jr on our success at manheim
This document discusses test automation at Manheim, a wholesale auto auction company. It describes how test automation was implemented for three of Manheim's major applications: Ove.com, Simulcast, and Manheim.com. Regression testing times were reduced from over 160 hours to under 10 minutes for Ove.com and similar improvements for the other applications. This was achieved by converting test cases to Cucumber scenarios, prioritizing by business value, and implementing the tests in Ruby and Java using tools like Watir and Selenium. The automation allows running hundreds of tests in parallel and integration with a build pipeline.
Progressive f# tutorials nyc dmitry mozorov & jack pappas on code quotations ...
Code Quotations: Code-as-Data for F#
This tutorial will cover F# Code Quotations in-depth. You'll learn what Code Quotations are, how to use them, and where to apply them in your applications. We'll work through several real-world examples to highlight the important features -- and potential pitfalls -- of Code Quotations.
Cukeup nyc ian dees on elixir, erlang, and cucumberl
Elixir, Erlang, and Cucumberl
Elixir is a new Ruby-inspired programming language that uses the powerful concurrent machinery of Erlang behind the scenes. Cucumberl is a port of Cucumber to Erlang. Let's see what happens when we put them together.
In this talk, we'll discuss:
How Erlang's concurrency makes it easier to write robust programs
Elixir's approachable syntax
How to test Erlang and Elixir programs using Cucumberl
Attendees will walk away with a solid introduction to the principles of Erlang, and an appreciation of the way Elixir brings the joy of Ruby to the solidity of the Erlang runtime.
Cukeup nyc peter bell on getting started with cucumber.js
Cukeup NYC. Peter Bell on Getting started with cucumber.js
Ever wished you could use cucumber in your javascript apps? In this talk we'll look at the current state of play of cucumber js, when you should and shouldn't use it, and how to get started writing your step definitions in javascript.
Agile testing & bdd e xchange nyc 2013 jeffrey davidson & lav pathak & sam ho...
In this engaging experience report, we will present 3 different views – Developer, Tester, Business Analyst – of implementing Acceptance Test Driven Development in a complex, data-driven domain. Hear how we used ATDD for building a ubiquitous language across the entire team, promoting faster feedback, and cultivating a culture where product owners were deeply invested in the quality of both every deliverable and the system as a whole.
Progressive f# tutorials nyc rachel reese & phil trelford on try f# from zero...
This document outlines the agenda for a workshop on trying F# for data science. The agenda includes introductions and setup, three sets of hands-on exercises - getting started in F#, financial applications, and data visualization - as well as breaks. It also covers type providers and their benefits, and concludes with a challenge problem and additional resources.
Progressive f# tutorials nyc don syme on keynote f# in the open source world
F# is a powerful open-source language which Microsoft, other companies and the F# community all contribute to. In this talk, Don will discuss how the “F# space” has recently opened up significantly in interesting ways. F# now includes contributions that range from Cloud IDE platforms, Cloud Compute frameworks, Data interoperability components, Cross-platform execution, Try F#, MonoDevelop, and even Emacs editor integration with surprising tooling support, as well as the Visual F# tools from Microsoft and the broader NuGet package ecosystem. Don will also talk about some of the latest contributions from Microsoft Research, including new type provider components for F#, and describe how his team work with the Visual F# team and other teams around Microsoft. There will also be demos of some fun new stuff that’s been going on with F# at MSR and the community.
Agile testing & bdd e xchange nyc 2013 gojko adzic on bond villain guide to s...
Would you like to learn how to make your software testing practices more effective? And how to use your testing strategy to better capture and reflect customer requirements? Gojko Adzic takes a critical look at the effectiveness of current software testing practices and proposes strategies to make it much more effective.
Dmitry mozorov on code quotations code as-data for f#
This document summarizes code quotations in F# and their uses, including for meta-programming, code transformation, testing frameworks, type providers, and data binding. Key points include: code quotations allow treating code as data; F# supports full language quotations unlike C# expression trees; quotations enable composing and decomposing code; and quotations are essential for type providers to access and represent types from other sources. Examples are provided for constructing and splicing quotations, implementing type providers, and using quotations for GUI input validation and data binding.
A poet's guide_to_acceptance_testing
The document appears to be notes from an acceptance testing session where examples are provided and expanded upon to test different scenarios. It starts with a story about Mary and her lamb and provides examples of adding different variables like location or characters. It then moves to testing a library book reservation system, providing different user types and expected outcomes. The document ends with two short poems used to discuss how word choice matters.
Russ miles-cloudfoundry-deep-dive
The document discusses the architecture and workflow of deploying applications on Cloud Foundry. It describes how the vmc command line tool is used to target an API endpoint, login, push an application, and shows the steps Cloud Foundry takes to validate the application package, stage it, find an available Diego Application Container instance to run it, and start the application.
Serendipity-neo4j
The document discusses the concept of serendipity and how to increase serendipitous discoveries through database and system design. It defines serendipity as the occurrence of beneficial discoveries by chance and describes three steps to encourage serendipity: 1) remove isolation by increasing connections across semantic and contextual boundaries, 2) allow information to traverse multiple hops, and 3) weight and filter information based on relevance and user feedback. Graph databases are said to better support serendipity compared to relational databases by more easily facilitating these three steps.
Simon Peyton Jones: Managing parallelism
If you want to program a parallel computer, it obviously makes sense to start with a computational paradigm in which parallelism is the default (ie functional programming), rather than one in which computation is based on sequential flow of control (the imperative paradigm). And yet, and yet ... functional programmers have been singing this tune since the 1980s, but do not yet rule the world. In this talk I’ll say why I think parallelism is too complex a beast to be slain at one blow, and how we are going to be driven, willy-nilly, towards a world in which side effects are much more tightly controlled than now. I’ll sketch a whole range of ways of writing parallel program in a functional paradigm (implicit parallelism, transactional memory, data parallelism, DSLs for GPUs, distributed processes, etc, etc), illustrating with examples from the rapidly moving Haskell community, and identifying some of the challenges we need to tackle.
Plug 20110217
The document discusses big data and Hadoop. It notes that big data comes in terabytes and petabytes, sometimes generated daily. Hadoop is presented as a framework for distributed computing on large datasets using MapReduce. While Hadoop can store and process massive amounts of data across commodity servers, it was not designed for business intelligence requirements. The document proposes addressing this by adding data integration and transformation capabilities to Hadoop through tools like Pentaho Data Integration, to enable it to better meet the needs of big data analytics.
Lug presentation
This document discusses different types of "magic" that can be done in Pentaho reporting including parameter magic, wizard magic, and query magic. Parameter magic allows parameters to control system settings like enabling server-side printing. Wizard magic involves features for customizing report outputs like summary fields and row layout. Query magic refers to functions that allow running queries and using results in reports or parameters, primarily for calculated default values. Demos are provided for each type of magic.
I went to_a_communications_workshop_and_they_t
The document discusses lessons from a communications workshop. It covers:
1. The benefits of continuous integration (CI) automation over manual processes, including peace of mind and high visibility.
2. An introduction to the Community Build Framework (CBF) which manages server configurations and automatically patches builds.
3. Types of tests that can be automated, including databases, ETL, user interfaces, and more.
Plug saiku
This document summarizes Saiku, an open source business intelligence and analytics tool. Saiku provides a lightweight user interface using HTML and JavaScript with a separate Java server and RESTful JSON communication. It is 100% open source and easily integrates with other data sources like SAP BW, Microsoft Analysis Services, and Mondrian. The roadmap outlines upcoming releases in early 2011 that will add features like drill support, visualizations, and basic integration with SAP BW.
More from Skills Matter (20)
Scala e xchange 2013 haoyi li on metascala a tiny diy jvm
Scala e xchange 2013 haoyi li on metascala a tiny diy jvm
Progressive f# tutorials nyc dmitry mozorov & jack pappas on code quotations ...
Progressive f# tutorials nyc dmitry mozorov & jack pappas on code quotations ...
Cukeup nyc ian dees on elixir, erlang, and cucumberl
Cukeup nyc ian dees on elixir, erlang, and cucumberl
Cukeup nyc peter bell on getting started with cucumber.js
Cukeup nyc peter bell on getting started with cucumber.js
Agile testing & bdd e xchange nyc 2013 jeffrey davidson & lav pathak & sam ho...
Agile testing & bdd e xchange nyc 2013 jeffrey davidson & lav pathak & sam ho...
Progressive f# tutorials nyc rachel reese & phil trelford on try f# from zero...
Progressive f# tutorials nyc rachel reese & phil trelford on try f# from zero...
Progressive f# tutorials nyc don syme on keynote f# in the open source world
Progressive f# tutorials nyc don syme on keynote f# in the open source world
Agile testing & bdd e xchange nyc 2013 gojko adzic on bond villain guide to s...
Agile testing & bdd e xchange nyc 2013 gojko adzic on bond villain guide to s...
Dmitry mozorov on code quotations code as-data for f#
Dmitry mozorov on code quotations code as-data for f#
Recently uploaded
20240607 QFM018 Elixir Reading List May 2024
Everything I found interesting about the Elixir programming ecosystem in May 2024
20240609 QFM020 Irresponsible AI Reading List May 2024
Everything I found interesting about the irresponsible use of machine intelligence in May 2024
Programming Foundation Models with DSPy - Meetup Slides
Prompting language models is hard, while programming language models is easy. In this talk, I will discuss the state-of-the-art framework DSPy for programming foundation models with its powerful optimizers and runtime constraint system.
Skybuffer SAM4U tool for SAP license adoption
Manage and optimize your license adoption and consumption with SAM4U, an SAP free customer software asset management tool.
SAM4U, an SAP complimentary software asset management tool for customers, delivers a detailed and well-structured overview of license inventory and usage with a user-friendly interface. We offer a hosted, cost-effective, and performance-optimized SAM4U setup in the Skybuffer Cloud environment. You retain ownership of the system and data, while we manage the ABAP 7.58 infrastructure, ensuring fixed Total Cost of Ownership (TCO) and exceptional services through the SAP Fiori interface.
Project Management Semester Long Project - Acuity
Acuity is an innovative learning app designed to transform the way you engage with knowledge. Powered by AI technology, Acuity takes complex topics and distills them into concise, interactive summaries that are easy to read & understand. Whether you're exploring the depths of quantum mechanics or seeking insight into historical events, Acuity provides the key information you need without the burden of lengthy texts.
Introduction of Cybersecurity with OSS at Code Europe 2024
I develop the Ruby programming language, RubyGems, and Bundler, which are package managers for Ruby. Today, I will introduce how to enhance the security of your application using open-source software (OSS) examples from Ruby and RubyGems.
The first topic is CVE (Common Vulnerabilities and Exposures). I have published CVEs many times. But what exactly is a CVE? I'll provide a basic understanding of CVEs and explain how to detect and handle vulnerabilities in OSS.
Next, let's discuss package managers. Package managers play a critical role in the OSS ecosystem. I'll explain how to manage library dependencies in your application.
I'll share insights into how the Ruby and RubyGems core team works to keep our ecosystem safe. By the end of this talk, you'll have a better understanding of how to safeguard your code.
Fueling AI with Great Data with Airbyte Webinar
This talk will focus on how to collect data from a variety of sources, leveraging this data for RAG and other GenAI use cases, and finally charting your course to productionalization.
How to Get CNIC Information System with Paksim Ga.pptx
Pakdata Cf is a groundbreaking system designed to streamline and facilitate access to CNIC information. This innovative platform leverages advanced technology to provide users with efficient and secure access to their CNIC details.
UiPath Test Automation using UiPath Test Suite series, part 6
Welcome to UiPath Test Automation using UiPath Test Suite series part 6. In this session, we will cover Test Automation with generative AI and Open AI.
UiPath Test Automation with generative AI and Open AI webinar offers an in-depth exploration of leveraging cutting-edge technologies for test automation within the UiPath platform. Attendees will delve into the integration of generative AI, a test automation solution, with Open AI advanced natural language processing capabilities.
Throughout the session, participants will discover how this synergy empowers testers to automate repetitive tasks, enhance testing accuracy, and expedite the software testing life cycle. Topics covered include the seamless integration process, practical use cases, and the benefits of harnessing AI-driven automation for UiPath testing initiatives. By attending this webinar, testers, and automation professionals can gain valuable insights into harnessing the power of AI to optimize their test automation workflows within the UiPath ecosystem, ultimately driving efficiency and quality in software development processes.
What will you get from this session?
1. Insights into integrating generative AI.
2. Understanding how this integration enhances test automation within the UiPath platform
3. Practical demonstrations
4. Exploration of real-world use cases illustrating the benefits of AI-driven test automation for UiPath
Topics covered:
What is generative AI
Test Automation with generative AI and Open AI.
UiPath integration with generative AI
Speaker:
Deepak Rai, Automation Practice Lead, Boundaryless Group and UiPath MVP
Presentation of the OECD Artificial Intelligence Review of Germany
Consult the full report at https://www.oecd.org/digital/oecd-artificial-intelligence-review-of-germany-609808d6-en.htm
Salesforce Integration for Bonterra Impact Management (fka Social Solutions A...
Sidekick Solutions uses Bonterra Impact Management (fka Social Solutions Apricot) and automation solutions to integrate data for business workflows.
We believe integration and automation are essential to user experience and the promise of efficient work through technology. Automation is the critical ingredient to realizing that full vision. We develop integration products and services for Bonterra Case Management software to support the deployment of automations for a variety of use cases.
This video focuses on integration of Salesforce with Bonterra Impact Management.
Interested in deploying an integration with Salesforce for Bonterra Impact Management? Contact us at sales@sidekicksolutionsllc.com to discuss next steps.
Webinar: Designing a schema for a Data Warehouse
Are you new to data warehouses (DWH)? Do you need to check whether your data warehouse follows the best practices for a good design? In both cases, this webinar is for you.
A data warehouse is a central relational database that contains all measurements about a business or an organisation. This data comes from a variety of heterogeneous data sources, which includes databases of any type that back the applications used by the company, data files exported by some applications, or APIs provided by internal or external services.
But designing a data warehouse correctly is a hard task, which requires gathering information about the business processes that need to be analysed in the first place. These processes must be translated into so-called star schemas, which means, denormalised databases where each table represents a dimension or facts.
We will discuss these topics:
- How to gather information about a business;
- Understanding dictionaries and how to identify business entities;
- Dimensions and facts;
- Setting a table granularity;
- Types of facts;
- Types of dimensions;
- Snowflakes and how to avoid them;
- Expanding existing dimensions and facts.
National Security Agency - NSA mobile device best practices
Threats to mobile devices are more prevalent and increasing in scope and complexity. Users of mobile devices desire to take full advantage of the features
available on those devices, but many of the features provide convenience and capability but sacrifice security. This best practices guide outlines steps the users can take to better protect personal devices and information.
Choosing The Best AWS Service For Your Website + API.pptx
Have you ever been confused by the myriad of choices offered by AWS for hosting a website or an API?
Lambda, Elastic Beanstalk, Lightsail, Amplify, S3 (and more!) can each host websites + APIs. But which one should we choose?
Which one is cheapest? Which one is fastest? Which one will scale to meet our needs?
Join me in this session as we dive into each AWS hosting service to determine which one is best for your scenario and explain why!
Let's Integrate MuleSoft RPA, COMPOSER, APM with AWS IDP along with Slack
Discover the seamless integration of RPA (Robotic Process Automation), COMPOSER, and APM with AWS IDP enhanced with Slack notifications. Explore how these technologies converge to streamline workflows, optimize performance, and ensure secure access, all while leveraging the power of AWS IDP and real-time communication via Slack notifications.
AI 101: An Introduction to the Basics and Impact of Artificial Intelligence
Imagine a world where machines not only perform tasks but also learn, adapt, and make decisions. This is the promise of Artificial Intelligence (AI), a technology that's not just enhancing our lives but revolutionizing entire industries.
Recently uploaded (20)
20240609 QFM020 Irresponsible AI Reading List May 2024
20240609 QFM020 Irresponsible AI Reading List May 2024
Programming Foundation Models with DSPy - Meetup Slides
Programming Foundation Models with DSPy - Meetup Slides
Introduction of Cybersecurity with OSS at Code Europe 2024
Introduction of Cybersecurity with OSS at Code Europe 2024
How to Get CNIC Information System with Paksim Ga.pptx
How to Get CNIC Information System with Paksim Ga.pptx
UiPath Test Automation using UiPath Test Suite series, part 6
UiPath Test Automation using UiPath Test Suite series, part 6
Presentation of the OECD Artificial Intelligence Review of Germany
Presentation of the OECD Artificial Intelligence Review of Germany
Salesforce Integration for Bonterra Impact Management (fka Social Solutions A...
Salesforce Integration for Bonterra Impact Management (fka Social Solutions A...
Deep Dive: AI-Powered Marketing to Get More Leads and Customers with HyperGro...
Deep Dive: AI-Powered Marketing to Get More Leads and Customers with HyperGro...
National Security Agency - NSA mobile device best practices
National Security Agency - NSA mobile device best practices
Choosing The Best AWS Service For Your Website + API.pptx
Choosing The Best AWS Service For Your Website + API.pptx
Let's Integrate MuleSoft RPA, COMPOSER, APM with AWS IDP along with Slack
Let's Integrate MuleSoft RPA, COMPOSER, APM with AWS IDP along with Slack
AI 101: An Introduction to the Basics and Impact of Artificial Intelligence
AI 101: An Introduction to the Basics and Impact of Artificial Intelligence
Uncertainty in agile projects
- 1. Uncertainty in Agile Projects A lightning talk about uncertainty