The document discusses how focusing on finishing work rather than starting new work can improve productivity. It notes that many companies are "drowning in a sea of opportunity" by taking on too much work at once and not completing anything. The document advocates for limiting work in progress to improve flow and focus, balancing demand with throughput, and delivering work frequently to build trust. It provides examples of how multi-tasking reduces efficiency compared to focusing on one task at a time.
The document discusses how companies can improve their technology development processes through adopting Agile and Lean principles. It argues that companies often try to maximize utilization and multi-tasking, which causes waste and slows everything down. Better approaches include focusing on one task at a time to improve flow, limiting work in progress to identify bottlenecks, and balancing demand with throughput. Implementing Kanban techniques like visualizing work and imposing work-in-progress limits can help achieve more efficient flow and frequent delivery of value.
The document discusses how focusing on improving throughput and limiting work in progress can help organizations finish work more quickly. It suggests that companies should balance demand against throughput by throttling input into the system. This will expose bottlenecks and enable the team to try improvements to optimize the whole process and achieve level flow. A Kanban board can be used to visualize and limit work in progress.
After revolutionizing the automobile industry, Lean principles have been successfully applied to different knowledge areas including software development. This workshop is intended to master Lean concepts like Waste, Push&Pull systems, systems thinking,Kaizen etc.! In this interactive game, the participants will work in a small Lego production line, experiencing problems and applying Lean practices to overcome them.
Using Agile and Lean to Stay Ahead in a Tough EconomySally Elatta
This seminar was presented to a group of IT and Business managers and executives on the topic of how to use Agile and Lean methods to stay ahead in the current economic conditions.
Contact me if you would like this presented for your organization.
sally@agiletransformation.com
“Learn about the 4 Key Steps to Application Modernization from Solutions Director Derek Britton along with our customer Jeroen van der Heijden, Chief Technical Officer at Raet. This presentation took place at the Gartner Symposium ITxpo in Barcelona on 7th November 2012.”
Top Ways Agile Adoption Fails, How to Avoid Them!Sally Elatta
This was a webinar I offered to discuss real world reasons behind Agile adoption failure and the success factors for avoiding them. You can watch the video of the webinar here:
Learn about the 4 Key Steps to Application Modernization with Kevin Brearley Product Management Director, joined with our customer Troy Sheeley Senior Project Manager at CSC. This presentation took place at the Gartner Symposium ITxpo in Orlando on 23rd October 2012.”
Amir Barylko gave a presentation to the Agile User Group in April 2011 about agile planning. He discussed why projects fail, the agile manifesto and principles, estimating work using story points and planning poker, and how to structure an agile project using iterations. He emphasized quality, visual communication, and metrics like burn down charts to manage projects agilely.
The document discusses how companies can improve their technology development processes through adopting Agile and Lean principles. It argues that companies often try to maximize utilization and multi-tasking, which causes waste and slows everything down. Better approaches include focusing on one task at a time to improve flow, limiting work in progress to identify bottlenecks, and balancing demand with throughput. Implementing Kanban techniques like visualizing work and imposing work-in-progress limits can help achieve more efficient flow and frequent delivery of value.
The document discusses how focusing on improving throughput and limiting work in progress can help organizations finish work more quickly. It suggests that companies should balance demand against throughput by throttling input into the system. This will expose bottlenecks and enable the team to try improvements to optimize the whole process and achieve level flow. A Kanban board can be used to visualize and limit work in progress.
After revolutionizing the automobile industry, Lean principles have been successfully applied to different knowledge areas including software development. This workshop is intended to master Lean concepts like Waste, Push&Pull systems, systems thinking,Kaizen etc.! In this interactive game, the participants will work in a small Lego production line, experiencing problems and applying Lean practices to overcome them.
Using Agile and Lean to Stay Ahead in a Tough EconomySally Elatta
This seminar was presented to a group of IT and Business managers and executives on the topic of how to use Agile and Lean methods to stay ahead in the current economic conditions.
Contact me if you would like this presented for your organization.
sally@agiletransformation.com
“Learn about the 4 Key Steps to Application Modernization from Solutions Director Derek Britton along with our customer Jeroen van der Heijden, Chief Technical Officer at Raet. This presentation took place at the Gartner Symposium ITxpo in Barcelona on 7th November 2012.”
Top Ways Agile Adoption Fails, How to Avoid Them!Sally Elatta
This was a webinar I offered to discuss real world reasons behind Agile adoption failure and the success factors for avoiding them. You can watch the video of the webinar here:
Learn about the 4 Key Steps to Application Modernization with Kevin Brearley Product Management Director, joined with our customer Troy Sheeley Senior Project Manager at CSC. This presentation took place at the Gartner Symposium ITxpo in Orlando on 23rd October 2012.”
Amir Barylko gave a presentation to the Agile User Group in April 2011 about agile planning. He discussed why projects fail, the agile manifesto and principles, estimating work using story points and planning poker, and how to structure an agile project using iterations. He emphasized quality, visual communication, and metrics like burn down charts to manage projects agilely.
This document contains a series of unflattering evaluations and insults about an employee or employees. Some key points made in the evaluations include that the employee has reached rock bottom, works only when closely supervised, has low standards that they fail to achieve, and lacks basic cognitive functions or intelligence. Many of the evaluations are only 1-2 sentences, containing insults but little substantive feedback.
The document discusses the product backlog in Scrum. It defines the product backlog as the master list of all functionality desired in the product, prioritized by the product owner. The product backlog allows requirements to grow and change as more is learned about customers and the product. It also contains descriptions of features, benefits, and user stories to capture requirements for the product.
Behavior-Driven Development, or BDD, is an excellent development strategy that can help bridge the traditional gap between requirements and implementation. This talk will go discuss the basic principles of Behavior Driven Development, and look at how it builds on and differs from “traditional” Test-Driven Development. This session will demo two BDD tools: JDave, an open source framework that incorporates BDD concepts into JUnit, and easyb, a DSL-based behavior driven development framework for Java that uses Groovy to let you pretty much write tests that document themselves.
Overview of Agile for Business AnalystsSally Elatta
This seminar was presented to the IIBA Omaha group. My goal was to provide a quick overview of Agile and then dive into the role and skills needed for a BA on an Agile team. Let me know if you would like me to present this or a similar topic at your organization. sally@agiletransformation.com
What is 'Just Enough' Documentation in Agile?Sally Elatta
There are lots of misconceptions around what Agile says about documentation. One is that Agile has NO Documentation! That brings a smile to a few folks and drives others (like me) crazy! If you’ve read anything about Agile, you’ll hear that what it really preaches is ‘Just In Time’ or ‘Just Enough’ documentation. So what does that mean? Why aim for ‘Just Enough’ and not ‘Perfect’ Documentation? This seminar was presented at the IIBA group.
Want this seminar presented at YOUR organization? just email sally@agiletransformation.com
Yes, both of them are buzz words, but when you peel back the buzz, what is the true value that lies behind both of these methods? How do they compare and how do they differ? Most importantly, how can we bring about Agility to SOA projects and how can better architecture be applied to Agile projects? Me and Kyle also discussed some of the challenges with attempting iterative development on SOA projects and provided some ways both can leverage each other's strengths.
Want this seminar presented at YOUR organization? just email sally@agiletransformation.com
www.AgileTransformation.com
Chasing code quality in huge multi-location team projectAgile Lietuva
The document discusses challenges with maintaining code quality in large, multi-location development teams and outlines solutions implemented at Exigen Services. It describes setting up separate continuous integration environments for each team to isolate changes and failures. A process of code reviews before automated merging to the central repository is also implemented to ensure all code is reviewed before affecting other teams. Specific tools like Mercurial, Jenkins, ReviewBoard and Sonar are highlighted.
Next Level Agile - David Hawks - Keep Austin Agile 2018Agile Velocity
Today most Agile teams are trying to achieve predictable, fast delivery. While that’s good, it’s no longer good enough—not if we want to keep up in this highly competitive, rapidly changing world. It’s not just about teams anymore. Next Level Agility is about the ability of entire organizations to quickly adapt to market changes.
In his Keep Austin Agile 2018 session, David Hawks shared principles and practices that are the future of Agile organizations. Together, he and the audience reset the bar on how great Agile organizations operate by moving beyond practices like user stories, project plans, stakeholder feedback, continuous integration, and velocity, and towards a new Next Level Agile Manifesto with an emphasis on Discovery over Execution.
Learn to identify organizational impediments keeping you from breaking through to the next level. Attendees walked away from this session with concrete practices needed in order to support this new way of working.
Agile Velocity - Deliver double the value in half the timeDavid Hawks
Learn practical techniques to guide your teams and escape the top 6 traps preventing organizations from realizing the full benefits of agile.
64% of product features built in software development are rarely or never used. Too many teams focus on increasing the amount of output. Not enough teams focus on delivering the most value with the least amount of output. In this interactive presentation, David Hawks will share the key factors that sabotage product success and what to do about it. Learn practical tools and techniques that accelerate learning throughout the product development cycle to deliver double the value in half the time.
Deliver double the value in half the timeDavid Hawks
The document discusses how to deliver double the value in half the time through agile principles and practices. It identifies common problems such as making decisions too early, long feedback cycles, lack of prioritization, and lack of focus. Solutions proposed include deferring decisions, frequent validation of work, limiting work in progress, focusing on completing work rather than starting new work, and prioritizing the backlog. Adopting these agile practices can help teams deliver 80% of value in 20% of the time.
The document introduces Behavior Driven Development (BDD) and describes how the author implemented BDD practices at their company to help a development team meet an aggressive production goal of completing 550 story points by the end of the year. Key aspects of the introduction included establishing acceptance criteria and executable specifications for features, conducting regular release planning and backlog grooming sessions, and emphasizing exploratory testing over ad-hoc testing. Feedback loops and close collaboration between development and business partners were crucial to successfully adopting the new approach.
HP Discover Session BB2160: Agile DevOps Continuous DeliveryCapgemini
This document discusses how businesses need faster time-to-market and time-to-value for new functionality. It outlines challenges with traditional waterfall development approaches and notes that Agile development helps but that releasing software still takes too long. HP Software solutions for continuous delivery, DevOps, and automation are presented to help bridge the gaps between development and operations for faster software releases while maintaining quality. These include solutions for lab management, application release acceleration, and enterprise collaboration.
Agile and Startups - What can go wrong - a Case study (Presented at ExpoQA 20...Vipin Jain
I recently got this wonderful opportunity to present a case study "Agile and Startups - What can go wrong" at ExpoQA, Madrid. The talk is about how startups think, build on the idea and try to sell it, until it is influenced by external factors like market and competitors. A lack of strong product owner didnt help as well. Agile, is a technology and is prone to failure as well, until it is practiced right.
The document discusses next level agility and how organizations can achieve it. It outlines five stages of agility maturity from superficial to fast. Next level agility provides benefits like faster time to value, organizational agility, and quicker validation of ideas. Six practices are presented to help organizations level up: serving customers over stakeholders, using hypotheses over requirements, objective decision making, goal-driven investment, continuous release, and measuring value over velocity. The document concludes by matching each practice to the values it impacts most.
This document introduces the Scaled Agile Framework (SAFe) as an approach for applying Agile and Lean principles at an enterprise scale. It discusses how traditional development methods are not keeping pace with increasing software complexity. SAFe is presented as a proven framework that harnesses the power of Agile for large software enterprises through elements like Agile teams, program execution, alignment, code quality, and scaling practices up to the portfolio level. The document advocates for SAFe's ability to accelerate value delivery, make money faster, deliver better customer fit, and reduce risk through approaches like continuous delivery, cadenced development, and synchronizing teams.
User Stories Suck by David Hawks at North Dallas Product Owners MeetupAgile Velocity
The User Story concept was invented almost 20 years ago, it’s time for an update. This outdated process supports an old way of working focused on predictable requirements delivery instead of product discovery. Wouldn’t you like to know much earlier which features are not going to be valued by your market? We need techniques that shorten the feedback loop with customers, not stakeholders. We need to prioritize based on riskiest assumptions and iterate quickly through small experiments in order to (in)validate our ideas as fast as possible.
SITA underwent an agile transformation journey from an initial state of confusion to exploration and finally commitment. In the initial state, management, customers and delivery teams had many questions around how agile would work. Through education on agile principles and practices, forming cross-functional teams, and exploring new ways of working, confusion started to reduce. In the state of exploration, focus shifted to customer collaboration, continuous delivery, addressing changes through "exchange requests", and exploring new techniques like behavior driven development. Finally, in the state of commitment, principles of customer satisfaction, social responsibility, continuous improvement, and one-button deployments became guiding lights for working in an agile way.
This document summarizes how the author introduced Behavior Driven Development (BDD) at their company. It describes using BDD basics like acceptance criteria and executable specifications to collaborate more closely with business stakeholders. It also discusses overcoming challenges through open communication, learning together in small experiments, and building trust between technical and business teams.
This document discusses building high performing agile teams. It provides tips on embracing continuous improvement, managing backlogs and task boards, conducting effective story kickoffs, addressing defects early, embracing test-driven development, and constantly seeking to improve processes through lean principles. The presentation was given by Naveed Khawaja and Carl Bruiners and provides advice based on their experience helping organizations adopt agile practices.
This document contains a series of unflattering evaluations and insults about an employee or employees. Some key points made in the evaluations include that the employee has reached rock bottom, works only when closely supervised, has low standards that they fail to achieve, and lacks basic cognitive functions or intelligence. Many of the evaluations are only 1-2 sentences, containing insults but little substantive feedback.
The document discusses the product backlog in Scrum. It defines the product backlog as the master list of all functionality desired in the product, prioritized by the product owner. The product backlog allows requirements to grow and change as more is learned about customers and the product. It also contains descriptions of features, benefits, and user stories to capture requirements for the product.
Behavior-Driven Development, or BDD, is an excellent development strategy that can help bridge the traditional gap between requirements and implementation. This talk will go discuss the basic principles of Behavior Driven Development, and look at how it builds on and differs from “traditional” Test-Driven Development. This session will demo two BDD tools: JDave, an open source framework that incorporates BDD concepts into JUnit, and easyb, a DSL-based behavior driven development framework for Java that uses Groovy to let you pretty much write tests that document themselves.
Overview of Agile for Business AnalystsSally Elatta
This seminar was presented to the IIBA Omaha group. My goal was to provide a quick overview of Agile and then dive into the role and skills needed for a BA on an Agile team. Let me know if you would like me to present this or a similar topic at your organization. sally@agiletransformation.com
What is 'Just Enough' Documentation in Agile?Sally Elatta
There are lots of misconceptions around what Agile says about documentation. One is that Agile has NO Documentation! That brings a smile to a few folks and drives others (like me) crazy! If you’ve read anything about Agile, you’ll hear that what it really preaches is ‘Just In Time’ or ‘Just Enough’ documentation. So what does that mean? Why aim for ‘Just Enough’ and not ‘Perfect’ Documentation? This seminar was presented at the IIBA group.
Want this seminar presented at YOUR organization? just email sally@agiletransformation.com
Yes, both of them are buzz words, but when you peel back the buzz, what is the true value that lies behind both of these methods? How do they compare and how do they differ? Most importantly, how can we bring about Agility to SOA projects and how can better architecture be applied to Agile projects? Me and Kyle also discussed some of the challenges with attempting iterative development on SOA projects and provided some ways both can leverage each other's strengths.
Want this seminar presented at YOUR organization? just email sally@agiletransformation.com
www.AgileTransformation.com
Chasing code quality in huge multi-location team projectAgile Lietuva
The document discusses challenges with maintaining code quality in large, multi-location development teams and outlines solutions implemented at Exigen Services. It describes setting up separate continuous integration environments for each team to isolate changes and failures. A process of code reviews before automated merging to the central repository is also implemented to ensure all code is reviewed before affecting other teams. Specific tools like Mercurial, Jenkins, ReviewBoard and Sonar are highlighted.
Next Level Agile - David Hawks - Keep Austin Agile 2018Agile Velocity
Today most Agile teams are trying to achieve predictable, fast delivery. While that’s good, it’s no longer good enough—not if we want to keep up in this highly competitive, rapidly changing world. It’s not just about teams anymore. Next Level Agility is about the ability of entire organizations to quickly adapt to market changes.
In his Keep Austin Agile 2018 session, David Hawks shared principles and practices that are the future of Agile organizations. Together, he and the audience reset the bar on how great Agile organizations operate by moving beyond practices like user stories, project plans, stakeholder feedback, continuous integration, and velocity, and towards a new Next Level Agile Manifesto with an emphasis on Discovery over Execution.
Learn to identify organizational impediments keeping you from breaking through to the next level. Attendees walked away from this session with concrete practices needed in order to support this new way of working.
Agile Velocity - Deliver double the value in half the timeDavid Hawks
Learn practical techniques to guide your teams and escape the top 6 traps preventing organizations from realizing the full benefits of agile.
64% of product features built in software development are rarely or never used. Too many teams focus on increasing the amount of output. Not enough teams focus on delivering the most value with the least amount of output. In this interactive presentation, David Hawks will share the key factors that sabotage product success and what to do about it. Learn practical tools and techniques that accelerate learning throughout the product development cycle to deliver double the value in half the time.
Deliver double the value in half the timeDavid Hawks
The document discusses how to deliver double the value in half the time through agile principles and practices. It identifies common problems such as making decisions too early, long feedback cycles, lack of prioritization, and lack of focus. Solutions proposed include deferring decisions, frequent validation of work, limiting work in progress, focusing on completing work rather than starting new work, and prioritizing the backlog. Adopting these agile practices can help teams deliver 80% of value in 20% of the time.
The document introduces Behavior Driven Development (BDD) and describes how the author implemented BDD practices at their company to help a development team meet an aggressive production goal of completing 550 story points by the end of the year. Key aspects of the introduction included establishing acceptance criteria and executable specifications for features, conducting regular release planning and backlog grooming sessions, and emphasizing exploratory testing over ad-hoc testing. Feedback loops and close collaboration between development and business partners were crucial to successfully adopting the new approach.
HP Discover Session BB2160: Agile DevOps Continuous DeliveryCapgemini
This document discusses how businesses need faster time-to-market and time-to-value for new functionality. It outlines challenges with traditional waterfall development approaches and notes that Agile development helps but that releasing software still takes too long. HP Software solutions for continuous delivery, DevOps, and automation are presented to help bridge the gaps between development and operations for faster software releases while maintaining quality. These include solutions for lab management, application release acceleration, and enterprise collaboration.
Agile and Startups - What can go wrong - a Case study (Presented at ExpoQA 20...Vipin Jain
I recently got this wonderful opportunity to present a case study "Agile and Startups - What can go wrong" at ExpoQA, Madrid. The talk is about how startups think, build on the idea and try to sell it, until it is influenced by external factors like market and competitors. A lack of strong product owner didnt help as well. Agile, is a technology and is prone to failure as well, until it is practiced right.
The document discusses next level agility and how organizations can achieve it. It outlines five stages of agility maturity from superficial to fast. Next level agility provides benefits like faster time to value, organizational agility, and quicker validation of ideas. Six practices are presented to help organizations level up: serving customers over stakeholders, using hypotheses over requirements, objective decision making, goal-driven investment, continuous release, and measuring value over velocity. The document concludes by matching each practice to the values it impacts most.
This document introduces the Scaled Agile Framework (SAFe) as an approach for applying Agile and Lean principles at an enterprise scale. It discusses how traditional development methods are not keeping pace with increasing software complexity. SAFe is presented as a proven framework that harnesses the power of Agile for large software enterprises through elements like Agile teams, program execution, alignment, code quality, and scaling practices up to the portfolio level. The document advocates for SAFe's ability to accelerate value delivery, make money faster, deliver better customer fit, and reduce risk through approaches like continuous delivery, cadenced development, and synchronizing teams.
User Stories Suck by David Hawks at North Dallas Product Owners MeetupAgile Velocity
The User Story concept was invented almost 20 years ago, it’s time for an update. This outdated process supports an old way of working focused on predictable requirements delivery instead of product discovery. Wouldn’t you like to know much earlier which features are not going to be valued by your market? We need techniques that shorten the feedback loop with customers, not stakeholders. We need to prioritize based on riskiest assumptions and iterate quickly through small experiments in order to (in)validate our ideas as fast as possible.
SITA underwent an agile transformation journey from an initial state of confusion to exploration and finally commitment. In the initial state, management, customers and delivery teams had many questions around how agile would work. Through education on agile principles and practices, forming cross-functional teams, and exploring new ways of working, confusion started to reduce. In the state of exploration, focus shifted to customer collaboration, continuous delivery, addressing changes through "exchange requests", and exploring new techniques like behavior driven development. Finally, in the state of commitment, principles of customer satisfaction, social responsibility, continuous improvement, and one-button deployments became guiding lights for working in an agile way.
This document summarizes how the author introduced Behavior Driven Development (BDD) at their company. It describes using BDD basics like acceptance criteria and executable specifications to collaborate more closely with business stakeholders. It also discusses overcoming challenges through open communication, learning together in small experiments, and building trust between technical and business teams.
This document discusses building high performing agile teams. It provides tips on embracing continuous improvement, managing backlogs and task boards, conducting effective story kickoffs, addressing defects early, embracing test-driven development, and constantly seeking to improve processes through lean principles. The presentation was given by Naveed Khawaja and Carl Bruiners and provides advice based on their experience helping organizations adopt agile practices.
The document summarizes a presentation on Agile Testing for a software development group. The presentation covered the textbook definition of Agile Testing, focusing on doing the simplest tests to verify functionality and quality standards. It also discussed the street version, emphasizing establishing a quality philosophy throughout the team. Finally, it discussed challenges such as finding the right testing resources and preventing work from being "thrown over the wall" to testing without proper communication between teams.
Agile testing for agile sparks kanban clientsYuval Yeret
The document discusses agile testing practices like continuous integration, test automation, and behavior driven development. It emphasizes delivering working, tested software frequently through smaller batches and providing early feedback. Automating tests is part of the definition of done to enable continuous integration. Quality assurance experts focus on riskier areas like performance and security testing rather than manual testing. Behavior driven development uses examples and acceptance tests to drive development and automation. Technical debt can be addressed incrementally by automating tests for new features and riskier areas first.
PCA14: Accelerate Learning and Overcome the 6 Traps of AgileDavid Hawks
The document discusses 6 common traps that teams fall into when working in an agile way. These traps are: 1) making decisions too early and locking them in, 2) not having a shared understanding of purpose, 3) long feedback cycles with no validation, 4) being overwhelmed by opportunities, 5) not getting work fully completed ("done"), and 6) treating all work as equally important. For each trap, the document provides examples and proposes solutions like deferring decisions, using user story mapping, employing lean startup principles, limiting work in progress, focusing on completion over features, and prioritizing work. The overall message is that teams need to accelerate learning, deliver value faster, and avoid these traps in order to be
What got you here as a leader is not going to get you to the next level. Faster rate of disruption and a new workforce dynamic are demanding leaders to work differently.
In this presentatation at Agile Leadership Fest, David Hawks walked through key mindset shifts leaders need to make to thrive in this new world.
This document provides an introduction to Agile Scrum project management methodology and advocates for fully transforming JDE enterprise portfolio implementations from the traditional Waterfall methodology to Agile Scrum. It begins by sharing the author's experience with Agile Scrum and describes some of its key benefits over Waterfall. The core of Agile Scrum is described, including sprint cycles, daily stand-up meetings, and artifacts like product backlogs and sprint backlogs. Case examples are provided and Scrum roles are outlined. The document argues that Agile Scrum is better suited than Waterfall for JDE implementations and that only a full transformation, not partial adoption, will realize its benefits.
The document discusses several agile practices for sustainable change including:
1) Using A3 problem solving templates and Deming's plan-do-check-act cycle for continuous improvement.
2) Empowering cross-functional teams to make decisions and prioritizing delivering valuable work iteratively through time boxed iterations and a backlog of user stories.
3) Daily stand-ups for team members to share progress and obstacles, and using consensus-based techniques like "fist of five" for decisions.
4) Having product owners define and ensure delivery of valuable products in iterations to maximize speed to value.
Similar to Agile Velocity Stop Starting. Start Finishing. PMI - Austin (20)
The document discusses problems organizations face and solutions to increase engagement and agility. It addresses three main problems: focusing only on output, a changed workforce, and lack of engagement. To solve these, the document recommends self-organizing teams with autonomy, servant leadership, daily huddles and visual boards for collaboration, and regular retrospectives. This allows teams to prioritize work in a backlog and finish projects through user stories.
The document is a presentation on overcoming six traps of Agile. It discusses making decisions too early and locking them in. It advocates deferring decisions to the last responsible moment to avoid this trap. It also discusses teams not having a shared understanding of their purpose and advocates shifting from a requirements delivery process to a requirements discovery process through techniques like user story mapping. The presentation provides examples of how to address these common Agile traps.
The document discusses 10 common pitfalls that can occur during an agile transformation. The first pitfall is thinking agile is just a process change rather than a cultural shift. Other pitfalls include providing no guidance during the transformation, leadership not being properly aligned, transparency being abused, and organizational culture remaining misaligned after the transition to agile. The document stresses the importance of establishing a continuous improvement culture, aligning teams to products and customers, and gaining organizational alignment across the entire company for a successful agile transformation.
The document discusses problems with leadership and engagement in the modern workforce. It proposes that self-organizing teams with servant leaders who support rather than dictate can lead to better outcomes and engagement. Regular retrospectives, visibility of work, and team prioritization of backlogs can help with collaboration, alignment and finishing work to satisfy stakeholders through shortened feedback loops. The key is balancing servant leadership, team ownership and visibility to drive engagement, innovation and improvement.
Agile velocity - Requirements Discovery Presentation David Hawks
1. The document discusses challenges with user stories and provides strategies for splitting stories into smaller pieces.
2. It then covers how agile practices like Scrum can help with execution and testing, while lean startup practices aid discovery and learning from customers.
3. The key message is that teams should seek to shorten the learning cycle by treating requirements as hypotheses and getting customer feedback quickly through methods like paper prototyping and explainer videos.
Would you like to be able to increase the adoption rate of your product? In this session, we will introduce you to cutting edge concepts and techniques to shift your product development process from output to outcome driven. We will combine elements of Lean Startup, Product Discovery, and Experiment Driven Development to accelerate learning to quickly build products customer love.
In this interactive workshop, David Hawks will share best practices for writing user stories, acceptance criteria, the INVEST approach, and breaking down user stories. Using these approaches you will be able to effectively convey your vision to the development team so they can output what you want.
This document outlines an agenda for a session on the role of coaching and building trust within teams. The agenda includes: defining coaching; aligning teams around goals and values; building trust; and creating an action plan. It discusses tools for coaching, common team dysfunctions, and conducting an exercise to assess team trust. Methods are presented for improving trust through sharing experiences, open communication, and establishing team values. The document provides guidance and exercises for teams to identify their core and aspirational values, as well as intrinsic motivators. It emphasizes taking action to demonstrate that values matter in building an aligned, high-trust team.
KAA: Deliver Double the Value in Half the TimeDavid Hawks
The document discusses six common traps that teams can fall into when working in an agile way. These traps are: making decisions too early and locking them in; not having a shared understanding of purpose; long or no feedback cycles; being overwhelmed by opportunities; not actually getting to a "done" state for features; and treating everything as equally important. It provides strategies for overcoming each trap, such as deferring decisions, using user story mapping, implementing lean startup and MVP approaches, focusing on highest value work, defining "done" rigorously, and prioritizing work.
PCA14: Intro to agile for product managersDavid Hawks
This document provides an introduction to agile development for product managers. It discusses some key differences between traditional waterfall development and empirical agile processes. The document also outlines the scrum process, including product owner responsibilities like maintaining the product backlog and collaborating with stakeholders. It emphasizes that working software is the primary measure of progress in agile.
Agile Austin - Deliver Double the Value in Half the TimeDavid Hawks
Learn practical techniques to guide your teams and escape the top 6 traps preventing organizations from realizing the full benefits of agile.
64% of product features built in software development are rarely or never used. Too many teams focus on increasing the amount of output. Not enough teams focus on delivering the most value with the least amount of output. In this interactive presentation, David Hawks will share the key factors that sabotage product success and what to do about it. Learn practical tools and techniques that accelerate learning throughout the product development cycle to deliver double the value in half the time.
Deliver Double the Value in Half the TimeDavid Hawks
This session was presented at the PMI Austin Development Day Conference in Sept 2014. We explore the difference between "Doing Agile" vs. "Being Agile." Establishing a learning culture is critical. Six problems are presented and solutions are shown which lead to the team's ability to deliver double the value in half the time.
Deliver Double the Value in Half the Time - PCA13 - PCATXDavid Hawks
64% of product features built in software development are rarely or never used. Too many teams focus on increasing the amount of output, as opposed to focusing on delivering the most value with the least amount of output. In this interactive presentation, David Hawks will share the key factors that sabotage product success and what to do about it. Learn practical tools and techniques that accelerate learning throughout the product development cycle to deliver double the value in half the time.
Presented at ProductCamp Austin 13 on August 2nd, 2014
David Hawks is a Certified Scrum Coach and Certified Scrum Trainer. David guides software organizations to deliver innovative products faster. David brings his broad experience working with Fortune 50 companies and early stage startups to challenge organizations to think differently about how they build products.
KAA How to get your Good agile teams to GreatDavid Hawks
The document provides tips for getting an agile team from good to great by focusing on outcomes over outputs, allocating time to incremental improvements to reduce technical debt, and limiting work in progress to focus on finishing projects instead of starting new ones in order to deliver value earlier. The presentation also discusses building trust, handling conflicts constructively, establishing team values and policies, and developing team members' breadth and depth of skills.
In this session you will learn what is Agile and how it compares to traditional waterfall development. We will also explore the advantages of Agile for increasing visibility and shortening the feedback loop. Then we will introduce you to Scrum, the most popular agile process improvement framework. We will finish with a description of the Product Owner role and its involvement in Scrum.
David Hawks is a Certified Scrum Coach and Certified Scrum Trainer. He founded Agile Velocity when he noticed companies ineffectively building innovative software products. David brings his broad experience working with Fortune 50 companies and early stage startups to challenge organizations to think differently about how they build software.
How to Keep Going Fast - Agile Velocity - Product Camp AustinDavid Hawks
Features often get delivered quickly on new software projects and slow to an exponentially slower pace over time. Teams are usually on their own to discover, implement, and even get buy-in for improving the technical capability to deliver. In this session we'll discuss how technical debt accrues and impacts the flow of features over time as well as how Product Owners can encourage and support teams to improve. We will run a simulation of a software project that demonstrates the impact of employing technical practices and addressing other technical debt.
Agile Velocity Story Mapping Session from Product Camp Austin 11 #PCATXDavid Hawks
User Story Mapping is a technique for organizing and prioritizing user stories. It addresses challenges with traditional backlogs by providing context and showing relationships between stories. The process shifts from requirements delivery to requirements discovery, recognizing that customers discover wants and developers discover solutions as things change. User story mapping decomposes user tasks into smaller tasks and organizes them into activities to form user stories. It is collaborative and fosters co-ownership by helping understand the user perspective and test for gaps by walking through the map.
TrustArc Webinar - 2024 Global Privacy SurveyTrustArc
How does your privacy program stack up against your peers? What challenges are privacy teams tackling and prioritizing in 2024?
In the fifth annual Global Privacy Benchmarks Survey, we asked over 1,800 global privacy professionals and business executives to share their perspectives on the current state of privacy inside and outside of their organizations. This year’s report focused on emerging areas of importance for privacy and compliance professionals, including considerations and implications of Artificial Intelligence (AI) technologies, building brand trust, and different approaches for achieving higher privacy competence scores.
See how organizational priorities and strategic approaches to data security and privacy are evolving around the globe.
This webinar will review:
- The top 10 privacy insights from the fifth annual Global Privacy Benchmarks Survey
- The top challenges for privacy leaders, practitioners, and organizations in 2024
- Key themes to consider in developing and maintaining your privacy program
Programming Foundation Models with DSPy - Meetup SlidesZilliz
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.
5th LF Energy Power Grid Model Meet-up SlidesDanBrown980551
5th Power Grid Model Meet-up
It is with great pleasure that we extend to you an invitation to the 5th Power Grid Model Meet-up, scheduled for 6th June 2024. This event will adopt a hybrid format, allowing participants to join us either through an online Mircosoft Teams session or in person at TU/e located at Den Dolech 2, Eindhoven, Netherlands. The meet-up will be hosted by Eindhoven University of Technology (TU/e), a research university specializing in engineering science & technology.
Power Grid Model
The global energy transition is placing new and unprecedented demands on Distribution System Operators (DSOs). Alongside upgrades to grid capacity, processes such as digitization, capacity optimization, and congestion management are becoming vital for delivering reliable services.
Power Grid Model is an open source project from Linux Foundation Energy and provides a calculation engine that is increasingly essential for DSOs. It offers a standards-based foundation enabling real-time power systems analysis, simulations of electrical power grids, and sophisticated what-if analysis. In addition, it enables in-depth studies and analysis of the electrical power grid’s behavior and performance. This comprehensive model incorporates essential factors such as power generation capacity, electrical losses, voltage levels, power flows, and system stability.
Power Grid Model is currently being applied in a wide variety of use cases, including grid planning, expansion, reliability, and congestion studies. It can also help in analyzing the impact of renewable energy integration, assessing the effects of disturbances or faults, and developing strategies for grid control and optimization.
What to expect
For the upcoming meetup we are organizing, we have an exciting lineup of activities planned:
-Insightful presentations covering two practical applications of the Power Grid Model.
-An update on the latest advancements in Power Grid -Model technology during the first and second quarters of 2024.
-An interactive brainstorming session to discuss and propose new feature requests.
-An opportunity to connect with fellow Power Grid Model enthusiasts and users.
A Comprehensive Guide to DeFi Development Services in 2024Intelisync
DeFi represents a paradigm shift in the financial industry. Instead of relying on traditional, centralized institutions like banks, DeFi leverages blockchain technology to create a decentralized network of financial services. This means that financial transactions can occur directly between parties, without intermediaries, using smart contracts on platforms like Ethereum.
In 2024, we are witnessing an explosion of new DeFi projects and protocols, each pushing the boundaries of what’s possible in finance.
In summary, DeFi in 2024 is not just a trend; it’s a revolution that democratizes finance, enhances security and transparency, and fosters continuous innovation. As we proceed through this presentation, we'll explore the various components and services of DeFi in detail, shedding light on how they are transforming the financial landscape.
At Intelisync, we specialize in providing comprehensive DeFi development services tailored to meet the unique needs of our clients. From smart contract development to dApp creation and security audits, we ensure that your DeFi project is built with innovation, security, and scalability in mind. Trust Intelisync to guide you through the intricate landscape of decentralized finance and unlock the full potential of blockchain technology.
Ready to take your DeFi project to the next level? Partner with Intelisync for expert DeFi development services today!
Trusted Execution Environment for Decentralized Process MiningLucaBarbaro3
Presentation of the paper "Trusted Execution Environment for Decentralized Process Mining" given during the CAiSE 2024 Conference in Cyprus on June 7, 2024.
For the full video of this presentation, please visit: https://www.edge-ai-vision.com/2024/06/temporal-event-neural-networks-a-more-efficient-alternative-to-the-transformer-a-presentation-from-brainchip/
Chris Jones, Director of Product Management at BrainChip , presents the “Temporal Event Neural Networks: A More Efficient Alternative to the Transformer” tutorial at the May 2024 Embedded Vision Summit.
The expansion of AI services necessitates enhanced computational capabilities on edge devices. Temporal Event Neural Networks (TENNs), developed by BrainChip, represent a novel and highly efficient state-space network. TENNs demonstrate exceptional proficiency in handling multi-dimensional streaming data, facilitating advancements in object detection, action recognition, speech enhancement and language model/sequence generation. Through the utilization of polynomial-based continuous convolutions, TENNs streamline models, expedite training processes and significantly diminish memory requirements, achieving notable reductions of up to 50x in parameters and 5,000x in energy consumption compared to prevailing methodologies like transformers.
Integration with BrainChip’s Akida neuromorphic hardware IP further enhances TENNs’ capabilities, enabling the realization of highly capable, portable and passively cooled edge devices. This presentation delves into the technical innovations underlying TENNs, presents real-world benchmarks, and elucidates how this cutting-edge approach is positioned to revolutionize edge AI across diverse applications.
Let's Integrate MuleSoft RPA, COMPOSER, APM with AWS IDP along with Slackshyamraj55
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.
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!
Digital Marketing Trends in 2024 | Guide for Staying AheadWask
https://www.wask.co/ebooks/digital-marketing-trends-in-2024
Feeling lost in the digital marketing whirlwind of 2024? Technology is changing, consumer habits are evolving, and staying ahead of the curve feels like a never-ending pursuit. This e-book is your compass. Dive into actionable insights to handle the complexities of modern marketing. From hyper-personalization to the power of user-generated content, learn how to build long-term relationships with your audience and unlock the secrets to success in the ever-shifting digital landscape.
leewayhertz.com-AI in predictive maintenance Use cases technologies benefits ...alexjohnson7307
Predictive maintenance is a proactive approach that anticipates equipment failures before they happen. At the forefront of this innovative strategy is Artificial Intelligence (AI), which brings unprecedented precision and efficiency. AI in predictive maintenance is transforming industries by reducing downtime, minimizing costs, and enhancing productivity.
zkStudyClub - LatticeFold: A Lattice-based Folding Scheme and its Application...Alex Pruden
Folding is a recent technique for building efficient recursive SNARKs. Several elegant folding protocols have been proposed, such as Nova, Supernova, Hypernova, Protostar, and others. However, all of them rely on an additively homomorphic commitment scheme based on discrete log, and are therefore not post-quantum secure. In this work we present LatticeFold, the first lattice-based folding protocol based on the Module SIS problem. This folding protocol naturally leads to an efficient recursive lattice-based SNARK and an efficient PCD scheme. LatticeFold supports folding low-degree relations, such as R1CS, as well as high-degree relations, such as CCS. The key challenge is to construct a secure folding protocol that works with the Ajtai commitment scheme. The difficulty, is ensuring that extracted witnesses are low norm through many rounds of folding. We present a novel technique using the sumcheck protocol to ensure that extracted witnesses are always low norm no matter how many rounds of folding are used. Our evaluation of the final proof system suggests that it is as performant as Hypernova, while providing post-quantum security.
Paper Link: https://eprint.iacr.org/2024/257
Generating privacy-protected synthetic data using Secludy and MilvusZilliz
During this demo, the founders of Secludy will demonstrate how their system utilizes Milvus to store and manipulate embeddings for generating privacy-protected synthetic data. Their approach not only maintains the confidentiality of the original data but also enhances the utility and scalability of LLMs under privacy constraints. Attendees, including machine learning engineers, data scientists, and data managers, will witness first-hand how Secludy's integration with Milvus empowers organizations to harness the power of LLMs securely and efficiently.
Skybuffer SAM4U tool for SAP license adoptionTatiana Kojar
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.
Ivanti’s Patch Tuesday breakdown goes beyond patching your applications and brings you the intelligence and guidance needed to prioritize where to focus your attention first. Catch early analysis on our Ivanti blog, then join industry expert Chris Goettl for the Patch Tuesday Webinar Event. There we’ll do a deep dive into each of the bulletins and give guidance on the risks associated with the newly-identified vulnerabilities.
Driving Business Innovation: Latest Generative AI Advancements & Success StorySafe Software
Are you ready to revolutionize how you handle data? Join us for a webinar where we’ll bring you up to speed with the latest advancements in Generative AI technology and discover how leveraging FME with tools from giants like Google Gemini, Amazon, and Microsoft OpenAI can supercharge your workflow efficiency.
During the hour, we’ll take you through:
Guest Speaker Segment with Hannah Barrington: Dive into the world of dynamic real estate marketing with Hannah, the Marketing Manager at Workspace Group. Hear firsthand how their team generates engaging descriptions for thousands of office units by integrating diverse data sources—from PDF floorplans to web pages—using FME transformers, like OpenAIVisionConnector and AnthropicVisionConnector. This use case will show you how GenAI can streamline content creation for marketing across the board.
Ollama Use Case: Learn how Scenario Specialist Dmitri Bagh has utilized Ollama within FME to input data, create custom models, and enhance security protocols. This segment will include demos to illustrate the full capabilities of FME in AI-driven processes.
Custom AI Models: Discover how to leverage FME to build personalized AI models using your data. Whether it’s populating a model with local data for added security or integrating public AI tools, find out how FME facilitates a versatile and secure approach to AI.
We’ll wrap up with a live Q&A session where you can engage with our experts on your specific use cases, and learn more about optimizing your data workflows with AI.
This webinar is ideal for professionals seeking to harness the power of AI within their data management systems while ensuring high levels of customization and security. Whether you're a novice or an expert, gain actionable insights and strategies to elevate your data processes. Join us to see how FME and AI can revolutionize how you work with data!
HCL Notes and Domino License Cost Reduction in the World of DLAUpanagenda
Webinar Recording: https://www.panagenda.com/webinars/hcl-notes-and-domino-license-cost-reduction-in-the-world-of-dlau/
The introduction of DLAU and the CCB & CCX licensing model caused quite a stir in the HCL community. As a Notes and Domino customer, you may have faced challenges with unexpected user counts and license costs. You probably have questions on how this new licensing approach works and how to benefit from it. Most importantly, you likely have budget constraints and want to save money where possible. Don’t worry, we can help with all of this!
We’ll show you how to fix common misconfigurations that cause higher-than-expected user counts, and how to identify accounts which you can deactivate to save money. There are also frequent patterns that can cause unnecessary cost, like using a person document instead of a mail-in for shared mailboxes. We’ll provide examples and solutions for those as well. And naturally we’ll explain the new licensing model.
Join HCL Ambassador Marc Thomas in this webinar with a special guest appearance from Franz Walder. It will give you the tools and know-how to stay on top of what is going on with Domino licensing. You will be able lower your cost through an optimized configuration and keep it low going forward.
These topics will be covered
- Reducing license cost by finding and fixing misconfigurations and superfluous accounts
- How do CCB and CCX licenses really work?
- Understanding the DLAU tool and how to best utilize it
- Tips for common problem areas, like team mailboxes, functional/test users, etc
- Practical examples and best practices to implement right away
11. Examplesthis Costs Resulting from Long Cycle Time
I need to know if of
estimate you gave me
last month is still
accurate.
But I workedtime to
I don’t have on that Can you take a
I’ll check with Jim OK. don’t think you by
Yes,I’ll get defect, and
I it’s a it to this
fix it allweeks ago! I’ll
three properly now. look at this? I
when he get’s back. Monday, I’mthison the
I’ve built all in valid
requirement is other
I’ll do a quick fix and
have to read through think it’s a defect.
He’s away for a few weekendtopis it?
stuff more, of it!
any on anyway.
tidy it up later.
the code again.
days.
Project
Manager
Analyst Developer Tester
Knowledge decay
+ increase in the cost of fixing defects
+ reduced quality
+ information becomes stale and needs rework
+ delays accumulate
= reduced customer value
getKanban.com
Couple questions?Who is working with software development teams?Who is employing Agile Methods?Who is using Scrum?Who is using Kanban?Who has heard of Kanban before?Give aways at the end. Let them choose which class they want a 50% discount on. Random person and who tweets
Many software companies are drowning in a sea of opportunity and instead of focusing on getting the highest value items done we are crippled by trying to do too much at one time.http://www.123rf.com/photo_8127859_single-hand-of-drowning-man-in-sea-asking-for-help.html
3m
What is the impact of change in the left vs the right?Change – underestimatedChange – new high priority requirementWhich plan will have the biggest impact if there is a change?
15 minsTeam breakout then highlights as a group
15 minsTeam breakout then highlights as a group
15 minsTeam breakout then highlights as a group
http://www.123rf.com/photo_7850401_young-male-student-is-overwhelmed-by-way-too-many-homework-assignments.htmlRequestsLack of resourcesDon’t trust that project will ever get started (maybe that is the right business decision)Sr leadership not setting priorities
http://twinpowerment.blogspot.com/
Why waste effort trying to order the input when there is no dependability in the order of delivery? Until this is fixed, management time is better used to focus on improving both the ability to deliver and the predictability of delivery.
Set the rate at which we accept new requirements into our software development pipe to correspond with the rate at which we can deliver working code.Once you balance demand against throughput and limit the work-in-progress within your value stream, magic will happen. Only the bottleneck resources will remain fully loaded. Very quickly, other workers in the value stream will find they have slack capacity. Meanwhile, those working in the bottleneck will be busy, but not swamped. For the first time, perhaps in years, the team will no longer be overloaded and many people will experience something very rare in their careers, the feeling of having time on their hands.Limit WIP in andLevel Flow will:Expose the bottlenecksEnable improvementSimplifies prioritizationWhy waste effort trying to order the input when there is no dependability in the order of delivery? Until this is fixed, management time is better used to focus on improving both the ability to deliver and the predictability of delivery.
Need to throttle the input (demand) into the system
The slack capacity created by the act of limiting work-in-progress and pulling new work only as capacity is available will enable improvement no one thought was possible.By throttling the input (demand) into the systemThis will limit the Work In Progress and Level Flow Which will expose the bottlenecksAnd enable improvementOnce you balance demand against throughput and limit the work-in-progress within your value stream, magic will happen. Only the bottleneck resources will remain fully loaded. Very quickly, other workers in the value stream will find they have slack capacity. Meanwhile, those working in the bottleneck will be busy, but not swamped. For the first time, perhaps in years, the team will no longer be overloaded and many people will experience something very rare in their careers, the feeling of having time on their hands.Limit WIP in andLevel Flow will:Expose the bottlenecksEnable improvementSimplifies prioritizationWhy waste effort trying to order the input when there is no dependability in the order of delivery? Until this is fixed, management time is better used to focus on improving both the ability to deliver and the predictability of delivery.
Buy a Feature
Does this feel like the dev process? Dev and QA?
Do we ever have any built up queue in front of QA?Gets continually slower
Slow down A to 5 items/ min (reduce Dev resources)Put B before A Double B Resources (hire more QA)Reallocate resources from A to B to level the flow (TDD or Dev help QA?)
Prioritization is no longer about ordering all the WIP or all initiatives but picking the next one as one finishes
draw card walls to show the activities that happen to the work rather than specific functions or job descriptions.The first school of thought says do not try to second-guess the location of bottleneck or the source of variability that will require a buffer. Rather, implement the system and wait for the bottleneck to reveal itself, then make changes to introduce a buffer. A variant on this suggests that WIP limits should be set
Couple questions?Who is working with software development teams?Who is employing Agile Methods?Who is using Scrum?Who is using Kanban?Who has heard of Kanban before?Give aways at the end. Let them choose which class they want a 50% discount on. Random person and who tweets