What's this thing called "pull" - Mary PoppendieckAGILEMinds
This document discusses the transition from a push to a pull model of production. It summarizes the experience of a video cassette plant that was struggling until it switched from an MRP push system to a just-in-time pull system. The plant went from reliably shipping 60% of its weekly plan under MRP to shipping 95% after adopting pull and filling orders in 2 weeks instead of 6 with no expediting needed. It also discusses how pull systems create strategic inflection points that change how businesses operate.
This document discusses factors important for competitiveness, including reducing lead times. It defines various lead times and emphasizes reducing non-value added time to improve responsiveness to customers. The document also covers 5S standards, waste elimination, and continuous improvement principles like standardizing work and ongoing inspection.
- The team transitioned from Scrum to a Kanban system with no iterations to address issues like lack of continuous delivery and pressure to complete all work by the end of each sprint.
- They implemented Kanban practices like limiting work in progress, just-in-time planning, and decoupling demos from sprints. This improved focus and flow of work.
- Over time, new challenges emerged as the team grew and split into two teams, and business stakeholders had different preferences around estimating work. The engagement ended as the teams refined their Kanban approach to maintenance further.
ManpowerGroup Solutions helped insurance company P&V replace 1,600 workstations across two sites within a tight timeframe by providing additional personnel through outsourcing. They planned and coordinated the entire project efficiently, moving 800 workstations in one location ahead of schedule and replacing 800 aging computers in another location 3 weeks early. P&V appreciated ManpowerGroup Solutions' assurances that replacement staff could be deployed quickly if needed and their transparent pricing structure.
The document discusses the concepts of agile development. It provides definitions and perspectives from agile experts on what agile is and key principles such as iterative development, minimum viable products, emergent design, collaboration, and self-organization. Agile values individuals, interactions, working software, and responding to change over processes, tools, documentation, and plans.
This document discusses lean software development principles. It emphasizes eliminating waste and non-value adding activities from development processes. It defines value and waste from a customer perspective. It also discusses mapping the end-to-end value stream to identify improvement opportunities like reducing cycle times and increasing efficiency. A case study example shows how responding to critical defects can be improved through applying lean principles.
The document discusses the evolution of agile development approaches over time from a contract focus to a development focus and now toward a customer focus. It notes agile has reached an "inflection point" where the focus has shifted from processes to interactions and working software, and now toward customer collaboration and initiating change. The document advocates for approaches like validated learning and customer discovery to ensure development focuses on building the right solution to meet customer needs.
What's this thing called "pull" - Mary PoppendieckAGILEMinds
This document discusses the transition from a push to a pull model of production. It summarizes the experience of a video cassette plant that was struggling until it switched from an MRP push system to a just-in-time pull system. The plant went from reliably shipping 60% of its weekly plan under MRP to shipping 95% after adopting pull and filling orders in 2 weeks instead of 6 with no expediting needed. It also discusses how pull systems create strategic inflection points that change how businesses operate.
This document discusses factors important for competitiveness, including reducing lead times. It defines various lead times and emphasizes reducing non-value added time to improve responsiveness to customers. The document also covers 5S standards, waste elimination, and continuous improvement principles like standardizing work and ongoing inspection.
- The team transitioned from Scrum to a Kanban system with no iterations to address issues like lack of continuous delivery and pressure to complete all work by the end of each sprint.
- They implemented Kanban practices like limiting work in progress, just-in-time planning, and decoupling demos from sprints. This improved focus and flow of work.
- Over time, new challenges emerged as the team grew and split into two teams, and business stakeholders had different preferences around estimating work. The engagement ended as the teams refined their Kanban approach to maintenance further.
ManpowerGroup Solutions helped insurance company P&V replace 1,600 workstations across two sites within a tight timeframe by providing additional personnel through outsourcing. They planned and coordinated the entire project efficiently, moving 800 workstations in one location ahead of schedule and replacing 800 aging computers in another location 3 weeks early. P&V appreciated ManpowerGroup Solutions' assurances that replacement staff could be deployed quickly if needed and their transparent pricing structure.
The document discusses the concepts of agile development. It provides definitions and perspectives from agile experts on what agile is and key principles such as iterative development, minimum viable products, emergent design, collaboration, and self-organization. Agile values individuals, interactions, working software, and responding to change over processes, tools, documentation, and plans.
This document discusses lean software development principles. It emphasizes eliminating waste and non-value adding activities from development processes. It defines value and waste from a customer perspective. It also discusses mapping the end-to-end value stream to identify improvement opportunities like reducing cycle times and increasing efficiency. A case study example shows how responding to critical defects can be improved through applying lean principles.
The document discusses the evolution of agile development approaches over time from a contract focus to a development focus and now toward a customer focus. It notes agile has reached an "inflection point" where the focus has shifted from processes to interactions and working software, and now toward customer collaboration and initiating change. The document advocates for approaches like validated learning and customer discovery to ensure development focuses on building the right solution to meet customer needs.
We usually think of agility for software development — agility allows a small team to produce valuable software.
However, this is not the only place for agility. In this talk Dan discusses the «layering» of agility in a software- focused organization.
This layering starts at the bottom, with Agile Software Development (the writing of quality code), and ends at the top, with Agile Portfolio Management (the management of Projects, Programs, and Products for the good of the Organization).
In this (non-technical, yet entertaining) talk Dan develops a big picture showing how all the pieces fit together in a logical model.
Zend provides expert PHP delivery through best practices for development, deployment, and management. It helps improve developer productivity with tools like Zend Studio, trains developers, and ensures quality and speed through a consistent PHP stack. Zend also helps optimize performance, enable faster releases, and reduce problem resolution times.
Enterprise Product Set Introductory customer presentation. An introduction to the new Micro Focus Enterprise product set, released 2012, taken from the webinar of the same name, August 2012. For more information see www.microfocus.com
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.”
“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.”
An overview of the current state of Scrum, as well as some major challenges that will determine the future state of Scrum.
This is presented from the perspective of Capgemini, knowing that it is in line with the Scrum communities. Included is the current offering of Scrum trainings by Capgemini.
Can MVP help Government innovate like a Startup?aboobier
Presentation I gave to GOVIS, 2012 in Weelington New Zealand on how Minimum Viable Product can help Government innovate like a Lean Start Up. It's all in the Business Model !
The document discusses managing software debt through continuous quality assurance practices. It covers different types of software debt like technical debt, quality debt, and design debt. It emphasizes establishing clear definitions of done for tasks and releases to assert quality. Automating tests through practices like test-driven development and continuous integration can significantly reduce costs by making testing more efficient. Focusing on quality practices upfront helps reduce technical barriers and costs of making changes over the long run.
David Anderson, author of the recent book, Kanban appeared on the Business901 podcast and added 50 minutes of Kanban discussion. David covered a lot of ground in this discussion and answered a lot of questions for me that his book raised. David is a thought leader in managing highly effective software teams. He is President of David J. Anderson & Associates, based in Seattle, Washington, a management consulting firm dedicated to improving leadership in the IT and software development sector
1. Business value engineering (BVE) aims to continuously deliver more business value to customers through incremental improvements. It takes a learning approach focused on understanding customer needs.
2. Agile specifications provide just enough documentation for developers to implement user stories, typically being developed for one or a few user stories at a time. The content is determined by the team and improves over time based on feedback.
3. BVE and agile specifications work together when product owners work with stakeholders to develop specifications in sprints before stories, ensuring developers understand needs while avoiding unnecessary documentation. Continuous feedback improves the process.
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
Among Oracle database administrators (DBAs), "Agile" is widely regarded as a dirty word, a synonym for "sloppy programming." But in the most commercially and technically successful projects I've ever worked on, the principles of the Agile Manifesto have defined our work (specifically, the implementation of the Agile Manifesto called Extreme Programming (XP), as explained by Kent Beck). In fact, further than that: the principles of Agile, implemented as XP, have profoundly enriched my entire life—not just professionally, but personally. The contradiction between the typical DBA's perception of "Agile" and my own is, thus, stunning.
This session describes my experiences with Agile values and our implementation of them. I describe the circumstances that have led me to believe passionately that it's XP that will best assure the success of my projects. I describe what has worked for me and why, and I describe what hasn't worked and why.
The document discusses testing in an Agile context. It presents an agenda on finding issues earlier using Agile methods, the effects of quality debt, definitions of done, quality dashboards, and Agile test and integration strategies like acceptance test-driven development. It also covers managing configuration debt and questions.
The document discusses managing the fuzzy front end of new product development projects. It describes the fuzzy front end as the early ideation and concept development stage with high uncertainty. It highlights the importance of the project manager in bringing structure and process to the fuzzy front end to effectively evaluate ideas and make investment commitments. The presentation provides strategies for project managers to create an innovative climate, align ideas with business objectives, and iterate concepts through assessment and stakeholder presentations.
Earned Value Management and Agile Tips for Success Brent Barton
As the Department of Defense focuses on "delivering 75% solutions in months [instead of] 100% solutions in years" Agile is finding its way into big, traditionally managed programs. This event http://www.afei.org/events/2A01/Pages/default.aspx specifically addresses Agile in Defense. This presentation was an invitation following a successful meeting at the ADAPT meeting.
The document describes a case study involving a time-and-materials contract between Dave, a division engineering manager, and XRI, a vendor, to develop a new system with the goal of keeping costs down. Over 18 months, the author and Harold, a senior engineer, work with the XRI development team on a monthly basis. In the end, the system is delivered on time and saves the plant half its costs in the first month, making Harold a hero. The contract approach of frequent delivery, assessment and adjustment of requirements allows the project to be successful despite initial uncertainties.
Integrating Quality into Project Portfolio ManagementChris Sterling
Traditionally, projects are managed based on cost, schedule, and scope. This continues to be insufficient and leads to poor outcomes, unsustainable development efforts, quality issues, and software that may meet requirements but not the expectations of users. This talk will go into how organizations can integrate quality and value considerations into their portfolio management strategies leading to less surprises and more valuable outcomes. The talk will go into detail about how Agile, Lean thinking, and Managing Software Debt can give a more holistic view of the project portfolio.
This document describes how a company used Scrum practices to rebuild critical software over eight months while also addressing the needs and concerns of senior management. They assigned two Certified Scrum Masters, one to lead development and one to manage communication. They tracked performance data to update estimates and forecasts regularly. By reporting trends in a transparent, data-driven manner they earned trust and showed progress, satisfying both those embracing change and those wanting results.
We usually think of agility for software development — agility allows a small team to produce valuable software.
However, this is not the only place for agility. In this talk Dan discusses the «layering» of agility in a software- focused organization.
This layering starts at the bottom, with Agile Software Development (the writing of quality code), and ends at the top, with Agile Portfolio Management (the management of Projects, Programs, and Products for the good of the Organization).
In this (non-technical, yet entertaining) talk Dan develops a big picture showing how all the pieces fit together in a logical model.
Zend provides expert PHP delivery through best practices for development, deployment, and management. It helps improve developer productivity with tools like Zend Studio, trains developers, and ensures quality and speed through a consistent PHP stack. Zend also helps optimize performance, enable faster releases, and reduce problem resolution times.
Enterprise Product Set Introductory customer presentation. An introduction to the new Micro Focus Enterprise product set, released 2012, taken from the webinar of the same name, August 2012. For more information see www.microfocus.com
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.”
“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.”
An overview of the current state of Scrum, as well as some major challenges that will determine the future state of Scrum.
This is presented from the perspective of Capgemini, knowing that it is in line with the Scrum communities. Included is the current offering of Scrum trainings by Capgemini.
Can MVP help Government innovate like a Startup?aboobier
Presentation I gave to GOVIS, 2012 in Weelington New Zealand on how Minimum Viable Product can help Government innovate like a Lean Start Up. It's all in the Business Model !
The document discusses managing software debt through continuous quality assurance practices. It covers different types of software debt like technical debt, quality debt, and design debt. It emphasizes establishing clear definitions of done for tasks and releases to assert quality. Automating tests through practices like test-driven development and continuous integration can significantly reduce costs by making testing more efficient. Focusing on quality practices upfront helps reduce technical barriers and costs of making changes over the long run.
David Anderson, author of the recent book, Kanban appeared on the Business901 podcast and added 50 minutes of Kanban discussion. David covered a lot of ground in this discussion and answered a lot of questions for me that his book raised. David is a thought leader in managing highly effective software teams. He is President of David J. Anderson & Associates, based in Seattle, Washington, a management consulting firm dedicated to improving leadership in the IT and software development sector
1. Business value engineering (BVE) aims to continuously deliver more business value to customers through incremental improvements. It takes a learning approach focused on understanding customer needs.
2. Agile specifications provide just enough documentation for developers to implement user stories, typically being developed for one or a few user stories at a time. The content is determined by the team and improves over time based on feedback.
3. BVE and agile specifications work together when product owners work with stakeholders to develop specifications in sprints before stories, ensuring developers understand needs while avoiding unnecessary documentation. Continuous feedback improves the process.
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
Among Oracle database administrators (DBAs), "Agile" is widely regarded as a dirty word, a synonym for "sloppy programming." But in the most commercially and technically successful projects I've ever worked on, the principles of the Agile Manifesto have defined our work (specifically, the implementation of the Agile Manifesto called Extreme Programming (XP), as explained by Kent Beck). In fact, further than that: the principles of Agile, implemented as XP, have profoundly enriched my entire life—not just professionally, but personally. The contradiction between the typical DBA's perception of "Agile" and my own is, thus, stunning.
This session describes my experiences with Agile values and our implementation of them. I describe the circumstances that have led me to believe passionately that it's XP that will best assure the success of my projects. I describe what has worked for me and why, and I describe what hasn't worked and why.
The document discusses testing in an Agile context. It presents an agenda on finding issues earlier using Agile methods, the effects of quality debt, definitions of done, quality dashboards, and Agile test and integration strategies like acceptance test-driven development. It also covers managing configuration debt and questions.
The document discusses managing the fuzzy front end of new product development projects. It describes the fuzzy front end as the early ideation and concept development stage with high uncertainty. It highlights the importance of the project manager in bringing structure and process to the fuzzy front end to effectively evaluate ideas and make investment commitments. The presentation provides strategies for project managers to create an innovative climate, align ideas with business objectives, and iterate concepts through assessment and stakeholder presentations.
Earned Value Management and Agile Tips for Success Brent Barton
As the Department of Defense focuses on "delivering 75% solutions in months [instead of] 100% solutions in years" Agile is finding its way into big, traditionally managed programs. This event http://www.afei.org/events/2A01/Pages/default.aspx specifically addresses Agile in Defense. This presentation was an invitation following a successful meeting at the ADAPT meeting.
The document describes a case study involving a time-and-materials contract between Dave, a division engineering manager, and XRI, a vendor, to develop a new system with the goal of keeping costs down. Over 18 months, the author and Harold, a senior engineer, work with the XRI development team on a monthly basis. In the end, the system is delivered on time and saves the plant half its costs in the first month, making Harold a hero. The contract approach of frequent delivery, assessment and adjustment of requirements allows the project to be successful despite initial uncertainties.
Integrating Quality into Project Portfolio ManagementChris Sterling
Traditionally, projects are managed based on cost, schedule, and scope. This continues to be insufficient and leads to poor outcomes, unsustainable development efforts, quality issues, and software that may meet requirements but not the expectations of users. This talk will go into how organizations can integrate quality and value considerations into their portfolio management strategies leading to less surprises and more valuable outcomes. The talk will go into detail about how Agile, Lean thinking, and Managing Software Debt can give a more holistic view of the project portfolio.
This document describes how a company used Scrum practices to rebuild critical software over eight months while also addressing the needs and concerns of senior management. They assigned two Certified Scrum Masters, one to lead development and one to manage communication. They tracked performance data to update estimates and forecasts regularly. By reporting trends in a transparent, data-driven manner they earned trust and showed progress, satisfying both those embracing change and those wanting results.
The document summarizes a presentation by Dan Rawsthorne on the role of the Product Owner in Scrum. It discusses that the Product Owner is accountable for what the Scrum team builds and optimizing its value. The responsibilities of the Product Owner include providing vision and goals, prioritizing the product backlog, and releasing valuable products. It emphasizes that the Product Owner is a core member of the Scrum team and works to guide the team towards achieving the product goals.
Doing agile with an ISO-20000 Telco (AgilePT 2015)Manuel Padilha
A story from the trenches regarding a software project developed for a Telco company. The challenges faced while dealing with a mostly Agile customer that is part of a larger company with heavily defined processes.
The "way out" and how to deliver working software with close to zero spec and still complying to project management requirements, customer timings and own company budget.
[mobiconf 2014] Shazam mobile apps - Data Driven Project ManagementTomasz Kustrzynski MSc
Shazam has been growing very fast recently. A lot of this growth happened in the engineering department at London HQ where our mobile apps are being developed.
This talk will go into technicalities of project management techniques we use to keep 100+ MAU a month happy while maintain agility and respond to rapidly changing market situation.
We will talk about data driven Kanban, flow, visual standups, changing requirements and structure of our teams. We will show what metrics we care about, how we measure them and what we do with the results.
You should expect some observations about development of state of art apps useful from product/project manager’s and developer’s perspective.
This document summarizes Roy Wu's experience introducing Scrum to a project team at CloudyBay, a company that develops weather and disaster information systems. It discusses some common "Scrum Buts" or challenges project teams face when adopting Scrum. Some examples included lacking a clear Product Owner role, not having a ScrumMaster, and not defining a Sprint Goal. The document outlines Roy's views on Scrum and agile from the perspective of the Cynefin framework. It also describes small group discussions where teams shared their Scrum Buts and lessons learned as a ScrumMaster.
The document discusses the principles behind the Agile Manifesto and provides examples of patterns and anti-patterns related to adopting Agile practices. It begins by listing the 12 principles from the Agile Manifesto, including delivering working software frequently and valuing customer collaboration over contract negotiation. The document then analyzes scenarios to determine whether team decisions align with or contradict Agile principles, and suggests more aligned approaches when needed.
The document discusses Agile development principles and practices. It provides 3 key points:
1. Agile development puts the product owner, representing the customer or business, in control of determining what features are developed. This allows customers to change priorities and react quickly to changing market needs.
2. Agile provides transparency into the development process for customers. It engages customers throughout development to provide better understanding and reduce feelings of helplessness.
3. Agile puts the development team in control of how features are developed. Teams are self-organizing to determine the best approaches.
Agile in Practice An Agile Success Story February 2.docxnettletondevon
Agile in Practice
An Agile Success
Story
February 2012
2
Agile in Practice - An Agile Success Story
Contents
Overview
1
Why
Agile
2
How
We
Did
Agile
4
SCRUM-‐derived
Model
4
Distributed
Teams
5
Planning
6
Execution
7
Documentation
7
Reporting
8
Lessons
Learned
11
What
Worked
11
What
We
Could
Have
Done
Better
11
1 Agile in Practice - An Agile Success Story
Overview
Our client serves about 10,000 clients worldwide. Their aging platform was
proving to be inefficient, difficult and expensive to adapt to the changing needs of
their clients.
In August 2010 our client asked Deloitte Consulting (DC) to help drive an effort to
create a new global platform to offer portal, collaboration and document
management capabilities.
Many of the requirements for this new solution were above and beyond what the
selected platform, Microsoft SharePoint 2010 (SP), had to offer. To make matters
more complex, the expected number of combinations of clients, locations,
application modules and individual functionalities quickly grew into the
thousands. Moreover, our client had little experience embarking into an
enterprise like this one.
16 months and 11 releases later our top-talented DC team completed a solution
that exceeded our client's expectations. Each release delivered working
software, showing the team's progress and giving our client the opportunity to
adjust requirements and design as needed. Each release was delivered on time
and under budget, every time!
This document explains why we chose an agile life cycle model for this project,
how we implemented it and what lessons we learned, so other DC teams can
benefit from our experiences1.
1 For more information on Agile methodologies, please see the “Agile Development POV”
available on KX
2
Why Agile
Like many other large-scale projects, the first couple of months were mostly
dedicated to establish the overall vision, business case and define high-level
business requirements for the solution. We started off with a traditional waterfall
Software Development Life Cycle (SDLC) approach; given the strong emphasis
of our established methods (Playbook) and for the need for a tight control over
scope and budget, it seemed an adequate decision at the time.
The original concepts for the solution were vaguely defined so we needed a way
to make them concrete through continuous refinement iterations with our client.
By the end of January 2011, requirements and design work started to pile up and
our initial attempts to prototype some of these concepts were not working well.
The interactions between the client and DC teams took too long to get from
concept to requirements to prototype and back again. It was clear we had to
make important adjustm.
Agile in Practice An Agile Success Story February 2.docxsimonlbentley59018
Agile in Practice
An Agile Success
Story
February 2012
2
Agile in Practice - An Agile Success Story
Contents
Overview
1
Why
Agile
2
How
We
Did
Agile
4
SCRUM-‐derived
Model
4
Distributed
Teams
5
Planning
6
Execution
7
Documentation
7
Reporting
8
Lessons
Learned
11
What
Worked
11
What
We
Could
Have
Done
Better
11
1 Agile in Practice - An Agile Success Story
Overview
Our client serves about 10,000 clients worldwide. Their aging platform was
proving to be inefficient, difficult and expensive to adapt to the changing needs of
their clients.
In August 2010 our client asked Deloitte Consulting (DC) to help drive an effort to
create a new global platform to offer portal, collaboration and document
management capabilities.
Many of the requirements for this new solution were above and beyond what the
selected platform, Microsoft SharePoint 2010 (SP), had to offer. To make matters
more complex, the expected number of combinations of clients, locations,
application modules and individual functionalities quickly grew into the
thousands. Moreover, our client had little experience embarking into an
enterprise like this one.
16 months and 11 releases later our top-talented DC team completed a solution
that exceeded our client's expectations. Each release delivered working
software, showing the team's progress and giving our client the opportunity to
adjust requirements and design as needed. Each release was delivered on time
and under budget, every time!
This document explains why we chose an agile life cycle model for this project,
how we implemented it and what lessons we learned, so other DC teams can
benefit from our experiences1.
1 For more information on Agile methodologies, please see the “Agile Development POV”
available on KX
2
Why Agile
Like many other large-scale projects, the first couple of months were mostly
dedicated to establish the overall vision, business case and define high-level
business requirements for the solution. We started off with a traditional waterfall
Software Development Life Cycle (SDLC) approach; given the strong emphasis
of our established methods (Playbook) and for the need for a tight control over
scope and budget, it seemed an adequate decision at the time.
The original concepts for the solution were vaguely defined so we needed a way
to make them concrete through continuous refinement iterations with our client.
By the end of January 2011, requirements and design work started to pile up and
our initial attempts to prototype some of these concepts were not working well.
The interactions between the client and DC teams took too long to get from
concept to requirements to prototype and back again. It was clear we had to
make important adjustm.
Practicing Scrum with Visual Studio 2010 and TFS 2010 - TechEd Middle East 2...Jose Luis Soria
Scrum is maybe the most exciting thing that has happened to the software development world over the last years. Its empirical approach, strikingly changes the way people face projects, and shifts the focus into improving upon development practices, while continuously delivering valuable software increments. Combined with the proper tools and practices, teams can dramatically improve their performance and fulfill customer expectations. This session makes a tour around the Scrum framework, showing how Scrum Teams work in practice, and going into details about how Visual Studio and Team Foundation Server can support and facilitate a great amount of the activities carried out by these teams in their quest for delivering value.
The document provides an overview of project estimating. It discusses what estimating is, the objectives of estimating, categories of estimates like rough order of magnitude and definitive estimating. It covers items to estimate like development tasks and risks. Types of estimating like task-based and deliverable-based are presented. The document emphasizes that all estimates involve assumptions and contingencies to account for risks and unknowns. It provides examples of risk and contingency factors. Effective estimating requires experience, making reasonable assumptions, and validation techniques like triangulation of different estimate types.
SpringPeople Introduction to Agile and ScrumSpringPeople
SpringPeople's Agile & Scrum Training course is for Developers, Project Managers, Business or System Analysts, and Technical Managers who wish to learn the philosophy and practices of Scrum.
As part of Salesforce’s “Summer of Mobile” webinar series, I presented a session on user experience design for mobile. This is adapted from that webinar
To Err Is Human To Keep Repeating Mistakes in Bad BusinessKen Bruss
This document discusses how companies can improve new product development (NPD) by systematically learning from past mistakes and successes. It notes that while risks cannot be eliminated, companies can gain a competitive advantage by applying lessons learned from similar past projects. It promotes the use of "after action reviews" throughout a project's lifecycle to identify lessons and apply them in real time. Sample AAR questions and a completed sample are provided as examples. The document suggests creating an online library to share lessons learned across an organization. It poses questions to assess if a company's NPD process could benefit from more strategic management of institutional knowledge.
Expectations from IT Team
Project Methodology - Why it is as important as the Technology for your Product
Gaps in Recent Graduates
How to bridge these gaps?
1. Agile development focuses on delivering working software frequently, such as every two weeks to two months, to get customer feedback early and often in order to adapt quickly to changing needs.
2. It emphasizes collaboration between business and development teams to keep the customer's needs and priorities front and center throughout the process.
3. Self-organizing teams work in short iterations to deliver incremental value with each release rather than attempting to deliver all functionality at once at the end.
Transitioning to Scrum is not easy, and for many, distributed teams are the most difficult to manage. In trying to make Scrum work with a geographically dispersed team, increasing efficiency requires adjustments to processes and effective communication and collaboration.
This webinar will provide guidance for proper planning and managing, in order to get your distributed teams working smoothly throughout the scrum processes. Dr. Kevin Thompson, cPrime’s Agile Practice Lead, will address key issues such as:
• How to have scrum meetings for distributed teams (daily scrum, sprint planning, sprint review, retrospective)
• How to cope with time-zone differences
• How to cope with language differences
• Best practices for collaborating in a distributed team
• Best practices for tools that mitigate distributed team impact
This is the Personal Agility Canvas worksheet the was used in the Personal Agility Canvas session I led at Heart of Agile 2017 in Pittsburgh on April 28, 2017.
Personal Kanban - Less Guilt More Finishing (Digital PM Summit 2014)Dave Prior
The document discusses the concept and methodology of Personal Kanban, which is a way to visualize and limit work in progress to improve productivity. It recommends mapping out one's workflow with columns like backlog, ready, doing, and done. The key rules are to visualize work and limit work in progress. Following these simple rules and mindfully observing one's work patterns can help identify dysfunctions and lead to improvements over time through an empirical approach. The overall goal of Personal Kanban is to finish more by focusing on learning how you work rather than just trying to get more tasks done.
Agile 2014 - Personal Agility Canvas - Dave PriorDave Prior
The document discusses developing personal agility through defining goals and creating an action plan. It introduces the Personal Agility Canvas as a tool to help individuals assess their strengths, weaknesses, environment and desired changes in their transition to being more agile. The canvas is used to define specific and measurable goals before creating an action plan with next steps and finding an accountability partner to help achieve those goals.
Scrum in the waterfall dpm2013 no pix rfsDave Prior
This document contains a summary of a presentation on implementing Scrum in a waterfall environment. It includes slides on Dalton's rules, acceptance criteria, ideas, communication models, leadership approaches, and concludes by thanking the audience and providing contact information for the presenter. Copyright for the presentation is held by BigVisible Solutions, Inc.
Essentials of Automations: The Art of Triggers and Actions in FMESafe Software
In this second installment of our Essentials of Automations webinar series, we’ll explore the landscape of triggers and actions, guiding you through the nuances of authoring and adapting workspaces for seamless automations. Gain an understanding of the full spectrum of triggers and actions available in FME, empowering you to enhance your workspaces for efficient automation.
We’ll kick things off by showcasing the most commonly used event-based triggers, introducing you to various automation workflows like manual triggers, schedules, directory watchers, and more. Plus, see how these elements play out in real scenarios.
Whether you’re tweaking your current setup or building from the ground up, this session will arm you with the tools and insights needed to transform your FME usage into a powerhouse of productivity. Join us to discover effective strategies that simplify complex processes, enhancing your productivity and transforming your data management practices with FME. Let’s turn complexity into clarity and make your workspaces work wonders!
How to Get CNIC Information System with Paksim Ga.pptxdanishmna97
Pakdata Cf is a groundbreaking system designed to streamline and facilitate access to CNIC information. This innovative platform leverages advanced technology to provide users with efficient and secure access to their CNIC details.
GraphSummit Singapore | The Future of Agility: Supercharging Digital Transfor...Neo4j
Leonard Jayamohan, Partner & Generative AI Lead, Deloitte
This keynote will reveal how Deloitte leverages Neo4j’s graph power for groundbreaking digital twin solutions, achieving a staggering 100x performance boost. Discover the essential role knowledge graphs play in successful generative AI implementations. Plus, get an exclusive look at an innovative Neo4j + Generative AI solution Deloitte is developing in-house.
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
Best 20 SEO Techniques To Improve Website Visibility In SERPPixlogix Infotech
Boost your website's visibility with proven SEO techniques! Our latest blog dives into essential strategies to enhance your online presence, increase traffic, and rank higher on search engines. From keyword optimization to quality content creation, learn how to make your site stand out in the crowded digital landscape. Discover actionable tips and expert insights to elevate your SEO game.
Sudheer Mechineni, Head of Application Frameworks, Standard Chartered Bank
Discover how Standard Chartered Bank harnessed the power of Neo4j to transform complex data access challenges into a dynamic, scalable graph database solution. This keynote will cover their journey from initial adoption to deploying a fully automated, enterprise-grade causal cluster, highlighting key strategies for modelling organisational changes and ensuring robust disaster recovery. Learn how these innovations have not only enhanced Standard Chartered Bank’s data infrastructure but also positioned them as pioneers in the banking sector’s adoption of graph technology.
Cosa hanno in comune un mattoncino Lego e la backdoor XZ?Speck&Tech
ABSTRACT: A prima vista, un mattoncino Lego e la backdoor XZ potrebbero avere in comune il fatto di essere entrambi blocchi di costruzione, o dipendenze di progetti creativi e software. La realtà è che un mattoncino Lego e il caso della backdoor XZ hanno molto di più di tutto ciò in comune.
Partecipate alla presentazione per immergervi in una storia di interoperabilità, standard e formati aperti, per poi discutere del ruolo importante che i contributori hanno in una comunità open source sostenibile.
BIO: Sostenitrice del software libero e dei formati standard e aperti. È stata un membro attivo dei progetti Fedora e openSUSE e ha co-fondato l'Associazione LibreItalia dove è stata coinvolta in diversi eventi, migrazioni e formazione relativi a LibreOffice. In precedenza ha lavorato a migrazioni e corsi di formazione su LibreOffice per diverse amministrazioni pubbliche e privati. Da gennaio 2020 lavora in SUSE come Software Release Engineer per Uyuni e SUSE Manager e quando non segue la sua passione per i computer e per Geeko coltiva la sua curiosità per l'astronomia (da cui deriva il suo nickname deneb_alpha).
Removing Uninteresting Bytes in Software FuzzingAftab Hussain
Imagine a world where software fuzzing, the process of mutating bytes in test seeds to uncover hidden and erroneous program behaviors, becomes faster and more effective. A lot depends on the initial seeds, which can significantly dictate the trajectory of a fuzzing campaign, particularly in terms of how long it takes to uncover interesting behaviour in your code. We introduce DIAR, a technique designed to speedup fuzzing campaigns by pinpointing and eliminating those uninteresting bytes in the seeds. Picture this: instead of wasting valuable resources on meaningless mutations in large, bloated seeds, DIAR removes the unnecessary bytes, streamlining the entire process.
In this work, we equipped AFL, a popular fuzzer, with DIAR and examined two critical Linux libraries -- Libxml's xmllint, a tool for parsing xml documents, and Binutil's readelf, an essential debugging and security analysis command-line tool used to display detailed information about ELF (Executable and Linkable Format). Our preliminary results show that AFL+DIAR does not only discover new paths more quickly but also achieves higher coverage overall. This work thus showcases how starting with lean and optimized seeds can lead to faster, more comprehensive fuzzing campaigns -- and DIAR helps you find such seeds.
- These are slides of the talk given at IEEE International Conference on Software Testing Verification and Validation Workshop, ICSTW 2022.
In his public lecture, Christian Timmerer provides insights into the fascinating history of video streaming, starting from its humble beginnings before YouTube to the groundbreaking technologies that now dominate platforms like Netflix and ORF ON. Timmerer also presents provocative contributions of his own that have significantly influenced the industry. He concludes by looking at future challenges and invites the audience to join in a discussion.
Unlock the Future of Search with MongoDB Atlas_ Vector Search Unleashed.pdfMalak Abu Hammad
Discover how MongoDB Atlas and vector search technology can revolutionize your application's search capabilities. This comprehensive presentation covers:
* What is Vector Search?
* Importance and benefits of vector search
* Practical use cases across various industries
* Step-by-step implementation guide
* Live demos with code snippets
* Enhancing LLM capabilities with vector search
* Best practices and optimization strategies
Perfect for developers, AI enthusiasts, and tech leaders. Learn how to leverage MongoDB Atlas to deliver highly relevant, context-aware search results, transforming your data retrieval process. Stay ahead in tech innovation and maximize the potential of your applications.
#MongoDB #VectorSearch #AI #SemanticSearch #TechInnovation #DataScience #LLM #MachineLearning #SearchTechnology
“An Outlook of the Ongoing and Future Relationship between Blockchain Technologies and Process-aware Information Systems.” Invited talk at the joint workshop on Blockchain for Information Systems (BC4IS) and Blockchain for Trusted Data Sharing (B4TDS), co-located with with the 36th International Conference on Advanced Information Systems Engineering (CAiSE), 3 June 2024, Limassol, Cyprus.
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!
AI 101: An Introduction to the Basics and Impact of Artificial IntelligenceIndexBug
Imagine a world where machines not only perform tasks but also learn, adapt, and make decisions. This is the promise of Artificial Intelligence (AI), a technology that's not just enhancing our lives but revolutionizing entire industries.
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
Maruthi Prithivirajan, Head of ASEAN & IN Solution Architecture, Neo4j
Get an inside look at the latest Neo4j innovations that enable relationship-driven intelligence at scale. Learn more about the newest cloud integrations and product enhancements that make Neo4j an essential choice for developers building apps with interconnected data and generative AI.
GraphSummit Singapore | The Art of the Possible with Graph - Q2 2024Neo4j
Neha Bajwa, Vice President of Product Marketing, Neo4j
Join us as we explore breakthrough innovations enabled by interconnected data and AI. Discover firsthand how organizations use relationships in data to uncover contextual insights and solve our most pressing challenges – from optimizing supply chains, detecting fraud, and improving customer experiences to accelerating drug discoveries.