This is an invited talk I gave at STC Management Day in Toronto (Feb 2010). After intro, show role of docs in iterations - sometimes trailing.
Let me know if you would like a copy of this presentation for your own use
Presented at NRF Big Show, the main technology in retail conference of the year, on January 13, 2015 in NYC. A discussion of challenges faced by big enterprises, particularly retailers, on their quest to become more agile, and what to do to enable agility through devops principles and pervasive automation in technology operations. It is the adaptation of the talk I gave at the CloudExpo 2 months earlier.
This document discusses applying software craftsmanship practices to a Scrum project. It presents software craftsmanship principles like clean code, test-driven development, and code reviews. It proposes a guideline to implement these principles in each phase of a Scrum project. The document also describes a case study where this guideline was applied to a mobile ecommerce app developed by a distributed Scrum team over 12 sprints. Technical metrics like deleted lines were used to measure reductions in technical debt from using craftsmanship practices in conjunction with Scrum. The conclusion is that Scrum benefits from these additional practices to improve quality.
Principles of Modern Application ArchitectureRajesh RV
The document outlines 5 principles of modern application architecture. The first principle is to develop an adaptive architecture that can easily replace parts to reduce replacement costs rather than building for 10 years of robust support. The second is to develop a system of records that acts as a platform for business innovation rather than focusing innovation only at the business level. The third is to develop a functional core focused on key responsibilities and leave non-functional aspects like performance to cloud providers. The fourth is to make technology changes irrelevant to overall success rather than using only proven technologies. The fifth is to design systems that fail and recover fast rather than attempting to design systems that never fail.
Intel relies on GE's Proficy Cimplicity software to precisely monitor and control their manufacturing facilities worldwide. GE software sales to Intel have exceeded $2 million in 2013, with half of that for replacing legacy Rockwell software at Intel's global assembly/test facilities. A new evaluation of GE Energy's Envisage energy management software could threaten Schneider Electric's existing solution at Intel, driving further Cimplicity sales. Next week, GE and Intel will meet to discuss cybersecurity and mobile applications collaboration. Intel also procured GE services to support a change management pilot to replace outdated source control software and allow version control of additional equipment brands.
A talk about what I call Progressive Delivery: a basket of skills and technologies concerned with modern software development, testing and deployment: including canarying, Feature Flags, A/B testing at scale. We're seeing Advances in approaches to application and service. On the technology side, Kubernetes and Istio bring new management challenges, but also opportunities – service mesh approaches can enable a lot more sophistication in routing of new application functions to particular user communities, managing and mitigating the blast ratio of a service.
The document summarizes Tony Bibbs' presentation on software development at the University of Northern Iowa. It discusses his background and career in software engineering. It then outlines the evolution of software development practices at his company, including establishing formal processes and frameworks to improve quality and productivity. The goals are to minimize bugs, standardize development, foster collaboration among skilled developers, and establish testing practices. Examples of successful projects are provided.
2020 progressive delivery, git ops, observability James Governor
GitOpsDays keynote. Tech trends in 2020. Progressive Delivery, GitOps and Observability. Moving to a product management driven culture of experimentation. But what underpins that. Automation, collaboration through GitHub. all the companies making it easier to experiment with features before rolling them out to more users. Tools used and built by Nike, CapitalOne, Target, Uber.
Continuous Integration has come a long way. From starting out as a fringe school of throught to the mainstream practice it is today, CI has had an enormous impact on the way build and development teams operate. In this presentation, we look at how CI has evolved, and where its future lies.
This document discusses project selection and prioritization. It covers various financial metrics used to evaluate projects including net present value (NPV), internal rate of return (IRR), payback period, and modeling project returns and costs. An example of evaluating a proposed new feature for a web-based payroll system called WebPayroll is presented, with financial projections built out over 8 quarters to calculate the NPV, IRR, payback period and discounted payback period for the project. The document emphasizes the importance of estimating project costs in addition to modeling projected financial returns in order to properly evaluate and prioritize projects.
This presentation by certified Scrum trainer Mike Cohn addresses a common challenge in agile development: the new role of leaders and managers in self-organizing teams.
Incorporating Learning and Expected Cost of ChangeMike Cohn
This document presents three guidelines for prioritizing features on agile projects:
1. Defer features with high expected costs of change, which is the probability of change multiplied by the cost of change. Features likely or costly to change should be delayed.
2. Prioritize features that generate useful knowledge, such as knowledge about a feature's desirability, usability, or technical feasibility.
3. Incorporate new learning often to decide what to do next, either implementing a feature now or reevaluating it later. Priorities should be reassessed each iteration to acknowledge continuous learning.
This document discusses transitioning to an agile development process and overcoming challenges associated with previous waterfall methods. It provides a framework for transitioning that includes treating the transition as a project with its own backlog and iterations. Common "waterfallacies" and fears of change ("agilephobias") are addressed, such as the inability to accurately predict schedules and fixed requirements upfront. Distributed teams and integrating testing are also discussed. The transition process itself needs to be agile and adapt to challenges identified along the way.
Compared to traditional software engineering, agile development is mainly targeted at projects with dynamic, undeterministic and non-linear characteristics, where accurate estimates, stable plans and predictions are often hard to get in early stages, and big up-front designs and arrangements will probably cause a lot of waste, i.e. are not economically sound.
Agile software development is a group of software development methods in which requirements and solutions evolve through collaboration between self-organizing, cross-functional teams. It promotes adaptive planning, evolutionary development, early delivery, continuous improvement and encourages rapid and flexible response to change. It is a conceptual framework that focuses on frequently delivering small increments of working software.
Getting Agile with Scrum discusses Scrum, an agile framework for project management. Some key points:
- Scrum uses short "sprints" typically 2-4 weeks long where work is designed, coded, and tested simultaneously rather than sequentially passed between teams.
- Scrum roles include the Product Owner who prioritizes work, the Scrum Master who facilitates the process, and a cross-functional Team.
- Ceremonies like daily stand-ups, sprint planning and reviews, and retrospectives help manage the work and process.
- Burndown charts track work completion. Scaling can involve multiple Scrum teams working on the same product managed through communities of practice.
The document discusses problems with traditional software development approaches and how agile software development aims to address these problems. Specifically, it notes that traditional phased development often results in unclear requirements, requirements that change and become more expensive to change, projects that take too long, lack of testing, and wasted time on unused functionality. Agile development breaks projects into shorter iterations to allow for inspection and adaptation, improving visibility, catching failures earlier, and focusing on only the most valuable functionality.
Velocity is perhaps the most useful metric available to agile teams. In this session we will look at advanced uses of velocity for planning under special but common circumstances. We will see how to forecast velocity in the complete absence of any historical data. We will look at how a new team can forecast velocity by looking at other teams. We will see how to predict the velocity of a team that will grow or shrink in size. Most importantly we will look at the use of confidence intervals to create plans we can be 90% confident in, even on fixed-price or fixed-date contracts.
This document discusses planning and tracking agile projects. It begins by introducing Mike Cohn and his background. It then provides examples for estimating tasks using story points and planning poker. It discusses relating different planning levels from portfolio down to daily tasks. Release planning and using velocity and a prioritized backlog to estimate delivery dates is covered. Finally, it discusses using burndown charts to track progress at both the iteration and release levels.
The first step in creating a useful plan is the ability to estimate reliably. In this session we will discuss how to do this. We will look at various approaches to estimating including unit-less points and ideal time. The class will present four specific techniques for deriving reliable estimates, including how to use the popular Planning Poker® technique and other techniques that dramatically improve a project's chances of on-time completion.
The document discusses principles for being agile and delighting customers. It suggests companies should be ready for the unpredictable like Oreo, adapt and innovate like Fujifilm, frequently deliver products like Zara, and care about customers like Zappos. It also emphasizes focusing on people and culture like Zappos. To create an agile culture, the document recommends establishing autonomous teams that iteratively deliver frequently, getting customer feedback to continuously improve processes and letting this new way of working spread throughout the company.
This document provides an overview of Agile and Scrum frameworks. It discusses the Agile Manifesto and 12 principles, Scrum roles like Product Owner and Scrum Master, Scrum artifacts like Product Backlog and Sprint Backlog, and Scrum ceremonies like Sprint Planning, Daily Standup, Sprint Review and Retrospectives. The goal of Scrum is to deliver working software frequently through an empirical and iterative process that is transparent, inspectable and adaptable.
A brief and visual introduction to the Agile.
Learn the Agile mindset and the big 3 (Extreme Programming, Scrum, and Kanban). Be able to whiteboard a simple view of how each one works to get things done and make things happen.
The technique of expressing requirements as user stories is one of the most broadly applicable techniques introduced by the agile processes. User stories are an effective approach on all time constrained projects and are a great way to begin introducing a bit of agility to your projects.
In this session, we will look at how to identify and write good user stories. The class will describe the six attributes that good stories should exhibit and present thirteen guidelines for writing better stories. We will explore how user role modeling can help when gathering a project’s initial stories.
Because requirements touch all job functions on a development project, this tutorial will be equally suited for analysts, customers, testers, programmers, managers, or anyone involved in a software development project. By the end of this tutorial, you will leave knowing the six attributes of a good story, learn a good format for writing most user stories, learn practical techniques for gathering user stories, know how much work to do up-front and how much to do just-in-time.
Scaling Agile and Working with a Distributed TeamMike Cohn
Mike Cohn presented on scaling agile with distributed teams. Some key challenges in scaling agile include managing dependencies between teams, coordinating large iteration planning meetings, and coordinating multiple teams. To address these challenges, Cohn recommends proactively managing dependencies, using rolling lookahead planning, scaling up iteration planning meetings by staggering them over multiple days or using a "big room" approach, and establishing communities of practice to facilitate collaboration. When teams are distributed across locations, it is important to decide how work will be distributed, create coherence among team members, and change communication approaches, such as adding documentation, encouraging lateral communication, and addressing time zone differences.
The first step in creating a useful plan is the ability to estimate reliably. In this session we will discuss how to do this. We will look at various approaches to estimating including unit-less points and ideal time. The class will present four specific techniques for deriving reliable estimates, including how to use the popular Planning Poker® technique and other techniques that dramatically improve a project's chances of on-time completion.
The document discusses an agenda for agile planning and project management. It covers iterative and incremental development, user stories, estimating effort for stories, and planning iterations. The presentation introduces user stories and templates, discusses adding details as sub-stories or conditions of satisfaction. It also covers estimating story points using planning poker and velocity to calculate how many story points a team can deliver in future iterations.
Scaling Agile and Working with a Distributed TeamMike Cohn
The early agile literature was adamant about two things: stick with small teams and put everyone in one room. However, in the years since the Agile Manifesto, the increasing popularity of agile and the dramatic improvements it brings has pushed it onto larger and larger projects. Additionally, having an entire team--especially on a large project--in one room, or even one building is a luxury no longer enjoyed by many projects.
In this presentation, we will look at how agile can be scaled to work on any multi-team project. Even a project with two teams will benefit from learning how to proactively manage interteam dependencies, conduct iteration planning for multiple teams, cultivate communities of practice, and coordinating work. Because so many projects are spread across multiple sites we will also look at overcoming the unique challenges facing distributed teams. We will look at deciding how to distribute a team, how to create coherence among team members, the importance of getting together and when are the most important times to use the travel budget, changes to what the team documents, and how to handle meetings when spread across timezones. Whether your project is spread across two locations in the same city or spread around the globe, you will leave with practical advice to try tomorrow.
There are a lot of choices and alternatives for getting started with Agile. It can be confusing. This talk will give you a brief guided tour of Agile methodologies so that you have some understanding of how they are similar and how they differ. We'll cover some of the history of iterative development and waterfall as well as the Agile Manifesto to provide context. At the end of this, you will have an understanding of key principles and the Agile landscape.
Please email me if you would like a download.
In this interactive webinar, the participants will get an overview of the fundamental principles and mechanics of Scrum, thereby understanding the benefits of adopting Scrum principles and values in an organization
Brief Intro to Agile, Benefits & TransitionMichael Sahota
This presentation was given to a client at the start of an assessment phase to explain to the staff why Agile is of value and briefly explain how it works. We also explained the typical approach to transition and what would happen during the assessment. The presentation was given to Engineering and related groups. This was prepared and delivered jointly with Gerry Kirk.
Please email us if you would like a download.
Business Value of Agile Testing: Using TDD, CI, CD, & DevOpsDavid Rico
Presentation on the "Business Value of Agile Testing: Using Test Driven Development, Continuous Integration, Continuous Delivery, & DevOps," which are highly-disciplined contemporary new product development (NPD) approaches for rapidly building high-quality information technology-intensive systems. Identifies the motivation for agile methods, provide a brief introduction to agile methods, describe the fundamental mechanics of agile methods, and a brief survey of the benefits of agile methods as reported by major industry studies (including rarely seen, late-breaking economic data and results from the top consulting firms). Defines agile testing and introduce basic and advanced agile testing practices, strategies, metrics, outcomes, costs & benefits, cost of quality, and statistical performance data. Introduces basic and advanced agile scaling practices, case studies of enterprise-level agile testing, Continuous Delivery, and DevOps at major Internet firms, and common agile testing tools and automation suites. Closes with a summary of agile testing adoption rates, common barriers to agile testing, organizational change models for agile testing, and a summary of the benefits of agile testing.
This document discusses project selection and prioritization. It covers various financial metrics used to evaluate projects including net present value (NPV), internal rate of return (IRR), payback period, and modeling project returns and costs. An example of evaluating a proposed new feature for a web-based payroll system called WebPayroll is presented, with financial projections built out over 8 quarters to calculate the NPV, IRR, payback period and discounted payback period for the project. The document emphasizes the importance of estimating project costs in addition to modeling projected financial returns in order to properly evaluate and prioritize projects.
This presentation by certified Scrum trainer Mike Cohn addresses a common challenge in agile development: the new role of leaders and managers in self-organizing teams.
Incorporating Learning and Expected Cost of ChangeMike Cohn
This document presents three guidelines for prioritizing features on agile projects:
1. Defer features with high expected costs of change, which is the probability of change multiplied by the cost of change. Features likely or costly to change should be delayed.
2. Prioritize features that generate useful knowledge, such as knowledge about a feature's desirability, usability, or technical feasibility.
3. Incorporate new learning often to decide what to do next, either implementing a feature now or reevaluating it later. Priorities should be reassessed each iteration to acknowledge continuous learning.
This document discusses transitioning to an agile development process and overcoming challenges associated with previous waterfall methods. It provides a framework for transitioning that includes treating the transition as a project with its own backlog and iterations. Common "waterfallacies" and fears of change ("agilephobias") are addressed, such as the inability to accurately predict schedules and fixed requirements upfront. Distributed teams and integrating testing are also discussed. The transition process itself needs to be agile and adapt to challenges identified along the way.
Compared to traditional software engineering, agile development is mainly targeted at projects with dynamic, undeterministic and non-linear characteristics, where accurate estimates, stable plans and predictions are often hard to get in early stages, and big up-front designs and arrangements will probably cause a lot of waste, i.e. are not economically sound.
Agile software development is a group of software development methods in which requirements and solutions evolve through collaboration between self-organizing, cross-functional teams. It promotes adaptive planning, evolutionary development, early delivery, continuous improvement and encourages rapid and flexible response to change. It is a conceptual framework that focuses on frequently delivering small increments of working software.
Getting Agile with Scrum discusses Scrum, an agile framework for project management. Some key points:
- Scrum uses short "sprints" typically 2-4 weeks long where work is designed, coded, and tested simultaneously rather than sequentially passed between teams.
- Scrum roles include the Product Owner who prioritizes work, the Scrum Master who facilitates the process, and a cross-functional Team.
- Ceremonies like daily stand-ups, sprint planning and reviews, and retrospectives help manage the work and process.
- Burndown charts track work completion. Scaling can involve multiple Scrum teams working on the same product managed through communities of practice.
The document discusses problems with traditional software development approaches and how agile software development aims to address these problems. Specifically, it notes that traditional phased development often results in unclear requirements, requirements that change and become more expensive to change, projects that take too long, lack of testing, and wasted time on unused functionality. Agile development breaks projects into shorter iterations to allow for inspection and adaptation, improving visibility, catching failures earlier, and focusing on only the most valuable functionality.
Velocity is perhaps the most useful metric available to agile teams. In this session we will look at advanced uses of velocity for planning under special but common circumstances. We will see how to forecast velocity in the complete absence of any historical data. We will look at how a new team can forecast velocity by looking at other teams. We will see how to predict the velocity of a team that will grow or shrink in size. Most importantly we will look at the use of confidence intervals to create plans we can be 90% confident in, even on fixed-price or fixed-date contracts.
This document discusses planning and tracking agile projects. It begins by introducing Mike Cohn and his background. It then provides examples for estimating tasks using story points and planning poker. It discusses relating different planning levels from portfolio down to daily tasks. Release planning and using velocity and a prioritized backlog to estimate delivery dates is covered. Finally, it discusses using burndown charts to track progress at both the iteration and release levels.
The first step in creating a useful plan is the ability to estimate reliably. In this session we will discuss how to do this. We will look at various approaches to estimating including unit-less points and ideal time. The class will present four specific techniques for deriving reliable estimates, including how to use the popular Planning Poker® technique and other techniques that dramatically improve a project's chances of on-time completion.
The document discusses principles for being agile and delighting customers. It suggests companies should be ready for the unpredictable like Oreo, adapt and innovate like Fujifilm, frequently deliver products like Zara, and care about customers like Zappos. It also emphasizes focusing on people and culture like Zappos. To create an agile culture, the document recommends establishing autonomous teams that iteratively deliver frequently, getting customer feedback to continuously improve processes and letting this new way of working spread throughout the company.
This document provides an overview of Agile and Scrum frameworks. It discusses the Agile Manifesto and 12 principles, Scrum roles like Product Owner and Scrum Master, Scrum artifacts like Product Backlog and Sprint Backlog, and Scrum ceremonies like Sprint Planning, Daily Standup, Sprint Review and Retrospectives. The goal of Scrum is to deliver working software frequently through an empirical and iterative process that is transparent, inspectable and adaptable.
A brief and visual introduction to the Agile.
Learn the Agile mindset and the big 3 (Extreme Programming, Scrum, and Kanban). Be able to whiteboard a simple view of how each one works to get things done and make things happen.
The technique of expressing requirements as user stories is one of the most broadly applicable techniques introduced by the agile processes. User stories are an effective approach on all time constrained projects and are a great way to begin introducing a bit of agility to your projects.
In this session, we will look at how to identify and write good user stories. The class will describe the six attributes that good stories should exhibit and present thirteen guidelines for writing better stories. We will explore how user role modeling can help when gathering a project’s initial stories.
Because requirements touch all job functions on a development project, this tutorial will be equally suited for analysts, customers, testers, programmers, managers, or anyone involved in a software development project. By the end of this tutorial, you will leave knowing the six attributes of a good story, learn a good format for writing most user stories, learn practical techniques for gathering user stories, know how much work to do up-front and how much to do just-in-time.
Scaling Agile and Working with a Distributed TeamMike Cohn
Mike Cohn presented on scaling agile with distributed teams. Some key challenges in scaling agile include managing dependencies between teams, coordinating large iteration planning meetings, and coordinating multiple teams. To address these challenges, Cohn recommends proactively managing dependencies, using rolling lookahead planning, scaling up iteration planning meetings by staggering them over multiple days or using a "big room" approach, and establishing communities of practice to facilitate collaboration. When teams are distributed across locations, it is important to decide how work will be distributed, create coherence among team members, and change communication approaches, such as adding documentation, encouraging lateral communication, and addressing time zone differences.
The first step in creating a useful plan is the ability to estimate reliably. In this session we will discuss how to do this. We will look at various approaches to estimating including unit-less points and ideal time. The class will present four specific techniques for deriving reliable estimates, including how to use the popular Planning Poker® technique and other techniques that dramatically improve a project's chances of on-time completion.
The document discusses an agenda for agile planning and project management. It covers iterative and incremental development, user stories, estimating effort for stories, and planning iterations. The presentation introduces user stories and templates, discusses adding details as sub-stories or conditions of satisfaction. It also covers estimating story points using planning poker and velocity to calculate how many story points a team can deliver in future iterations.
Scaling Agile and Working with a Distributed TeamMike Cohn
The early agile literature was adamant about two things: stick with small teams and put everyone in one room. However, in the years since the Agile Manifesto, the increasing popularity of agile and the dramatic improvements it brings has pushed it onto larger and larger projects. Additionally, having an entire team--especially on a large project--in one room, or even one building is a luxury no longer enjoyed by many projects.
In this presentation, we will look at how agile can be scaled to work on any multi-team project. Even a project with two teams will benefit from learning how to proactively manage interteam dependencies, conduct iteration planning for multiple teams, cultivate communities of practice, and coordinating work. Because so many projects are spread across multiple sites we will also look at overcoming the unique challenges facing distributed teams. We will look at deciding how to distribute a team, how to create coherence among team members, the importance of getting together and when are the most important times to use the travel budget, changes to what the team documents, and how to handle meetings when spread across timezones. Whether your project is spread across two locations in the same city or spread around the globe, you will leave with practical advice to try tomorrow.
There are a lot of choices and alternatives for getting started with Agile. It can be confusing. This talk will give you a brief guided tour of Agile methodologies so that you have some understanding of how they are similar and how they differ. We'll cover some of the history of iterative development and waterfall as well as the Agile Manifesto to provide context. At the end of this, you will have an understanding of key principles and the Agile landscape.
Please email me if you would like a download.
In this interactive webinar, the participants will get an overview of the fundamental principles and mechanics of Scrum, thereby understanding the benefits of adopting Scrum principles and values in an organization
Brief Intro to Agile, Benefits & TransitionMichael Sahota
This presentation was given to a client at the start of an assessment phase to explain to the staff why Agile is of value and briefly explain how it works. We also explained the typical approach to transition and what would happen during the assessment. The presentation was given to Engineering and related groups. This was prepared and delivered jointly with Gerry Kirk.
Please email us if you would like a download.
Business Value of Agile Testing: Using TDD, CI, CD, & DevOpsDavid Rico
Presentation on the "Business Value of Agile Testing: Using Test Driven Development, Continuous Integration, Continuous Delivery, & DevOps," which are highly-disciplined contemporary new product development (NPD) approaches for rapidly building high-quality information technology-intensive systems. Identifies the motivation for agile methods, provide a brief introduction to agile methods, describe the fundamental mechanics of agile methods, and a brief survey of the benefits of agile methods as reported by major industry studies (including rarely seen, late-breaking economic data and results from the top consulting firms). Defines agile testing and introduce basic and advanced agile testing practices, strategies, metrics, outcomes, costs & benefits, cost of quality, and statistical performance data. Introduces basic and advanced agile scaling practices, case studies of enterprise-level agile testing, Continuous Delivery, and DevOps at major Internet firms, and common agile testing tools and automation suites. Closes with a summary of agile testing adoption rates, common barriers to agile testing, organizational change models for agile testing, and a summary of the benefits of agile testing.
The document discusses challenges in software development life cycles (SDLC) and proposes solutions to increase effectiveness and efficiency. It recommends harnessing best practices like time-boxing requirements, using modeling tools, test-driven development, and continuous integration. Case studies show how these techniques reduced development times at various companies. The profile section introduces Mick Knutson, an experienced consultant advocating optimizing agility in SDLC.
Join Steph and Chris as they run through Microsoft's transformation from shipping boxed products to always-on online services. Developer Velocity is a critical part of that journey to ensure the teams can keep delivering value to their end-users at scale. In this session, you will learn about some of the tips & tricks that Microsoft used along the way.
https://www.youtube.com/watch?v=d_4i0lxKtr0
The document discusses agile as an active risk management strategy for software development projects. It notes that agile approaches can help reduce costs, delay, and increase benefits and value. The document also provides evidence that agile methods have benefits like increased productivity, quality and stakeholder satisfaction. It discusses how many large companies and government organizations like the DoD have adopted agile. Finally, it outlines a suggested agile transition approach using coaches over several phases.
Atagg2015 iot internet of things - get ready to test the connected future ata...Agile Testing Alliance
This document discusses Internet of Things (IoT) and its impact on testing. It begins with defining IoT and describing how it allows physical objects to be sensed and controlled remotely. It then outlines key verticals adopting IoT, typical IoT technology stacks, and how IoT will change testing approaches. Specifically, it notes that IoT systems will need to be tested for interoperability, different network types, security, and functionality across more devices and integrated users. It emphasizes that agile practices will be important for IoT delivery through continuous integration and deployment. The document concludes that skills like collaborative testing will be important for addressing the challenges of IoT testing.
Platform Requirements for CI/CD Success—and the Enterprises Leading the WayVMware Tanzu
All enterprises want to increase the speed of software delivery to get new products to market faster. The means for achieving this is often through the practice of continuous integration/continuous delivery. But speed alone isn’t enough—teams also require the ability to pivot when conditions change. They must ensure their software is stable and reliable, and be able to roll out patches and other security measures quickly and at scale.
A cloud-native platform coupled with test-driven development and CI/CD practices can help make this a reality. In this webinar, 451 Research’s Jay Lyman presents the results of his research into cloud-native platform requirements for enterprise CI/CD and DevOps success. Pivotal’s James Ma joins Lyman to discuss best practices from DevOps teams charged with running and managing cloud-native platforms, including applying CI/CD to the platform itself.
Speakers: James Ma, Pivotal and Jay Lyman, 451 Research
This document provides a summary of Arindom Kumar Biswas's professional experience and qualifications. It summarizes that he has over 7 years of experience working as a Project Lead and Technical Lead on Mainframe projects for insurance companies like Cognizant Technology Solutions and MetLife. It also lists his technical skills which include languages like COBOL, JCL, and databases like VSAM, DB2. Finally, it provides details of some of the projects he has worked on, including conversions from legacy to new platforms and product launches.
Postcards From The Agile Frontier FinalElena Yatzeck
This document summarizes a presentation titled "Postcards from the Agile Frontier" given by Elena Yatzeck at an IIBA meeting on March 3, 2010. The presentation provides an overview of agile basics, including definitions and principles from the Agile Manifesto. It describes a sample scrum process and discusses why agile has become popular. The presentation examines various roles for business analysts on agile projects, including as a dedicated business analyst, part of a product owner team, and as a scrum master. It recommends several classic books for further reading on agile project management.
This document provides an overview of DevOps and how to adopt a DevOps approach. It discusses that DevOps aims to shorten the systems development life cycle and provide continuous delivery with high software quality. The document outlines that adopting DevOps involves changes to an organization's people, processes and technologies. It provides strategies for building a collaborative culture and implementing shared goals and metrics. It also discusses implementing efficient processes for continuous integration, delivery, testing and monitoring. The document recommends technologies like infrastructure as code, collaboration tools, and release automation to support the DevOps approach.
An overview of IT challenges and how Perficient China uses agile frameworks, methodologies, and practices to address these challenges and consistently deliver valued results to our clients.
Reedy Feggins presented on adopting scaled agile practices. Some key points:
1. Feggins has over 15 years of software development experience and various agile certifications.
2. Innovation is increasingly driven by software, but software delivery faces challenges like changing requirements, unpredictable schedules, and high costs.
3. The Scaled Agile Framework (SAFe) provides a proven approach for applying agile practices at an enterprise scale across many teams. It aims to synchronize alignment, collaboration, and delivery.
IBM DevOps - Adopting Scaled Agile Framework (SAFe) WebinarReedy Feggins Jr
Reedy Feggins presents on scaling agile practices. He has over 15 years of software development experience including certifications in SAFe, Scrum, and Project Management. Innovation is increasingly driven by software, but software development faces challenges like changing requirements, unpredictable delivery, and high costs. Agile frameworks aim to address these challenges but don't scale beyond the team level. The Scaled Agile Framework (SAFe) provides a proven approach for applying agile practices at an enterprise scale through alignment, collaboration, and synchronized delivery across many teams. SAFe has helped other organizations increase productivity, speed time to market, and reduce defects.
The document discusses challenges with traditional waterfall software development approaches and how agile development methods address some of these challenges. It notes that waterfall projects often fail to meet schedules, budgets and user needs due to changing requirements. Agile methods use iterative development, prioritize working software over documentation, and emphasize collaboration between developers and customers.
Now-a-days the world of testing has shifted towards a Continuous Testing model. With increasing digital transformation, Agile & DevOps principles, the need to scale up quality initiatives becomes inevitable. Moreover, with increasing complexity and continuous integration cycles, the frequency of tests to release apps in a shorter time frame with continuous testing becomes the need of the hour to match the speed of Agile & DevOps.
Fast feedback loops and immediate responses allow businesses to adapt to changes in the market quicker than ever before. This is made possible with automation and continuous testing. But how do you achieve continuous testing?
In this, our specialist Sushma Nayak will discuss the present-day best practices in test automation at Knoldus and will examine the key testing trends that focus on the adoption of Continuous Delivery and the evolution of test automation in the coming year.
watch the video of this session on our website: https://www.knoldus.com/learn/webinars
Dancing With The Agile Goddess Agile 2008Israel Gat
This document summarizes an agenda for a presentation on agile methodologies. The presentation discusses agile success at BMC Software through the implementation of Scrum teams. It analyzes data comparing BMC's projects to industry trends, finding BMC achieved faster development times and higher productivity while maintaining quality. The presentation then discusses challenges of applying agile practices across an entire enterprise and proposes a three-level framework to scale agile.
Architecture vs. Design vs. Agile: What’s the Answer?TechWell
Is architecture the same as preliminary design in agile? It shouldn't be. Do we do architecture up front, then do iterative development after the architecture is done? That is edging back toward waterfall. Can you explain the purpose of the architecture in just two or three statements? Anthony Crain says that when he asks that question, he gets either verbose answers or blank stares. So Anthony shares an elegantly simple two bullet explanation of what an architecture does. Explore the models architects and designers should produce and learn why the models are so important to keep separate. Understand why it is vital to separate functional from nonfunctional requirements and how this affects architecture, design, and even code and test. Explore what a conceptual architectural model should look like vs. a physical one, and for the conceptual design model vs. a physical one—and the timing of all four models. Finally, explore the impact of iterative development on architecture.
Agile is both a set of practices and a mindset. Success lies in understanding both “Doing Agile” as well as “Being Agile”. In this hands-on session, 5 key practices to support an Agile Mindset will be demonstrated so that you have some practical tools use immediately at work. You will also be left with some deeper challenges about what it takes achieve Organizational Agility.
Here are the 10 most important Navigation Secrets for Execs and Coaches for guiding a successful Agile Transformation. Key Lessons from years of industry experience.
This document discusses reinventing organizations and moving towards more conscious and effective organizational cultures. It provides an overview of the Laloux culture model which plots organizational cultures on a scale from low to high effectiveness based on factors like consciousness, trust, and structure. Activities are suggested for participants to reflect on where their own organization currently sits on this model and what aspects could be improved. The document advocates for evolving organizational cultures by growing both consciousness among people and enabling structures, rather than following any specific blueprint. It emphasizes finding one's own path to positive change through inspiration, listening, choosing directions to move in, and applying learnings in a way that fits one's situation.
These slides (from Agile Toronto 2015) describe how we may dare to create environments where Agile may flourish so we have Organizational Agility.
My message is really simple:
If you want Breakthrough Results
Cultivate Culture to
Create Places People Love to Work and
Start with Yourself.
Reinventing Organizations for Enterprise AgilityMichael Sahota
We present an alternative view to fitting agile into larger organisations. Inspired by Fred Laloux’ book “Reinventing Organisations”, we offer a coherent and comprehensive model for organizational development which encompasses the past and guides us into the future. Agile finds its place in these concepts, and becomes a means to move between the model’s stages.
As a leader in an organization on its agile journey, you’ll notice at various pain points that increasing agility struggles with existing organizational structures, governance systems and management expectations. We’ve understood for a while that the prevalent ways of how we run organizations are not compatible with Agile. We’ve tried to package Agile in a way that makes sense to people in organizations working the classical way.
Learn what’s new and essential about this model: the idea of organizational models developing with the evolution of human consciousness, progressing in clear stages. Now being a time where a new organisational model is emerging, and what that looks like. Learn how self-management, wholeness and evolutionary purpose shape organisations where agile will flourish and which agile can help bring about.
"People over Process" slides that are about coming back to the heart of Agile: People!
Intro - People over Process.
Agile = Culture. Whole Agile.
Focus on People: Vulnerability, Authentic Connection, Safety & Trust (VAST)
People-centric organizations (Laloux Culture Model)
People-centric Change
An insider’s account of a manager’s journey of cultural transformation. How our beliefs and assumptions radically shifted. How we found the courage to fully see what is there and accept it. Being vulnerable enough to speak our truth to allow new options to emerge. Developing the boldness to choose them.
This session is ideal for anyone working as or with managers in a traditional hierarchy and wanting to reinvent their organization.
We present an alternative view to fitting Agile into larger organizations. Inspired by Fred Laloux' book "Reinventing Organizations", we offer a coherent and comprehensive model for organizational development which encompasses the past and guides us into the future. Agile finds its place in these concepts, and becomes a means to move between the model's stages.
As a leader in an organization on its agile journey, you'll notice that increasing agility struggles with existing organizational structures, governance systems and management expectations. We've understood for a while that the prevalent ways of how we run organizations are not compatible with Agile. We've tried to package Agile in a way that makes sense to people in organizations working the classical way.
Learn what's new and essential about this model: the idea of organizational models developing with the evolution of human consciousness, progressing in clear stages. Now being a time where a new organizational model is emerging, and what that looks like. Learn how self-management, wholeness and evolutionary purpose shape organizations where agile will flourish and which agile can help bring about.
Whole Agile - Unleashing People & Organizations Michael Sahota
In order to fully unleash the potential of workers we need to augment Agile/Scrum with Valuing People and rewire Organizational Governance.
Valuing People is about building a place where the whole person is welcome. Where there is safety, trust and authentic connection.
Organizational Governance refers to the approaches we use to run organizations: organizational structure, planning & control, roles & titles, compensation, performance management, information access, leadership and power. It has been well understood that these typically impact Scrum significantly.
Scrum and Kanban - Getting the Most from EachMichael Sahota
Scrum is the most popular Agile methodology with Kanban a growing second choice. Learn about the core parts of each one as well as how they differ so that you can find the best fit for your team or organizational context. For example, Scrum is great when you want to shake up the status quo and transform the way you work. Kanban is great when small changes are a better fit for the environment. Learn how they work and how you can use them in your environment.
We outline a fundamentally different approach for organizational change: one where valuing people is integral to building lasting success.
Agile and Lean are a means to an end. Once we are clear what our goals are and our approach is consistent with what we truly value, then we may hope for success.
When we simplify the Agile Manifesto’s “Individuals and Interactions over Processes and Tools” we get “People over Process”. Agile is about people. It’s about a people-first culture. Lean is simliar.
Sadly, many organizations are mired in organizational debt: mistrust, politics and fear. Changing the process won’t fix this. We need to go to the root of it - to find a way to talk about and shift to a healthier culture: one that values people.
The VAST (Vulnerability, Authentic Connection, Safety and Trust) model makes the dynamics of human systems visible and clarifies where we may apply leverage to foster lasting change.
Case study on a transformation of a 100 person department.
What I did (that made the difference):
1. Uncover what’s really going on
2. Share observations in a loving and caring way
3. Help people choose their own reality and destiny
Sticky notes can help optimize reading and handling complexity by allowing you to break down complex information into simple pieces represented by individual notes that you can physically arrange and rearrange to better understand relationships and flow. The notes serve as visual representations that aid comprehension and creative thinking.
Top 10 Agile Gotchas, Problems and Challenges + What you can do about themMichael Sahota
The document discusses common problems teams face when implementing Agile practices, such as long sprint planning meetings, boring daily standups, and unfinished user stories at the end of each sprint. It provides suggestions for how to address these issues, such as splitting large stories into smaller ones, focusing daily standups on planning for the day, and using retrospectives to understand why stories aren't finished and make improvements. The document emphasizes the importance of team culture and fit for successful Agile adoption.
This document discusses Agile principles and practices for managing changing priorities and improving visibility, productivity, quality, and reducing risk. It emphasizes that most value comes from developing the right mindset and culture, not just practices. Culture provides the greatest leverage for change. Specific techniques mentioned include value stream mapping, innovation games, and strategic play to reveal patterns and encourage partnership, seeing people as valuable, courage, vulnerability, and continuous learning.
The business case for agile transformationMichael Sahota
There is a wide array of qualitative and quantitative research demonstrating the benefits of Agile. Unfortunately, this research does not disambiguate between the results from Agile Adoption of practices versus Agile Transformation to a new mindset and organizational culture. In this workshop, participants will learn the key differences between Adoption and Transformation as well as characterize the key benefits of each approach. Finally, participants will relate learnings to their current organizations.
Agile 2012 - An Agile Adoption and Transformation Survival GuideMichael Sahota
This survival guide (based on book) will provide you with essential mental models and a framework to navigate safely through the treacherous jungle of Agile adoption and transformation.
As much of the Agile adoption failure is a result of not understanding organizational culture, you will learn how to use the Schneider model to assess your organization.
Designing Low-Latency Systems with Rust and ScyllaDB: An Architectural Deep DiveScyllaDB
Want to learn practical tips for designing systems that can scale efficiently without compromising speed?
Join us for a workshop where we’ll address these challenges head-on and explore how to architect low-latency systems using Rust. During this free interactive workshop oriented for developers, engineers, and architects, we’ll cover how Rust’s unique language features and the Tokio async runtime enable high-performance application development.
As you explore key principles of designing low-latency systems with Rust, you will learn how to:
- Create and compile a real-world app with Rust
- Connect the application to ScyllaDB (NoSQL data store)
- Negotiate tradeoffs related to data modeling and querying
- Manage and monitor the database for consistently low latencies
This is the keynote of the Into the Box conference, highlighting the release of the BoxLang JVM language, its key enhancements, and its vision for the future.
Special Meetup Edition - TDX Bengaluru Meetup #52.pptxshyamraj55
We’re bringing the TDX energy to our community with 2 power-packed sessions:
🛠️ Workshop: MuleSoft for Agentforce
Explore the new version of our hands-on workshop featuring the latest Topic Center and API Catalog updates.
📄 Talk: Power Up Document Processing
Dive into smart automation with MuleSoft IDP, NLP, and Einstein AI for intelligent document workflows.
Mastering Advance Window Functions in SQL.pdfSpiral Mantra
How well do you really know SQL?📊
.
.
If PARTITION BY and ROW_NUMBER() sound familiar but still confuse you, it’s time to upgrade your knowledge
And you can schedule a 1:1 call with our industry experts: https://spiralmantra.com/contact-us/ or drop us a mail at [email protected]
Unlocking the Power of IVR: A Comprehensive Guidevikasascentbpo
Streamline customer service and reduce costs with an IVR solution. Learn how interactive voice response systems automate call handling, improve efficiency, and enhance customer experience.
TrustArc Webinar: Consumer Expectations vs Corporate Realities on Data Broker...TrustArc
Most consumers believe they’re making informed decisions about their personal data—adjusting privacy settings, blocking trackers, and opting out where they can. However, our new research reveals that while awareness is high, taking meaningful action is still lacking. On the corporate side, many organizations report strong policies for managing third-party data and consumer consent yet fall short when it comes to consistency, accountability and transparency.
This session will explore the research findings from TrustArc’s Privacy Pulse Survey, examining consumer attitudes toward personal data collection and practical suggestions for corporate practices around purchasing third-party data.
Attendees will learn:
- Consumer awareness around data brokers and what consumers are doing to limit data collection
- How businesses assess third-party vendors and their consent management operations
- Where business preparedness needs improvement
- What these trends mean for the future of privacy governance and public trust
This discussion is essential for privacy, risk, and compliance professionals who want to ground their strategies in current data and prepare for what’s next in the privacy landscape.
Noah Loul Shares 5 Steps to Implement AI Agents for Maximum Business Efficien...Noah Loul
Artificial intelligence is changing how businesses operate. Companies are using AI agents to automate tasks, reduce time spent on repetitive work, and focus more on high-value activities. Noah Loul, an AI strategist and entrepreneur, has helped dozens of companies streamline their operations using smart automation. He believes AI agents aren't just tools—they're workers that take on repeatable tasks so your human team can focus on what matters. If you want to reduce time waste and increase output, AI agents are the next move.
Andrew Marnell: Transforming Business Strategy Through Data-Driven InsightsAndrew Marnell
With expertise in data architecture, performance tracking, and revenue forecasting, Andrew Marnell plays a vital role in aligning business strategies with data insights. Andrew Marnell’s ability to lead cross-functional teams ensures businesses achieve sustainable growth and operational excellence.
HCL Nomad Web – Best Practices and Managing Multiuser Environmentspanagenda
Webinar Recording: https://www.panagenda.com/webinars/hcl-nomad-web-best-practices-and-managing-multiuser-environments/
HCL Nomad Web is heralded as the next generation of the HCL Notes client, offering numerous advantages such as eliminating the need for packaging, distribution, and installation. Nomad Web client upgrades will be installed “automatically” in the background. This significantly reduces the administrative footprint compared to traditional HCL Notes clients. However, troubleshooting issues in Nomad Web present unique challenges compared to the Notes client.
Join Christoph and Marc as they demonstrate how to simplify the troubleshooting process in HCL Nomad Web, ensuring a smoother and more efficient user experience.
In this webinar, we will explore effective strategies for diagnosing and resolving common problems in HCL Nomad Web, including
- Accessing the console
- Locating and interpreting log files
- Accessing the data folder within the browser’s cache (using OPFS)
- Understand the difference between single- and multi-user scenarios
- Utilizing Client Clocking
Role of Data Annotation Services in AI-Powered ManufacturingAndrew Leo
From predictive maintenance to robotic automation, AI is driving the future of manufacturing. But without high-quality annotated data, even the smartest models fall short.
Discover how data annotation services are powering accuracy, safety, and efficiency in AI-driven manufacturing systems.
Precision in data labeling = Precision on the production floor.
Increasing Retail Store Efficiency How can Planograms Save Time and Money.pptxAnoop Ashok
In today's fast-paced retail environment, efficiency is key. Every minute counts, and every penny matters. One tool that can significantly boost your store's efficiency is a well-executed planogram. These visual merchandising blueprints not only enhance store layouts but also save time and money in the process.
Social Media App Development Company-EmizenTechSteve Jonas
EmizenTech is a trusted Social Media App Development Company with 11+ years of experience in building engaging and feature-rich social platforms. Our team of skilled developers delivers custom social media apps tailored to your business goals and user expectations. We integrate real-time chat, video sharing, content feeds, notifications, and robust security features to ensure seamless user experiences. Whether you're creating a new platform or enhancing an existing one, we offer scalable solutions that support high performance and future growth. EmizenTech empowers businesses to connect users globally, boost engagement, and stay competitive in the digital social landscape.
Quantum Computing Quick Research Guide by Arthur MorganArthur Morgan
This is a Quick Research Guide (QRG).
QRGs include the following:
- A brief, high-level overview of the QRG topic.
- A milestone timeline for the QRG topic.
- Links to various free online resource materials to provide a deeper dive into the QRG topic.
- Conclusion and a recommendation for at least two books available in the SJPL system on the QRG topic.
QRGs planned for the series:
- Artificial Intelligence QRG
- Quantum Computing QRG
- Big Data Analytics QRG
- Spacecraft Guidance, Navigation & Control QRG (coming 2026)
- UK Home Computing & The Birth of ARM QRG (coming 2027)
Any questions or comments?
- Please contact Arthur Morgan at [email protected].
100% human made.
Dev Dives: Automate and orchestrate your processes with UiPath MaestroUiPathCommunity
This session is designed to equip developers with the skills needed to build mission-critical, end-to-end processes that seamlessly orchestrate agents, people, and robots.
📕 Here's what you can expect:
- Modeling: Build end-to-end processes using BPMN.
- Implementing: Integrate agentic tasks, RPA, APIs, and advanced decisioning into processes.
- Operating: Control process instances with rewind, replay, pause, and stop functions.
- Monitoring: Use dashboards and embedded analytics for real-time insights into process instances.
This webinar is a must-attend for developers looking to enhance their agentic automation skills and orchestrate robust, mission-critical processes.
👨🏫 Speaker:
Andrei Vintila, Principal Product Manager @UiPath
This session streamed live on April 29, 2025, 16:00 CET.
Check out all our upcoming Dev Dives sessions at https://community.uipath.com/dev-dives-automation-developer-2025/.
Spark is a powerhouse for large datasets, but when it comes to smaller data workloads, its overhead can sometimes slow things down. What if you could achieve high performance and efficiency without the need for Spark?
At S&P Global Commodity Insights, having a complete view of global energy and commodities markets enables customers to make data-driven decisions with confidence and create long-term, sustainable value. 🌍
Explore delta-rs + CDC and how these open-source innovations power lightweight, high-performance data applications beyond Spark! 🚀
2. Michael - 15+ years in ITV.P. Research and DevelopmentEnterprise ArchitectDirector Software DevelopmentArchitectSenior J2EE DeveloperProject ManagerTeam LeadC++ DeveloperJava DeveloperResearcherM.Sc. in Computer ScienceB.A.Sc. in Engineering Science
3. Michael - 8 years working with AgileAgile CoachLean ConsultantScrum Master
5. Impact of agile on productivity 88% Dr Dobbs Journal, 2008 Survey. Data, summary, and slides downloadable from www.ambysoft.com/surveys/Copyright 2008 Scott W. Ambler www.ambysoft.com/surveys/
6. Impact of agile on quality of systems deployed 77% Copyright 2008 Scott W. Ambler www.ambysoft.com/surveys/
7. Impact of agile on business stakeholder satisfaction 78% Copyright 2008 Scott W. Ambler www.ambysoft.com/surveys/
8. Survey of “good time” or “best time” working at Salesforce.comBefore Agile - 40%92% wouldrecommend Agile to othersWith Agile - 86%
9. DoD prefers an Agile approachAfter years of learning, identified evolutionary delivery (Agile) as the preferred approach over Waterfall
55. The Agile Manifesto sets out valuesIndividuals and interactions over processes and tools Working software over comprehensive documentation Customer collaboration over contract negotiation Responding to change over following a plan Craftsmanship*over crapCommon SenseEnablerWhile there is value in the items on the right, we value the items on the left more* 2008 proposal by Bob Martin
58. Documentation matters too!It is important that details get stored (paper, models, images, video, etc.) to handle:Gaps in time - What did we decide last month?