Rise and fall of Story Points. Capacity based planning from the trenches.
4 likes2,352 views
Люди в мире Agile используют Story Points - для Agile коучей и тренеров это самый простой способ объяснить, как следует проводить оценку и планирование в «новом мире». Но тогда эта простая концепция нарушает реальные практические кейсы. В настоящее время команды состоят из очень специализированных людей, работающих над бэкендом, фронтэндом, тестировании, инфраструктуре и прочим. Для них почти невозможно иметь общий уровень сложности. Это только одна из проблем, которые мы собираемся осветить в этом докладе. Чтобы оставаться конструктивным, а не просто старомодным парнем из XP, Николай поделится своим опытом с более точной и прагматичной техникой оценки/планирования - планированием на основе возможностей.
1 of 44
![Detailed instructions
Define and agree focus factor for each team member,
taking into account all aspects
Specify seniority factor to balance hours [OPTIONAL]
Use main competence of team members for grouping
Fill team individual Sprint calendars (1 – full day, 0.5 –
half day, 0.25 – couple of hours)
Mark team events and time consuming meetings
Calculate total capacity by competence](https://image.slidesharecdn.com/riseandfallofstorypoints-200229163545/85/Rise-and-fall-of-Story-Points-Capacity-based-planning-from-the-trenches-35-320.jpg)
Ad
Recommended
[HCM Scrum Breakfast] Agile estimation - Story points by Scrum Breakfast Vietnam, has 41 slides with 2363 views.This document provides information about agile estimation techniques, including story points and planning poker. It discusses how story points are used to provide relative estimates of complexity rather than time estimates. Planning poker is described as a consensus-based technique where a team privately selects story point cards before discussing to reach agreement. The document also covers insights around how additional details don't necessarily lead to better estimates and how past sprint performance can inform long-term planning estimates. Common questions about estimation techniques are addressed.![[HCM Scrum Breakfast] Agile estimation - Story points](https://cdn.slidesharecdn.com/ss_thumbnails/storypointsestimations-160827052054-thumbnail.jpg?width=560&fit=bounds)
[HCM Scrum Breakfast] Agile estimation - Story pointsScrum Breakfast Vietnam
41 slides•2.4K views
This document provides information about agile estimation techniques, including story points and planning poker. It discusses how story points are used to provide relative estimates of complexity rather than time estimates. Planning poker is described as a consensus-based technique where a team privately selects story point cards before discussing to reach agreement. The document also covers insights around how additional details don't necessarily lead to better estimates and how past sprint performance can inform long-term planning estimates. Common questions about estimation techniques are addressed.Sprint Review and Planning Template by Mike Lally, has 15 slides with 31581 views.The document provides a template for conducting a Sprint Review, Retrospective, and Planning meeting. It includes sections for demoing completed work, reviewing work accepted in the previous Sprint, discussing key performance metrics and action items from the prior Retrospective, setting the Sprint goal, and estimating work for the upcoming Sprint.
Sprint Review and Planning TemplateMike Lally
15 slides•31.6K views
The document provides a template for conducting a Sprint Review, Retrospective, and Planning meeting. It includes sections for demoing completed work, reviewing work accepted in the previous Sprint, discussing key performance metrics and action items from the prior Retrospective, setting the Sprint goal, and estimating work for the upcoming Sprint.Estimation techniques for Scrum Teams by Jesus Mendez, has 47 slides with 3225 views.My main goal is to share and make you experiment some of the techniques that I use when transforming teams into high-perfoming agile teams, by providing you with four (4) different ways to estimate projects in Agile. 
Estimation techniques for Scrum TeamsJesus Mendez
47 slides•3.2K views
My main goal is to share and make you experiment some of the techniques that I use when transforming teams into high-perfoming agile teams, by providing you with four (4) different ways to estimate projects in Agile. SCRUM Estimation by Kristen Varona, has 13 slides with 2665 views.This document discusses key concepts in agile planning including story points, velocity, and release planning using velocity. It defines story points as relative sizes used to estimate user stories, and explains how they remain constant over time unlike ideal days estimates. Velocity is defined as the average story points a team can complete per sprint. The document outlines how to establish story points and use them along with velocity for release planning and tracking progress with a burn down chart.
SCRUM EstimationKristen Varona
13 slides•2.7K views
This document discusses key concepts in agile planning including story points, velocity, and release planning using velocity. It defines story points as relative sizes used to estimate user stories, and explains how they remain constant over time unlike ideal days estimates. Velocity is defined as the average story points a team can complete per sprint. The document outlines how to establish story points and use them along with velocity for release planning and tracking progress with a burn down chart.As 5 Disfunções dos Times by Rodrigo Pereira, has 19 slides with 1921 views.Apresentação sobre as 5 disfunções do time. Material baseado no livro "As 5 Disfunções dos Times" de Patrick Lencioni
As 5 Disfunções dos TimesRodrigo Pereira
19 slides•1.9K views
Apresentação sobre as 5 disfunções do time. Material baseado no livro "As 5 Disfunções dos Times" de Patrick LencioniAgile estimation by Stephen Forte, has 23 slides with 15771 views.Agile Patterns: Agile Estimation
We’re agile, so we don’t have to estimate and have no deadlines, right? Wrong! This session will consist of review of the problem with estimation in projects today and then an overview of the concept of agile estimation and the notion of re-estimation. We’ll learn about user stories, story points, team velocity, how to apply them all to estimation and iterative re-estimation. We will take a look at the cone of uncertainty and how to use it to your advantage. We’ll then take a look at the tools we will use for Agile Estimation, including planning poker, Visual Studio Team System, and much more. This is a very interactive session, so bring a lot of questions!
Agile estimationStephen Forte
23 slides•15.8K views
Agile Patterns: Agile Estimation
We’re agile, so we don’t have to estimate and have no deadlines, right? Wrong! This session will consist of review of the problem with estimation in projects today and then an overview of the concept of agile estimation and the notion of re-estimation. We’ll learn about user stories, story points, team velocity, how to apply them all to estimation and iterative re-estimation. We will take a look at the cone of uncertainty and how to use it to your advantage. We’ll then take a look at the tools we will use for Agile Estimation, including planning poker, Visual Studio Team System, and much more. This is a very interactive session, so bring a lot of questions!
Chapter 3 - The Generic Test Automation Architecture by Neeraj Kumar Singh, has 82 slides with 2378 views.This is the chapter 3 of ISTQB Advance Test Automation Engineer certification. This presentation helps aspirants understand and prepare content of certification.
Chapter 3 - The Generic Test Automation Architecture Neeraj Kumar Singh
82 slides•2.4K views
This is the chapter 3 of ISTQB Advance Test Automation Engineer certification. This presentation helps aspirants understand and prepare content of certification.Agile Assessment Version 1.0 by Ciprian Mester, has 14 slides with 4925 views.The document provides the results of an Agile self-evaluation for a software delivery team. It finds that the team supports some Agile principles like prioritizing user stories and having generalist developers. However, it also finds practices that could be improved like more frequent integration builds and check-ins. The report recommends a more thorough assessment and continuous improvement program to help the team better adopt Agile practices.
Agile Assessment Version 1.0Ciprian Mester
14 slides•4.9K views
The document provides the results of an Agile self-evaluation for a software delivery team. It finds that the team supports some Agile principles like prioritizing user stories and having generalist developers. However, it also finds practices that could be improved like more frequent integration builds and check-ins. The report recommends a more thorough assessment and continuous improvement program to help the team better adopt Agile practices.[Product Camp 2020] - Níveis de Maturidade em Prod Ops - Thiago Belluf - Favo![[Product Camp 2020] - Níveis de Maturidade em Prod Ops - Thiago Belluf - Favo](https://cdn.slidesharecdn.com/ss_thumbnails/pcamp20-201203212618-thumbnail.jpg?width=560&fit=bounds)
[Product Camp 2020] - Níveis de Maturidade em Prod Ops - Thiago Belluf - FavoProduct Camp Brasil [1] Operações de Produto engloba diversas áreas como estratégia, comunicação, processos de desenvolvimento e gestão de pessoas.
[2] Um modelo de maturidade pode ajudar a avaliar o nível atual de uma empresa nessas áreas e identificar prioridades de melhoria.
[3] Um diagnóstico colaborativo, envolvendo diferentes stakeholders, é essencial para traçar um plano de ação que eleve a maturidade de Operações de Produto de forma contínua.
The Challenges of Agile Adoption
The Challenges of Agile AdoptionIntelliware Development Inc. The process of adopting Agile in any organization is challenging in many ways. It is especially challenging in larger organizations because of complex infrastructures, numerous legacy systems and mature organizational cultures. These larger organizations often underestimate the difficulty of getting Agile right.
This presentation will focus on the common challenges of Agile adoption. Tips are provided to help improve the chances of Agile adoption success.
Agile Estimation Techniques
Agile Estimation TechniquesMikalai Alimenkou Presentation from Agile Base Camp conference (Kiev, April 2011) about estimation techniques in Agile teams.
Seven Key Metrics to Improve Agile Performance
Seven Key Metrics to Improve Agile PerformanceTechWell It’s been said: If you can’t measure it, you can’t improve it. For most agile teams burndown charts and some type of velocity measurement are all they are doing. However, with just a few more metrics, you can gain substantial insight into how teams are performing and identify improvement opportunities. Andrew Graves explores seven key metrics―Effort by Class of Service, Accuracy of Estimation, Cost per Point, and four others―to measure how your team is doing and make adjustments in real time. Andrew illustrates how to use these metrics to communicate progress to stakeholders. Discover how to use these metrics to identify and analyze trends that lead to performance improvement ideas and strategies. Learn how to use these seven metrics to monitor the impact of changes made to verify they are bringing the hoped-for difference.
User story and splitting workshop
User story and splitting workshopBrian Sjoberg Do you want to write great User Stories that provide the vehicle for conversation and confirmation that we build the right thing? Do you struggle with splitting stories so that they still provide business value but can be accomplished within a fraction of your iteration? We will do a quick refresher on User Story formatting to include Acceptance Criteria. Additionally we will learn techniques for splitting stories in this interactive workshop.
How to estimate in scrum
How to estimate in scrumGloria Stoilova - Story points are an arbitrary measure used by Scrum teams to estimate the effort required to implement a user story. Teams typically use a Fibonacci sequence like 1, 2, 3, 5, 8, 13, 20, 40, 100.
- Estimating user stories allows teams to plan how many highest priority stories can be completed in a sprint and helps forecast release schedules. The whole team estimates during backlog refinement.
- Stories are estimated once they are small enough to fit in a sprint and acceptance criteria are agreed upon. Teams commonly use planning poker where each member privately assigns a story point value and the team discusses until consensus is reached.
Agile sw development 101
Agile sw development 101Kiwon Kyung 하얀 눈 위에 발자국은 반갑고 친구와 같은 느낌이었던 것 같습니다. 애자일 적용에 첫발을
내딛으려는 팀에게 도움이 되었으면 좋겠네요.
경기원, LG CNS
애자일을 통해 내가 하고 있는 무엇인가를 더 낫게 만들려는 욕심 있는 분들께 추천합니다.
신황규, 삼성SDS
현실을 부정하지 말고 일단 작게 시작하세요.
관찰하고 적응하세요. 특정 방법에 얽매이지 말고 애자일 선언문을 기억하세요. :-D
심우곤, LG전자
어제보다 나은 오늘을 만드는데 도움이 되었으면 좋겠습니다.
이승룡, 삼성SDS
애자일을 적용하려는 팀에 도움이 되었으면 좋겠어요!
채수원, NHN
여러분들이 애자일과 더 친해졌으면 합니다.
황상철, NHN
Agile Estimating & Planning by Amaad Qureshi
Agile Estimating & Planning by Amaad QureshiAmaad Qureshi An introduction to Agile Estimating and how it can be used to measure the size and length of work.
Agile estimating & planning is a way of measuring the size and time it takes to complete a task. This technique is used by Agile teams in Enterprise and can be utilised in the same way by Start-ups not just for software but for all areas of the business. In this talk I will show you how estimating & planning works by:
- Writing effective user stories
- Writing tests to validate stories (acceptance criteria)
- Using story points to work out the size of a task
- Estimating using Planning Poker
- Using Story Points to calculate a team’s velocity (speed of work)
- Using a team’s velocity to calculate project length
The Scrum Master Role
The Scrum Master RoleNigel Thurlow The document outlines the key responsibilities of a Scrum Master which include facilitating transparent communication and self-organization within the team. The Scrum Master aims to help the team adapt quickly to changes, solve problems independently, and create visual reporting tools. Some of the Scrum Master's other responsibilities are to reflect on meetings and ceremonies, ensure definition of done is agreed upon, protect the team from obstacles, and celebrate the team's successes.
User Story Sizing using Agile Relative Estimation
User Story Sizing using Agile Relative EstimationAlex Kanaan, SPC5, CSP, ACC, ATF Ever wonder why Agile teams swear by relative estimation? My teams improved sprint planning efforts by a factor or 3, once we started using relative estimation.
Without understanding Agile relative estimation, teams tend to fall back to using time-based methods. This often leads them to spend way too much time on obsolete estimates that will be made even more complex with all the unknowns and constant emergent requirements of an Agile world!
“It's better to be roughly right, than precisely wrong!”
~ John Maynard Keyenes
The Solution is simple: understand that relative estimation is only a rough order of magnitude estimate to quickly organize the product backlog. This empowers your product owners (PO) to quickly make value based trade-offs on backlog items and decide on what stories the team should work next. This gives the business the highest bang for their buck!
PROBLEMS WITH TIME-BASED ESTIMATES
-Teams spend too much time trying to get it right
-Lack of confidence/experience can lead to people being either optimistic or pessimistic
-Timeline you are estimating may be too far in the future
-Due to long timeline, there are too many risks, unknowns, changes or dependencies!
WHY USE RELATIVE ESTIMATION?
-Allows a quick comparison of stories in the backlog
-Allows you to select a predictable volume of work to do in a sprint
-Uses a simple arbitrary scale
-Allows PO to make trade-offs and take on the most valuable stories next
ESTIMATION TIPS
-Relative points or equivalent Tshirt sizes are used to estimate stories, leveraging the Fibonacci sequence modified for Agile.
-The team estimates the story, not management nor the customer.
-Story estimates account for three things: effort, complexity, and unknowns. Don’t short sell yourself by estimating effort alone, that’s where waterfall projects face issues.
-Remember to estimate all Stories, user stories or technical stories. Even estimate research or discovery spikes.
-Refine your backlog as a team on a continuous basis, to get your stories to meet the Definition of Ready.
-Only pull into your sprint, stories that are refined and estimated.
-Break down stories that are large, into smaller slivers of value to optimize your flow.
-Don’t sweat it if you get it wrong, teams often do early on but improve over time.
Exploring Agile Transformation and Scaling Patterns
Exploring Agile Transformation and Scaling PatternsMike Cottmeyer The goal of any enterprise agile adoption strategy is NOT to adopt agile. Companies adopt agile to achieve better business outcomes. Large organizations have no time for dogma and one-size-fits-all thinking when it comes to introducing agile practices. These companies need pragmatic guidance for safely and incrementally introducing structure, principles, and ultimately practices that will result in greater long term, sustainable business results. This talk will introduce a framework for safely, pragmatically, and incrementally introducing agile to help you achieve your business goals.
Story Points Estimation And Planning Poker
Story Points Estimation And Planning PokerDaniel Toader An introduction into basic concepts about agile scrum story point estimation and planning poker. And a simple set of do's and don'ts.
The power to Say NO - Using Scrum in a BAU Team
The power to Say NO - Using Scrum in a BAU TeamMia Horrigan Using Scrum to empower your team during BAU (business as usual) development and maintenance. presentation at the #LAST Conference Melbourne 27 Jul 2012
#LAST (Lean, Agile, Systems Thinking)
Team building presentation ppt.2003
Team building presentation ppt.2003Aliraza Afzal Team building, aliraza afzal, pimsat, preston institute of management science and technologu , zubair shah,presentation to major zubair shah on team building
Relative Estimation: Exercises & Illustrations
Relative Estimation: Exercises & IllustrationsDavid Hanson Why estimate user stories using poker planning? What’s the advantage of relative estimation? Why leverage Fibonacci series?
These slides explore the reasons for relative estimation using Fibonacci through a collection of exercises and illustrations.
Slides assume a basic understanding of user stories and poker planning.
Originally presented as an Agile 101 at Agile New England in May 2023.
Agile Transformation Defined
Agile Transformation DefinedChristoph Mathis Explains the 3 main phases of Agile Transformation identified by the DACH30 exchange group. Contains a definition of the phases of an agile transformation and some glimpses on the education program.
What is psychological safety
What is psychological safetyjhayes8 Psychological safety refers to a culture that fosters taking interpersonal risks at work without fear of negative consequences. When psychological safety exists, teams experience benefits like improved learning, information sharing, and performance. Cultivating psychological safety involves role clarity, peer support, failure tolerance, and equal participation. Google's Project Aristotle found that psychologically safe teams had equal conversational turn-taking and were skilled at discerning others' feelings.
Definition of Ready (XP2011)
Definition of Ready (XP2011)Ken Power The document discusses the definition of ready as it relates to user stories and sprints in agile software development. It provides details on what constitutes a user story being ready, including it being defined, having acceptance criteria, identified dependencies, sized by the team, and more. It also lists criteria for a sprint to be ready, such as the sprint backlog being prioritized and containing all committed work with no hidden work, and all team members having calculated their capacity for the sprint.
Nexus - Scaled Professional Scrum - An introduction
Nexus - Scaled Professional Scrum - An introductionSubrahmaniam S.R.V This document provides an overview of the Nexus framework for scaling Scrum to multiple teams. Nexus introduces an integration team that is responsible for integrating the work of individual Scrum teams and ensuring the definition of done is met at each sprint's integrated increment. It also includes layered ceremonies that coordinate work across teams such as Nexus sprint planning and reviews. The key principles of Scrum like transparency, inspection, and adaptation still apply at scale with Nexus, allowing Scrum to scale fractally through these coordinated practices across multiple teams.
Current Trends in Agile - opening keynote for Agile Israel 2014
Current Trends in Agile - opening keynote for Agile Israel 2014Yuval Yeret Yuval Yeret, AgileSparks’s CTO will give trends overview session – What is hot, what is not, in the lean agile industry/community – with the aim of exposing people and giving a big picture view that places the different trends as well as sessions in the conference into the right context. We will discuss trends like Scaling Agile (SAFe, Less, DAD), DevOps / Continuous Delivery, Modern Management aspects, Modern Change Management approaches such as Open-Agile-Adoption, What is going on in the world of Kanban, Agile Fluency, Technical Safety / Anzeneering, and maybe more.
http://agileisrael2014.com/current-trends-in-agile/
Planning to Stick to the Plan.pdf
Planning to Stick to the Plan.pdfUpraiseSuccess Prioritizing tasks, or planning for them, is one of the biggest strengths of
leaders. They are tasked with re-architecting organizations, and they develop
comprehensive plans to achieve the same. They also ensure they execute the
plan to the best of their abilities, but others get stuck in the planning phase.
Ad
More Related Content
What's hot (20)
[Product Camp 2020] - Níveis de Maturidade em Prod Ops - Thiago Belluf - Favo
[Product Camp 2020] - Níveis de Maturidade em Prod Ops - Thiago Belluf - FavoProduct Camp Brasil [1] Operações de Produto engloba diversas áreas como estratégia, comunicação, processos de desenvolvimento e gestão de pessoas.
[2] Um modelo de maturidade pode ajudar a avaliar o nível atual de uma empresa nessas áreas e identificar prioridades de melhoria.
[3] Um diagnóstico colaborativo, envolvendo diferentes stakeholders, é essencial para traçar um plano de ação que eleve a maturidade de Operações de Produto de forma contínua.
The Challenges of Agile Adoption
The Challenges of Agile AdoptionIntelliware Development Inc. The process of adopting Agile in any organization is challenging in many ways. It is especially challenging in larger organizations because of complex infrastructures, numerous legacy systems and mature organizational cultures. These larger organizations often underestimate the difficulty of getting Agile right.
This presentation will focus on the common challenges of Agile adoption. Tips are provided to help improve the chances of Agile adoption success.
Agile Estimation Techniques
Agile Estimation TechniquesMikalai Alimenkou Presentation from Agile Base Camp conference (Kiev, April 2011) about estimation techniques in Agile teams.
Seven Key Metrics to Improve Agile Performance
Seven Key Metrics to Improve Agile PerformanceTechWell It’s been said: If you can’t measure it, you can’t improve it. For most agile teams burndown charts and some type of velocity measurement are all they are doing. However, with just a few more metrics, you can gain substantial insight into how teams are performing and identify improvement opportunities. Andrew Graves explores seven key metrics―Effort by Class of Service, Accuracy of Estimation, Cost per Point, and four others―to measure how your team is doing and make adjustments in real time. Andrew illustrates how to use these metrics to communicate progress to stakeholders. Discover how to use these metrics to identify and analyze trends that lead to performance improvement ideas and strategies. Learn how to use these seven metrics to monitor the impact of changes made to verify they are bringing the hoped-for difference.
User story and splitting workshop
User story and splitting workshopBrian Sjoberg Do you want to write great User Stories that provide the vehicle for conversation and confirmation that we build the right thing? Do you struggle with splitting stories so that they still provide business value but can be accomplished within a fraction of your iteration? We will do a quick refresher on User Story formatting to include Acceptance Criteria. Additionally we will learn techniques for splitting stories in this interactive workshop.
How to estimate in scrum
How to estimate in scrumGloria Stoilova - Story points are an arbitrary measure used by Scrum teams to estimate the effort required to implement a user story. Teams typically use a Fibonacci sequence like 1, 2, 3, 5, 8, 13, 20, 40, 100.
- Estimating user stories allows teams to plan how many highest priority stories can be completed in a sprint and helps forecast release schedules. The whole team estimates during backlog refinement.
- Stories are estimated once they are small enough to fit in a sprint and acceptance criteria are agreed upon. Teams commonly use planning poker where each member privately assigns a story point value and the team discusses until consensus is reached.
Agile sw development 101
Agile sw development 101Kiwon Kyung 하얀 눈 위에 발자국은 반갑고 친구와 같은 느낌이었던 것 같습니다. 애자일 적용에 첫발을
내딛으려는 팀에게 도움이 되었으면 좋겠네요.
경기원, LG CNS
애자일을 통해 내가 하고 있는 무엇인가를 더 낫게 만들려는 욕심 있는 분들께 추천합니다.
신황규, 삼성SDS
현실을 부정하지 말고 일단 작게 시작하세요.
관찰하고 적응하세요. 특정 방법에 얽매이지 말고 애자일 선언문을 기억하세요. :-D
심우곤, LG전자
어제보다 나은 오늘을 만드는데 도움이 되었으면 좋겠습니다.
이승룡, 삼성SDS
애자일을 적용하려는 팀에 도움이 되었으면 좋겠어요!
채수원, NHN
여러분들이 애자일과 더 친해졌으면 합니다.
황상철, NHN
Agile Estimating & Planning by Amaad Qureshi
Agile Estimating & Planning by Amaad QureshiAmaad Qureshi An introduction to Agile Estimating and how it can be used to measure the size and length of work.
Agile estimating & planning is a way of measuring the size and time it takes to complete a task. This technique is used by Agile teams in Enterprise and can be utilised in the same way by Start-ups not just for software but for all areas of the business. In this talk I will show you how estimating & planning works by:
- Writing effective user stories
- Writing tests to validate stories (acceptance criteria)
- Using story points to work out the size of a task
- Estimating using Planning Poker
- Using Story Points to calculate a team’s velocity (speed of work)
- Using a team’s velocity to calculate project length
The Scrum Master Role
The Scrum Master RoleNigel Thurlow The document outlines the key responsibilities of a Scrum Master which include facilitating transparent communication and self-organization within the team. The Scrum Master aims to help the team adapt quickly to changes, solve problems independently, and create visual reporting tools. Some of the Scrum Master's other responsibilities are to reflect on meetings and ceremonies, ensure definition of done is agreed upon, protect the team from obstacles, and celebrate the team's successes.
User Story Sizing using Agile Relative Estimation
User Story Sizing using Agile Relative EstimationAlex Kanaan, SPC5, CSP, ACC, ATF Ever wonder why Agile teams swear by relative estimation? My teams improved sprint planning efforts by a factor or 3, once we started using relative estimation.
Without understanding Agile relative estimation, teams tend to fall back to using time-based methods. This often leads them to spend way too much time on obsolete estimates that will be made even more complex with all the unknowns and constant emergent requirements of an Agile world!
“It's better to be roughly right, than precisely wrong!”
~ John Maynard Keyenes
The Solution is simple: understand that relative estimation is only a rough order of magnitude estimate to quickly organize the product backlog. This empowers your product owners (PO) to quickly make value based trade-offs on backlog items and decide on what stories the team should work next. This gives the business the highest bang for their buck!
PROBLEMS WITH TIME-BASED ESTIMATES
-Teams spend too much time trying to get it right
-Lack of confidence/experience can lead to people being either optimistic or pessimistic
-Timeline you are estimating may be too far in the future
-Due to long timeline, there are too many risks, unknowns, changes or dependencies!
WHY USE RELATIVE ESTIMATION?
-Allows a quick comparison of stories in the backlog
-Allows you to select a predictable volume of work to do in a sprint
-Uses a simple arbitrary scale
-Allows PO to make trade-offs and take on the most valuable stories next
ESTIMATION TIPS
-Relative points or equivalent Tshirt sizes are used to estimate stories, leveraging the Fibonacci sequence modified for Agile.
-The team estimates the story, not management nor the customer.
-Story estimates account for three things: effort, complexity, and unknowns. Don’t short sell yourself by estimating effort alone, that’s where waterfall projects face issues.
-Remember to estimate all Stories, user stories or technical stories. Even estimate research or discovery spikes.
-Refine your backlog as a team on a continuous basis, to get your stories to meet the Definition of Ready.
-Only pull into your sprint, stories that are refined and estimated.
-Break down stories that are large, into smaller slivers of value to optimize your flow.
-Don’t sweat it if you get it wrong, teams often do early on but improve over time.
Exploring Agile Transformation and Scaling Patterns
Exploring Agile Transformation and Scaling PatternsMike Cottmeyer The goal of any enterprise agile adoption strategy is NOT to adopt agile. Companies adopt agile to achieve better business outcomes. Large organizations have no time for dogma and one-size-fits-all thinking when it comes to introducing agile practices. These companies need pragmatic guidance for safely and incrementally introducing structure, principles, and ultimately practices that will result in greater long term, sustainable business results. This talk will introduce a framework for safely, pragmatically, and incrementally introducing agile to help you achieve your business goals.
Story Points Estimation And Planning Poker
Story Points Estimation And Planning PokerDaniel Toader An introduction into basic concepts about agile scrum story point estimation and planning poker. And a simple set of do's and don'ts.
The power to Say NO - Using Scrum in a BAU Team
The power to Say NO - Using Scrum in a BAU TeamMia Horrigan Using Scrum to empower your team during BAU (business as usual) development and maintenance. presentation at the #LAST Conference Melbourne 27 Jul 2012
#LAST (Lean, Agile, Systems Thinking)
Team building presentation ppt.2003
Team building presentation ppt.2003Aliraza Afzal Team building, aliraza afzal, pimsat, preston institute of management science and technologu , zubair shah,presentation to major zubair shah on team building
Relative Estimation: Exercises & Illustrations
Relative Estimation: Exercises & IllustrationsDavid Hanson Why estimate user stories using poker planning? What’s the advantage of relative estimation? Why leverage Fibonacci series?
These slides explore the reasons for relative estimation using Fibonacci through a collection of exercises and illustrations.
Slides assume a basic understanding of user stories and poker planning.
Originally presented as an Agile 101 at Agile New England in May 2023.
Agile Transformation Defined
Agile Transformation DefinedChristoph Mathis Explains the 3 main phases of Agile Transformation identified by the DACH30 exchange group. Contains a definition of the phases of an agile transformation and some glimpses on the education program.
What is psychological safety
What is psychological safetyjhayes8 Psychological safety refers to a culture that fosters taking interpersonal risks at work without fear of negative consequences. When psychological safety exists, teams experience benefits like improved learning, information sharing, and performance. Cultivating psychological safety involves role clarity, peer support, failure tolerance, and equal participation. Google's Project Aristotle found that psychologically safe teams had equal conversational turn-taking and were skilled at discerning others' feelings.
Definition of Ready (XP2011)
Definition of Ready (XP2011)Ken Power The document discusses the definition of ready as it relates to user stories and sprints in agile software development. It provides details on what constitutes a user story being ready, including it being defined, having acceptance criteria, identified dependencies, sized by the team, and more. It also lists criteria for a sprint to be ready, such as the sprint backlog being prioritized and containing all committed work with no hidden work, and all team members having calculated their capacity for the sprint.
Nexus - Scaled Professional Scrum - An introduction
Nexus - Scaled Professional Scrum - An introductionSubrahmaniam S.R.V This document provides an overview of the Nexus framework for scaling Scrum to multiple teams. Nexus introduces an integration team that is responsible for integrating the work of individual Scrum teams and ensuring the definition of done is met at each sprint's integrated increment. It also includes layered ceremonies that coordinate work across teams such as Nexus sprint planning and reviews. The key principles of Scrum like transparency, inspection, and adaptation still apply at scale with Nexus, allowing Scrum to scale fractally through these coordinated practices across multiple teams.
Similar to Rise and fall of Story Points. Capacity based planning from the trenches. (20)
Current Trends in Agile - opening keynote for Agile Israel 2014
Current Trends in Agile - opening keynote for Agile Israel 2014Yuval Yeret Yuval Yeret, AgileSparks’s CTO will give trends overview session – What is hot, what is not, in the lean agile industry/community – with the aim of exposing people and giving a big picture view that places the different trends as well as sessions in the conference into the right context. We will discuss trends like Scaling Agile (SAFe, Less, DAD), DevOps / Continuous Delivery, Modern Management aspects, Modern Change Management approaches such as Open-Agile-Adoption, What is going on in the world of Kanban, Agile Fluency, Technical Safety / Anzeneering, and maybe more.
http://agileisrael2014.com/current-trends-in-agile/
Planning to Stick to the Plan.pdf
Planning to Stick to the Plan.pdfUpraiseSuccess Prioritizing tasks, or planning for them, is one of the biggest strengths of
leaders. They are tasked with re-architecting organizations, and they develop
comprehensive plans to achieve the same. They also ensure they execute the
plan to the best of their abilities, but others get stuck in the planning phase.
Agile antipatterns: review after 10 years of practice
Agile antipatterns: review after 10 years of practiceMikalai Alimenkou Вот уже более 10 лет Agile движение шагает по Украине и стучится практически в каждую компанию. Но приносят ли новые процессы, принципы и практики реальную практическую пользу? Получается ли изменить к лучшему команды, проекты, компании? Я в роли консультанта за эти 10 лет поработал с более чем 100 компаниями, поэтому повидал много хорошего и плохого. В данном докладе хочется пробежаться по основным проблемам, сложностям и анти-паттернам в переходе отечественных компаний на "Agile рельсы". Мы рассмотрим какие практики не очень хорошо приживаются, от чего страдает большинство команд, какие основные препятствия встречают на своем пути и как умудряются их обходить. Я надеюсь, доклад поможет зародиться множеству интересных дискуссий.
1.How to Prepare FINAL!
1.How to Prepare FINAL!Timothy Dietrich The document provides guidance for managers and supervisors on how to prepare for effective coaching sessions. It includes:
1. A checklist of 5 key steps for preparation: creating an agenda, having tools ready, managing time, taking notes, and setting a professional tone.
2. An activity where participants discuss common distractions and ways to address them.
3. An exercise where participants review agent performance data and outline a coaching session.
The goal is for supervisors to show preparation, have a clear purpose in sessions, and develop action plans to improve agent performance. Effective preparation is important for successful coaching.
How to Apply a Product Mindset to Your Platform Team Tomorrow
How to Apply a Product Mindset to Your Platform Team TomorrowJelmer Borst 5 practical tips to apply for your platform team:
1. Don't build
2. Align with your company's strategy
3. Define and explain your team's value
4. Measure what matters
5. Iterate & celebrate your successes
Agile estimates - Insights about the basic
Agile estimates - Insights about the basicDiogo S. Del Gaudio 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.
:: Agile Scrum Methodology ::
:: Agile Scrum Methodology ::Zubaida Tasmeen Eliza 🇧🇩 “Doing Agile is just a first step; being agile needs to have a totally different mindset, and multidimensional perspectives.”
― Pearl Zhu, Digital Agility: The Rocky Road from Doing Agile to Being Agile
Scrum Master 101
Scrum Master 101David Wallace This document provides an overview of the roles and responsibilities of a Scrum Master compared to a traditional Project Manager in a Waterfall methodology. It describes how a Scrum Master is primarily focused on facilitating Agile ceremonies like planning, daily standups, and retrospectives. Their key responsibilities include removing impediments for the team, coaching them in Agile practices, and helping to manage team dynamics. The document also provides examples of questions for clients and candidates to determine if a Scrum Master role and individual are a good fit.
Facilitate a Timeline Futurespective
Facilitate a Timeline FuturespectiveJolly Rajan This document provides an agenda and instructions for facilitating a futurespective, which is a process for a team to reflect on past challenges and successes and identify action items for improvement. The facilitator will guide the team through gathering data on scenarios they handled well and faced challenges with. They will then group this data into themes, vote on priorities, and decide on specific actions to address the most important topics. The futurespective is intended to help the team gain insights into strengths and weaknesses to improve their performance in future sprints.
Agile camp2016 agile101
Agile camp2016 agile101Erin Bolk The document provides an overview of Agile principles and the Scrum framework. It describes key Scrum roles like the Product Owner and Scrum Master. It also summarizes Scrum ceremonies such as Sprint Planning, Daily Standup, Sprint Review, and Retrospective. User stories and tracking work using a Kanban or Scrum board in TFS are also covered at a high level.
Why using analytics is the only way to sell savings opportunities to the C-suite
Why using analytics is the only way to sell savings opportunities to the C-suiteJames Myers Nick Gunn as our featured speaker, with over 30 years’ experience working at HP/HPE he will be sharing his Tips on how FP&A can use analytics to get the attention of the C-Suite
Creating Valuable PI objectives v1.1.2 - OLD VERSION
Creating Valuable PI objectives v1.1.2 - OLD VERSIONSjoerd Kranendonk This document provides guidance on creating valuable PI Objectives in SAFe organizations. It defines PI Objectives as summaries of business and technical goals for an Agile Release Train (ART) in an upcoming Program Increment (PI). The document outlines benefits like focus, alignment, and learning. It discusses potential struggles and offers templates to help teams craft clear, measurable objectives. Examples demonstrate how to make objectives specific and focus on user/business impact. Metrics and acceptance criteria are emphasized to evaluate if objectives were achieved. Finally, case studies show potential outcomes with and without proper use of PI Objectives.
Agile Project Management
Agile Project ManagementSinaporn (Pam) Suebvisai The document provides an overview of agile project management principles and techniques, including:
1. Agile focuses on individuals, interactions, working software, customer collaboration, and responding to change over rigid processes and contracts.
2. Techniques like user stories, planning poker, prioritization, daily stand-ups, test-driven development, continuous integration, iteration planning and retrospectives help embrace changes and deliver working software frequently.
3. Adopting agile requires starting with easier practices, understanding goals, starting small, and continual improvement through retrospectives to find what works best for each project.
Erp
ErpPalash Biswas This document provides details of a group project for a production management course. It includes an introduction to the project topic, which is examining how ACI Electronics implemented an ERP system. It outlines the project scope, significance, expectations and limitations. It also includes plans for project activities such as work breakdown, scheduling, and communication. Risk management strategies are discussed. Finally, it provides a proposed budget for the project.
Story points vs hours choose wisely; turn the bane of project estimation into...
Story points vs hours choose wisely; turn the bane of project estimation into...Katy Slemon The document discusses the traditional method of estimating projects in hours versus the agile estimation method of using story points. It provides details on both methods, including perceived advantages of story points like being more flexible and collaborative. However, it also notes disadvantages like the potential to misunderstand or misuse story points. The company described, Bacancy Technology, prefers to use hours rather than story points for estimation since it is more straightforward and prevents confusion.
My understanding about Scrum
My understanding about ScrumJason Guo (PMP) 1. The document discusses reasons for adopting an Agile methodology like Scrum, including the need to be flexible and responsive to changing requirements in a dynamic business environment.
2. It provides examples of how Scrum addresses issues with traditional waterfall project management, such as long delivery periods, difficulty incorporating new requirements, and lack of visibility into real progress.
3. Finally, it outlines how to implement Scrum within an organization, including forming cross-functional teams, training, running retrospectives, and improving processes over time.
Backlog Refinement 101 & 202
Backlog Refinement 101 & 202David Hanson Backlog refinement is not a Scrum event, but instead is an ongoing activity during the Sprint required to decompose, describe, estimate, and order backlog items in the Product Backlog.
This material is divided into two sections. The first section reviews the basics of backlog refinement, covering various options for conducting the activity. The second section covers tips for maintaining a healthy backlog and potential anti-patterns.
This material was presented at Agile New England in July and August 2022 as "101" introduction and "202" advanced sessions.
Accelerator Workshop "Before"
Accelerator Workshop "Before"Yvonne Shek Full-day pre-conference workshop given at the IA Summit 2007. This is the slide deck we used during the workshop. See the "after" deck with participants' comments, discussions, work products, etc.
Agile Scrum
Agile ScrumHesham Shabana Why & what is Scrum?
Scrum Artifacts?
Is it ready? Is it done?
The Scrum Team,The Scrum Events
The ys behind the ceremonies
The ys behind the ceremoniesTheAgileDen This document provides an overview of the agenda and purpose of various agile ceremonies, including backlog refinement, daily standup, retrospective, sprint planning, and sprint review. It discusses forming groups to discuss the purpose and desired outcomes of each ceremony. For each ceremony, it lists the purpose as gaining a shared understanding of requirements, identifying uncertainties, negotiating acceptance criteria, prioritizing backlog items, synchronizing work and identifying impediments, reflecting on and improving processes, tasking out sprint work, and demonstrating product increments for feedback. The desired outcomes include estimated backlog items, fewer surprises, elaborated stories, understanding of daily work and impediments, agreed-upon process improvements, a committed sprint plan, and accepted stories and new
Ad
More from Mikalai Alimenkou (20)
Static analysis tools as the best friend of QA
Static analysis tools as the best friend of QAMikalai Alimenkou We have spent many years testing our applications and systems manually and with test automation tools. During this time many bug root causes have been classified and could be detected automatically with special static analysis tools. Most of them could be applied at the early stages of development even before code is integrated into the main development branch. In this talk, I will go through available solutions and demonstrate what kinds of issues may be detected automatically reducing the time and effort of traditional testing.
Modern CI/CD in the microservices world with Kubernetes
Modern CI/CD in the microservices world with KubernetesMikalai Alimenkou In this talk, we will go through the design process of modern CI/CD for the microservices-based system with Kubernetes support. We will discuss how to verify consistency between microservices, apply different levels of quality gates and promote artifacts between environments. Thanks to Kubernetes we will review different approaches of environment resources optimization for development needs during CI/CD cycles.
Saga about distributed business transactions in microservices world
Saga about distributed business transactions in microservices worldMikalai Alimenkou Most of people nowadays think microservices architecture is a great way to build any system. They visit conference talks, read books and review tutorials, where ‘hello world’ applications are built just in several minutes using microservices approach. But the reality is not so wonderful and one of the biggest pain is hidden inside distributed business transactions. In monolith application this topic is almost completely covered with DB level transactions. In distributed world you have to face many issues trying to implement reliable and consistent business logic.
In this talk we will review different types of problems related to distributed business transactions, popular SAGA pattern, frameworks and techniques to simplify your life without compromising quality of the system.
Effectiveness tips from Kubernetes trenches by Captain Obvious
Effectiveness tips from Kubernetes trenches by Captain ObviousMikalai Alimenkou Nowadays almost everybody knows about Kubernetes, some teams are using it and some are only dreaming about it. Despite the popularity, Kubernetes is not simple and there are so many ways of abuse this peaceful technology. In this talk I would like to present quite obvious set of tips, based on failures and ineffectiveness at different companies I have worked with during last several years.
Ride the database in JUnit tests with Database Rider
Ride the database in JUnit tests with Database RiderMikalai Alimenkou For a long time DB related testing in Java world has been a real pain and most developers tried to reduce number of such tests as much as possible. With good in-memory database implementations like H2, schema migration solutions like Liquibase or Flyway, containerization with libraries like TestContainers, database management is now much simpler. But test data management is still a pain. Some developers use SQL dumps, others insert data via JPA/JDBC or rely on prepared data sets. Good old DBUnit may be a good option, but it is not so developer friendly and not adopted well for modern annotations driven development style. Database Rider closes the gap between modern Java development environment and DBUnit, bringing DBUnit closer to your JUnit tests, so database testing will feel like a breeze. In addition to flexible data sets management this library provides other useful features: programmatic data sets definition, leak hunting, data sets export, constraints management, etc. As contributor and loyal user for many years, I would like to share my experience with Database Rider and demonstrate how to make database testing a fun again!
Wastful waste or why everything is so slow in development
Wastful waste or why everything is so slow in developmentMikalai Alimenkou I think almost everybody experienced cases when things are moving very slowly in IT companies or teams. You have many people, talented engineers, Agile process and development speed is still below expectations. We try to focus on performance and efficiency last 10 years, improving our practices and tools. But we are still there in terms of speed when they are applied to real life cases. How is it possible? In this talk we will review the concept of waste circles and understand what are the main sources of time waste in development process. This concept would help you to check your processess, focus on right things and achieve much better results in your organization or team.
Hexagonal architecture with Spring Boot
Hexagonal architecture with Spring BootMikalai Alimenkou The document discusses implementing a hexagonal architecture and domain-driven design approach with Spring Boot. It promotes starting with use cases and domain context, using entities and value objects to model the domain, and aggregates for complex relationships. It also advocates an ports and adapters approach using Spring Boot modules like Spring MVC, Spring Data, and Spring Messaging to connect business logic to databases, queues, APIs and other external services through adapters. The summary emphasizes changing one's perspective to focus on the business logic and domain model first and using existing Spring Boot features to build the technical implementation around it.
Wastful waste or why everything is so slow in development
Wastful waste or why everything is so slow in developmentMikalai Alimenkou I think almost everybody experienced cases when things are moving very slowly in IT companies or teams. You have many people, talented engineers, Agile process and development speed is still below expectations. We try to focus on performance and efficiency last 10 years, improving our practices and tools. But we are still there in terms of speed when they are applied to real life cases. How is it possible? In this talk we will review the concept of waste circles and understand what are the main sources of time waste in development process. This concept would help you to check your processess, focus on right things and achieve much better results in your organization or team.
DevOps checklist or how to understand where is your team in DevOps landscape ...
DevOps checklist or how to understand where is your team in DevOps landscape ...Mikalai Alimenkou DevOps become a buzzword in a last few years. Several companies, development and product teams have achieved quite impressive results in this area making cultural changes, transforming their processes and practices, introducing new roles, tools and techniques.
Do you think is achievable for you team or it’s still a bunch of drama? There is no common approach for measuring achievements and understanding how much DevOps’ich the current team/company is. In this talk I will provide attendees with basic checklist to start with and some reliable tools/techniques to monitor progress of “DevOps transformation”.
DevOps checklist or how to understand where is your team in DevOps landscape
DevOps checklist or how to understand where is your team in DevOps landscapeMikalai Alimenkou DevOps is a hot topic during last several years. Some companies, teams and products have achieved quite impressive results in this area making cultural changes, transforming their processes and practices, introducing new roles, tools and techniques. At the same time there is no common approach for measuring achievements and understanding “how DevOps” the current team/company is. In this talk I will provide attendees with basic checklist to start with and some reliable tools/techniques to monitor progress of “DevOps transformation”.
Практические трудности в разработке Медкарты для целой страны
Практические трудности в разработке Медкарты для целой страныMikalai Alimenkou Почти год мы в Whirl Software разрабатываем систему Медкарта в масштабе целой страны. За это время мы столкнулись с множеством интересных сложностей и проблем, часть из которых успешно победили, а для некоторых хорошего решения до сих пор не найдено. В этом докладе мы поделимся накопленным практическим опытом и некоторыми техническими решениями, которые могут быть полезны в рамках разработки электронных медицинских систем.
Hexagonal architecture with Spring Boot [EPAM Java online conference]![Hexagonal architecture with Spring Boot [EPAM Java online conference]](https://cdn.slidesharecdn.com/ss_thumbnails/hexagonalarchitecturewithspringboot-180925151506-thumbnail.jpg?width=560&fit=bounds)
Hexagonal architecture with Spring Boot [EPAM Java online conference]Mikalai Alimenkou Nowadays traditional layered monolithic architecture in Java world is not so popular as 5-10 years ago. I remember how we wrote tons of code for each layer repeating almost the same parts for every application. Add unit and integration testing to understand how much time and efforts has been spent on repeatable work. All cool ideas around DDD (domain driven design) and Hexagonal Architecture was just a nice theory because reality hasn’t allow us to implement it easily. Even Dependency Injection with Spring framework was completely focused on traditional layered approach, not even talking about JavaEE platform.
Today we have Spring Boot ecosystem covering most of our needs for integration with almost all possible technologies and microservices architectural trend, enabling completely new approach to build Java applications around domain model. It is so natural to build Java domain-oriented services and connect them with external world using ports and adapters, that Hexagonal Architecture is almost enabled by default. You just need to switch your way of thinking…
Bro, manage test data like a pro! [QA Fest 2018]![Bro, manage test data like a pro! [QA Fest 2018]](https://cdn.slidesharecdn.com/ss_thumbnails/bromanagetestdatalikeapro-180922193659-thumbnail.jpg?width=560&fit=bounds)
Bro, manage test data like a pro! [QA Fest 2018]Mikalai Alimenkou This document provides guidance on effectively managing test data for software testing. It discusses 6 approaches to preparing test data: 1) using the user interface, 2) inserting data via API calls, 3) direct SQL insertion into the database, 4) using data sets with DBUnit, 5) versioned data dumps, and 6) reusing production data. The key recommendations are to choose the approach that best fits the system under test, speed up test data management with APIs, reuse live data when possible, and mix strategies as needed to build reliable test cases.
Hexagonal architecture with Spring Boot
Hexagonal architecture with Spring BootMikalai Alimenkou Nowadays traditional layered monolithic architecture in Java world is not so popular as 5-10 years ago. I remember how we wrote tons of code for each layer repeating almost the same parts for every application. Add unit and integration testing to understand how much time and efforts has been spent on repeatable work. All cool ideas around DDD (domain driven design) and Hexagonal Architecture was just a nice theory because reality hasn’t allow us to implement it easily. Even Dependency Injection with Spring framework was completely focused on traditional layered approach, not even talking about JavaEE platform.
Today we have Spring Boot ecosystem covering most of our needs for integration with almost all possible technologies and microservices architectural trend, enabling completely new approach to build Java applications around domain model. It is so natural to build Java domain-oriented services and connect them with external world using ports and adapters, that Hexagonal Architecture is almost enabled by default. You just need to switch your way of thinking…
Bro, manage test data like a pro!
Bro, manage test data like a pro!Mikalai Alimenkou Almost any application or software system manages data. It is hard to imagine test automation that is not affected by this fact. There are many differenct approaches how to prepare system under test, providing predefined test data: use application UI, invoke API methods, run business logic directly, access DB from test scenarios, etc. In this talk we will review most of existing approaches, starting from the easiest and the most popular ones and finishing with really tricky ways to manage your test data for large distributed systems. There is no ideal solution for every case or silver bullet, but I hope your toolset will become wider after visiting this talk.
Бытовая классификация тестировщиков с точки зрения разработчика
Бытовая классификация тестировщиков с точки зрения разработчикаMikalai Alimenkou Тестировщики часто говорят о противостоянии и конфликтах с разработчиками. Но ведь есть команды, где все живут в мире и согласии. Видимо что-то тут не так? Я хочу поговорить о том, как тестировщиков видят сами разработчики. В докладе будет проведена забавная классификация. Кроме известного всем тестировщика-обезьянки будут представлены тестировщик-муха, тестировщик-нацист, тестировщик-панда и многие другие герои. Высможете лишний раз задуматься над тем, как вас видят со стороны и, возможно, изменить ситуацию к лучшему.
Доклад будет также полезен менеджерам проектов и лидерам команд. Вы сможете быстрее распознавать те или иные шаблоны поведения тестировщикови принимать меры по повышению уровня командной работы. Приходите, будет интересно!
Code Review tool for personal effectiveness and waste analysis
Code Review tool for personal effectiveness and waste analysisMikalai Alimenkou Usually it is hard to analyze personal effectiveness and detect wastes in development process because developer’s work decomposition is not transparent and available for analysis. As a good sample of ineffective process imagine developer, who spends 1 day on task implementation and then reimplements it several times according to code review notes during next 2 days. Or another developer, who is waiting for code review during 2 days, switching context to other tasks, finally gets notes and switches back to initial task, trying to refresh all details in his head. And so on and so forth…
Code review tool usage helps to aggregate lots of useful information about any code change at any stage (static analysis, code review, rework, acceptance, integration into main branch). In this talk I’m going to demontrate how this information could be used for detailed analysis of development effectiveness and wastes detection. Based on mentioned analysis you could implement many improvements for your development process and then measure their success.
Funny stories and anti-patterns from DevOps landscape
Funny stories and anti-patterns from DevOps landscapeMikalai Alimenkou During last several years DevOps became strong buzzword used almost in every project, team and company. But almost everywhere it is used in very funny and strange context. For example, existing ops guys are renamed to DevOps just to sell them to the client for more money. Or DevOps is used as new job title for some magically powerful person who is able to operate cloud environment and modern infrastructure related tools, leading team of old school ops and participating in management meetings. In this talk I’m going to review all different anti-patterns and bad practices in DevOps landscape using stories from my personal experience as Delivery Manager and independent consultant.
Developer + tester = quality++
Developer + tester = quality++Mikalai Alimenkou With Agile adoption many things have changed in quality assurance and tester role. Ourdays the whole team is responsible for product quality. But not so many people understand how such high level approaches work in practice, how developer interacts with tester, what stages each task passes on the way from requirements specification to customer acceptance, who is doing what at each stage.
I have met only few teams, where developer and tester work closely together on a daily basis. Some projects try to same money on developer's time, others try to have independent testing team without influence from developers side. Developers also don't understad how tester could help them in practice. But this pair is able to significantly improve product quality and avoid many common issues.
In this talk we will cover motivation behind pair work of develoeper and tester, concrete practices and approaches at different stages, and advantages that both sides could achieve from such work style.
Continuous improvements of developer efficiency with modern IDE
Continuous improvements of developer efficiency with modern IDEMikalai Alimenkou Nowadays IDE are much more intelligent than 10 years ago when they played mainly code editor functions. At the same time number of good practices and techniques is growing from day to day and most developers don’t have time to learn them with the same pace. So it could be a good idea to use IDE as continuous learning tool. In this talk we will cover following areas of developer efficiency: automated refactorings, live templates, useful suggestions, code standards, code navigation, code generation… I hope after this talk your daily job will become much more effective.
Ad
Recently uploaded (20)
Transcript: Canadian book publishing: Insights from the latest salary survey ...
Transcript: Canadian book publishing: Insights from the latest salary survey ...BookNet Canada Join us for a presentation in partnership with the Association of Canadian Publishers (ACP) as they share results from the recently conducted Canadian Book Publishing Industry Salary Survey. This comprehensive survey provides key insights into average salaries across departments, roles, and demographic metrics. Members of ACP’s Diversity and Inclusion Committee will join us to unpack what the findings mean in the context of justice, equity, diversity, and inclusion in the industry.
Results of the 2024 Canadian Book Publishing Industry Salary Survey: https://publishers.ca/wp-content/uploads/2025/04/ACP_Salary_Survey_FINAL-2.pdf
Link to presentation slides and transcript: https://bnctechforum.ca/sessions/canadian-book-publishing-insights-from-the-latest-salary-survey/
Presented by BookNet Canada and the Association of Canadian Publishers on May 1, 2025 with support from the Department of Canadian Heritage.
Heap, Types of Heap, Insertion and Deletion
Heap, Types of Heap, Insertion and DeletionJaydeep Kale This pdf will explain what is heap, its type, insertion and deletion in heap and Heap sort
The Future of Cisco Cloud Security: Innovations and AI Integration
The Future of Cisco Cloud Security: Innovations and AI IntegrationRe-solution Data Ltd Stay ahead with Re-Solution Data Ltd and Cisco cloud security, featuring the latest innovations and AI integration. Our solutions leverage cutting-edge technology to deliver proactive defense and simplified operations. Experience the future of security with our expert guidance and support.
Transcript: #StandardsGoals for 2025: Standards & certification roundup - Tec...
Transcript: #StandardsGoals for 2025: Standards & certification roundup - Tec...BookNet Canada Book industry standards are evolving rapidly. In the first part of this session, we’ll share an overview of key developments from 2024 and the early months of 2025. Then, BookNet’s resident standards expert, Tom Richardson, and CEO, Lauren Stewart, have a forward-looking conversation about what’s next.
Link to recording, presentation slides, and accompanying resource: https://bnctechforum.ca/sessions/standardsgoals-for-2025-standards-certification-roundup/
Presented by BookNet Canada on May 6, 2025 with support from the Department of Canadian Heritage.
AI 3-in-1: Agents, RAG, and Local Models - Brent Laster
AI 3-in-1: Agents, RAG, and Local Models - Brent LasterAll Things Open Presented at All Things Open RTP Meetup
Presented by Brent Laster - President & Lead Trainer, Tech Skills Transformations LLC
Talk Title: AI 3-in-1: Agents, RAG, and Local Models
Abstract:
Learning and understanding AI concepts is satisfying and rewarding, but the fun part is learning how to work with AI yourself. In this presentation, author, trainer, and experienced technologist Brent Laster will help you do both! We’ll explain why and how to run AI models locally, the basic ideas of agents and RAG, and show how to assemble a simple AI agent in Python that leverages RAG and uses a local model through Ollama.
No experience is needed on these technologies, although we do assume you do have a basic understanding of LLMs.
This will be a fast-paced, engaging mixture of presentations interspersed with code explanations and demos building up to the finished product – something you’ll be able to replicate yourself after the session!
#StandardsGoals for 2025: Standards & certification roundup - Tech Forum 2025
#StandardsGoals for 2025: Standards & certification roundup - Tech Forum 2025BookNet Canada Book industry standards are evolving rapidly. In the first part of this session, we’ll share an overview of key developments from 2024 and the early months of 2025. Then, BookNet’s resident standards expert, Tom Richardson, and CEO, Lauren Stewart, have a forward-looking conversation about what’s next.
Link to recording, transcript, and accompanying resource: https://bnctechforum.ca/sessions/standardsgoals-for-2025-standards-certification-roundup/
Presented by BookNet Canada on May 6, 2025 with support from the Department of Canadian Heritage.
Connect and Protect: Networks and Network Security
Connect and Protect: Networks and Network SecurityVICTOR MAESTRE RAMIREZ Connect and Protect: Networks and Network Security
Canadian book publishing: Insights from the latest salary survey - Tech Forum...
Canadian book publishing: Insights from the latest salary survey - Tech Forum...BookNet Canada Join us for a presentation in partnership with the Association of Canadian Publishers (ACP) as they share results from the recently conducted Canadian Book Publishing Industry Salary Survey. This comprehensive survey provides key insights into average salaries across departments, roles, and demographic metrics. Members of ACP’s Diversity and Inclusion Committee will join us to unpack what the findings mean in the context of justice, equity, diversity, and inclusion in the industry.
Results of the 2024 Canadian Book Publishing Industry Salary Survey: https://publishers.ca/wp-content/uploads/2025/04/ACP_Salary_Survey_FINAL-2.pdf
Link to presentation recording and transcript: https://bnctechforum.ca/sessions/canadian-book-publishing-insights-from-the-latest-salary-survey/
Presented by BookNet Canada and the Association of Canadian Publishers on May 1, 2025 with support from the Department of Canadian Heritage.
Make GenAI investments go further with the Dell AI Factory
Make GenAI investments go further with the Dell AI FactoryPrincipled Technologies The cost benefit of implementing a Dell AI Factory solution versus AWS and Azure
Our research shows that hosting GenAI workloads on premises, either in a traditional Dell solution or using managed Dell APEX Subscriptions, could significantly lower your GenAI costs over 4 years compared to hosting these workloads in the cloud. In fact, we found that a Dell AI Factory on-premises solution could reduce costs by at much as 71 percent vs. a comparable AWS SageMaker solution and as much as 61 percent vs. a comparable Azure ML solution. These results show that organizations looking to implement GenAI and reap the business benefits to come can find many advantages in an on-premises Dell AI Factory solution, whether they opt to purchase and manage it themselves or engage with Dell APEX Subscriptions. Choosing an on-premises Dell AI Factory solution could save your organization significantly over hosting GenAI in the cloud, while giving you control over the security and privacy of your data as well as any updates and changes to the environment, and while ensuring your environment is managed consistently.
Build 3D Animated Safety Induction - Tech EHS
Build 3D Animated Safety Induction - Tech EHSTECH EHS Solution Train Smarter, Not Harder – Let 3D Animation Lead the Way!
Discover how 3D animation makes inductions more engaging, effective, and cost-efficient.
Check out the slides to see how you can transform your safety training process!
Slide 1: Why 3D animation changes the game
Slide 2: Site-specific induction isn’t optional—it’s essential
Slide 3: Visitors are most at risk. Keep them safe
Slide 4: Videos beat text—especially when safety is on the line
Slide 5: TechEHS makes safety engaging and consistent
Slide 6: Better retention, lower costs, safer sites
Slide 7: Ready to elevate your induction process?
Can an animated video make a difference to your site's safety? Let's talk.
AI Agents at Work: UiPath, Maestro & the Future of Documents
AI Agents at Work: UiPath, Maestro & the Future of DocumentsUiPathCommunity Do you find yourself whispering sweet nothings to OCR engines, praying they catch that one rogue VAT number? Well, it’s time to let automation do the heavy lifting – with brains and brawn.
Join us for a high-energy UiPath Community session where we crack open the vault of Document Understanding and introduce you to the future’s favorite buzzword with actual bite: Agentic AI.
This isn’t your average “drag-and-drop-and-hope-it-works” demo. We’re going deep into how intelligent automation can revolutionize the way you deal with invoices – turning chaos into clarity and PDFs into productivity. From real-world use cases to live demos, we’ll show you how to move from manually verifying line items to sipping your coffee while your digital coworkers do the grunt work:
📕 Agenda:
🤖 Bots with brains: how Agentic AI takes automation from reactive to proactive
🔍 How DU handles everything from pristine PDFs to coffee-stained scans (we’ve seen it all)
🧠 The magic of context-aware AI agents who actually know what they’re doing
💥 A live walkthrough that’s part tech, part magic trick (minus the smoke and mirrors)
🗣️ Honest lessons, best practices, and “don’t do this unless you enjoy crying” warnings from the field
So whether you’re an automation veteran or you still think “AI” stands for “Another Invoice,” this session will leave you laughing, learning, and ready to level up your invoice game.
Don’t miss your chance to see how UiPath, DU, and Agentic AI can team up to turn your invoice nightmares into automation dreams.
This session streamed live on May 07, 2025, 13:00 GMT.
Join us and check out all our past and upcoming UiPath Community sessions at:
👉 https://community.uipath.com/dublin-belfast/
Reimagine How You and Your Team Work with Microsoft 365 Copilot.pptx
Reimagine How You and Your Team Work with Microsoft 365 Copilot.pptxJohn Moore M365 Community Conference 2025 Workshop on Microsoft 365 Copilot
Generative Artificial Intelligence (GenAI) in Business
Generative Artificial Intelligence (GenAI) in BusinessDr. Tathagat Varma My talk for the Indian School of Business (ISB) Emerging Leaders Program Cohort 9. In this talk, I discussed key issues around adoption of GenAI in business - benefits, opportunities and limitations. I also discussed how my research on Theory of Cognitive Chasms helps address some of these issues
Unlocking Generative AI in your Web Apps
Unlocking Generative AI in your Web AppsMaximiliano Firtman Slides for the session delivered at Devoxx UK 2025 - Londo.
Discover how to seamlessly integrate AI LLM models into your website using cutting-edge techniques like new client-side APIs and cloud services. Learn how to execute AI models in the front-end without incurring cloud fees by leveraging Chrome's Gemini Nano model using the window.ai inference API, or utilizing WebNN, WebGPU, and WebAssembly for open-source models.
This session dives into API integration, token management, secure prompting, and practical demos to get you started with AI on the web.
Unlock the power of AI on the web while having fun along the way!