Scrum is a popular and proven project management framework for rapidly changing development projects, especially those with significant technology uncertainty or evolving requirements. Since its inception fifteen years ago, Scrum has grown to be the leading agile methodology, boasting nearly 100,000 Certified ScrumMasters. In this highly interactive (no slides) introductory session, Mitch Lacey serves up the tools you need to get started with Scrum. Using Scrum to manage the session, you will learn the value of prioritization and how to do it, why timeboxing works, and how to determine a release plan using team velocity and more. As you are learning these techniques, Mitch answers your questions to help ensure your successful Scrum and agile adoption. Mitch also describes the roles and responsibilities of the ScrumMaster, the product owner, and each member of the Scrum team. This experiential workshop gets you started on the path to success.
This was some thoughts for maturing our Agile SDLC with some specific notes on how to improve JIRA workflows. This was a discussion slide deck; it's very wordy
How to Jumpstart Enterprise Agile AdoptionTechWell
- Alan Padula presented on how to jumpstart enterprise agile adoption based on his experience leading Intuit Financial Services' (IFS) transformation to agile.
- IFS followed Kotter's 8-step change model, starting with establishing urgency and guiding teams, then getting the vision right and communicating it. They enabled action through extensive training, transition elements, and governance processes. Short-term wins and continuous improvement helped make the change stick.
- Key lessons included focusing on promoters over naysayers, allocating dedicated resources, investing in training and coaches, finding leaders to drive the change, and accepting it takes time for a mindset change.
Marco Tedone is a thought leader who helps clients deliver business value through agile, DevOps, and BDD practices. He has over 15 years of experience transforming organizations to embrace these methods. Currently he is a DevOps and Testing Automation Strategy Lead at HSBC, where he has led several transformation initiatives. His skills include transformational leadership, DevOps, Agile coaching, testing automation, AWS, Java, and various DevOps tools.
Agility at Scale: WebSphere’s Agile TransformationTechWell
In today's rapidly changing environment, organizations—both large and small—must quickly respond to shifting market requirements to remain competitive. To be successful, many are adopting agile development and continuous delivery methodologies to deliver software quickly, while keeping the quality and maintainability high. Several years ago the WebSphere Application Server development teams embarked on the journey from traditional waterfall development to agile. They are now expanding to use both agile and continuous delivery methodologies across their organization worldwide. Susan Hanson shares the challenges of working with a worldwide team across multiple time zones while shifting away from component-based teams. Learn how the team transformed their development processes, tools, and culture to better adapt to changing requirements. See how, by integrating tools, the team is able to have a complete lifecycle from customer-submitted requirements through planning, development, test, and delivery of these requirements back to the customers, allowing for continuous delivery of cloud-based services.
This session is an overview on what DevOps is (to me) and how it impacts traditional organizations the most. DevOps is way more than just continuous delivery! From an Agile (synergetic) mindset, DevOps takes a step beyond and focusses on automation, collaboration and learning. Apart from that I also look forward to what oppurtunities lie ahead when implementing DevOps.
On March 2nd I presented this DevOps Unraveled session for abt 40 IT-managers at business university Nyenrode. This was part of the Masterclass Agile management
(Dutch website http://www.executiveeducation.nl/open-programmas/programmadetails/masterclass-agile-management/sectie/introductie.html ).
DevOps is the combination of cultural philosophies, practices, and tools that increases an organization's ability to deliver applications and services at high velocity: evolving and improving products at a faster pace than organizations using traditional software development and infrastructure management processes.
This was some thoughts for maturing our Agile SDLC with some specific notes on how to improve JIRA workflows. This was a discussion slide deck; it's very wordy
How to Jumpstart Enterprise Agile AdoptionTechWell
- Alan Padula presented on how to jumpstart enterprise agile adoption based on his experience leading Intuit Financial Services' (IFS) transformation to agile.
- IFS followed Kotter's 8-step change model, starting with establishing urgency and guiding teams, then getting the vision right and communicating it. They enabled action through extensive training, transition elements, and governance processes. Short-term wins and continuous improvement helped make the change stick.
- Key lessons included focusing on promoters over naysayers, allocating dedicated resources, investing in training and coaches, finding leaders to drive the change, and accepting it takes time for a mindset change.
Marco Tedone is a thought leader who helps clients deliver business value through agile, DevOps, and BDD practices. He has over 15 years of experience transforming organizations to embrace these methods. Currently he is a DevOps and Testing Automation Strategy Lead at HSBC, where he has led several transformation initiatives. His skills include transformational leadership, DevOps, Agile coaching, testing automation, AWS, Java, and various DevOps tools.
Agility at Scale: WebSphere’s Agile TransformationTechWell
In today's rapidly changing environment, organizations—both large and small—must quickly respond to shifting market requirements to remain competitive. To be successful, many are adopting agile development and continuous delivery methodologies to deliver software quickly, while keeping the quality and maintainability high. Several years ago the WebSphere Application Server development teams embarked on the journey from traditional waterfall development to agile. They are now expanding to use both agile and continuous delivery methodologies across their organization worldwide. Susan Hanson shares the challenges of working with a worldwide team across multiple time zones while shifting away from component-based teams. Learn how the team transformed their development processes, tools, and culture to better adapt to changing requirements. See how, by integrating tools, the team is able to have a complete lifecycle from customer-submitted requirements through planning, development, test, and delivery of these requirements back to the customers, allowing for continuous delivery of cloud-based services.
This session is an overview on what DevOps is (to me) and how it impacts traditional organizations the most. DevOps is way more than just continuous delivery! From an Agile (synergetic) mindset, DevOps takes a step beyond and focusses on automation, collaboration and learning. Apart from that I also look forward to what oppurtunities lie ahead when implementing DevOps.
On March 2nd I presented this DevOps Unraveled session for abt 40 IT-managers at business university Nyenrode. This was part of the Masterclass Agile management
(Dutch website http://www.executiveeducation.nl/open-programmas/programmadetails/masterclass-agile-management/sectie/introductie.html ).
DevOps is the combination of cultural philosophies, practices, and tools that increases an organization's ability to deliver applications and services at high velocity: evolving and improving products at a faster pace than organizations using traditional software development and infrastructure management processes.
The document discusses two types of "Agile elephants" - hiding elephants which provide little information and fighting elephants which provide contradictory information. It focuses on how to handle non-functional requirements (NFRs) and technical stories, which are often elephants in Agile projects. It recommends tracking NFRs in acceptance criteria, backlogs, definitions of done, or separate specifications. Technical stories should not be treated as user stories, and the document discusses debates around including them in velocity estimates. It also provides techniques for estimating entire projects by decomposing epics and features into user stories.
The Scaled Agile Framework (SAFe) is an agile framework for enterprise-scale organizations. It addresses challenges of architecture, integration, funding, and roles at scale. SAFe has three levels - portfolio, program, and team. At the portfolio level, investment themes drive budget allocations. The program level uses Agile Release Trains of 5-10 teams to deliver value in 10 week iterations. Teams use Scrum or Kanban with 2 week iterations. SAFe aims to apply lean-agile principles at an enterprise scale.
Leading enterprise transformation lessons adopting agile in governmentAgileDenver
The document summarizes lessons learned from adopting agile practices at the National Geospatial Technical Operations Center (NGTOC). It describes how NGTOC previously managed systems development in a disorganized way without clear processes or communication. It then explains changes made by adopting agile tools and methods like prioritizing requirements, organizing work into teams, and improving communication platforms. As a result, NGTOC saw improved code quality, workforce collaboration, planning, and ability to manage uncertainty. The document outlines leadership strategies that helped enable the agile transformation, such as allowing experimentation, spreading lessons learned, understanding what decisions to make themselves versus empowering the workforce, and facilitating cultural change.
Understanding the DevOps Tooling LandscapeXebiaLabs
The document discusses understanding the DevOps tooling landscape. It begins with introductions and an agenda. The presentation then discusses what constitutes a DevOps tool, focusing on tools related to application and service delivery. Five common categories of DevOps tools are identified: task execution, cloud/container management, system provisioning/configuration, application integration, and application deployment. Each category is described in terms of its functions, strengths, and limitations. The presentation concludes with guidance on selecting the right tools based on organizational goals and needs rather than a single solution.
This document discusses DevOps and explores whether it is a process, tool, or mindset. It describes the historical separation of development and operations teams and the problems this caused. DevOps aims to bridge this divide by promoting collaboration between teams. While tools can help, especially for large deployments, adopting a collaborative culture is most important. The document examines various aspects of DevOps including principles, processes, tools, challenges, success factors and benefits. It argues that having the right mindset is key and that infrastructure should now be treated as code.
This document discusses applying agile concepts to data warehousing projects to deliver results faster. It begins with the presenter's background and an overview of Snowflake Computing. It then covers the 12 principles of agile, explaining how each could be applied in a data warehousing context, such as having daily standups with business users, using prioritized backlogs and user stories, delivering working code/reports frequently in short iterations focused on a subject area, and using data vault modeling techniques. Retrospectives are emphasized as important for continuous improvement.
DevOps or Devops - living in silos or living as a teamVinay Krishna
DevOps aims to break down silos between development and operations teams and foster collaboration between the two as one unified team with a shared goal of continuously delivering value. While tools are part of DevOps, the cultural shift toward collaboration is more important. This involves developers and operations working together throughout the entire product development process from requirements gathering to deployment. Benefits include a common language between teams, knowledge sharing, and breaking down barriers between development and operations.
Relieveing the Testing Bottle Neck - WebinarCprime
When shifting to Agile, testing is often a bottleneck in the process, as it is the last step in the cycle. But, the responsibility to remove the bottleneck is not on the tester alone.
DevOps - an Agile Perspective (at Scale)Brad Appleton
by Brad Appleton, Agile Day Chicago 2018, October 26 2018;
This presentation gives a comprehensive introduction to DevOps, for Agile development practitioners. In 2018, there are many misunderstandings about Agile & DevOps and how they relate to one another. Too many think of Agile (development) as primarily "Scrum", and that DevOps is Continuous Integration & Delivery (both of which are wrong). This presentation describes the meaning, origin & history of DevOps from an Agile development perspective.
Kanban was originally created as a scheduling system to help manufacturing organizations determine what to produce, when to produce it, and how much to produce. Although this may not sound like software development, these lean principles can be successfully applied to development teams to improve the delivery of value through better visibility and limits on work in process.
This webinar will provide an overview of the Kanban method, including the history and motivation, the core principles and practices, and how these apply to efficiency and process improvement in software development.
Come join us for this free Webinar!
The document introduces the Scaled Agile Framework (SAFe) for helping organizations adopt agile practices at scale. It discusses how SAFe addresses the needs of large software enterprises by drawing from agile, lean principles and practices. SAFe provides a proven framework for synchronizing alignment, collaboration and delivery across multiple agile teams working on large programs and portfolios. It emphasizes values like continuous delivery of value, transparency, quality code and respect for individuals.
DevOpsGuys - How to get started with DevOps - Redgate Webinar April 2017DevOpsGroup
DevOpsGuys - How to get started with DevOps - Redgate Webinar April 2017. 9 steps to DevOps Transformation
#SystemsThinking
#MakeWorkVisible
#MeasureWhatsImportant
#ActOnFeedback
#IdentifyTheGoal
#BeAgile
#DeliverContinuously
#BuildTrust
#AlignToValue
#OptimiseForFlow
Victoria Schiffer has had a varied career spanning roles in software engineering, product management, business analysis, delivery lead, agile coaching, and leadership coaching. She shares her career journey and insights on adapting to change, embracing challenges, and maintaining a growth mindset. She emphasizes the importance of being a role model, pushing herself outside her comfort zone, and creating opportunities for other women in technology.
AgileLIVE – Accelerate Enterprise Agile with the Scaled Agile Framework®: Part IVersionOne
Interested in finding out how to scale agile faster, easier and smarter using the Scaled Agile Framework® (SAFe)? If so, make sure you watch this two-part webinar series!
Scrum, XP, Kanban and related methods have been proven to provide step changes in productivity and quality for software teams. However, these methods do not have the native constructs necessary to scale across the enterprise. What the industry desperately needs is a solution that moves from a set of simplistic, disparate, development-centric methods, to a scalable, unified approach that addresses the complex constructs and additional stakeholders in the organization – and accelerates the realization of enterprise-class product or service initiatives via aligned and cooperative solution development.
Part I: Join Dean Leffingwell, software industry veteran and Lean Systems Society Fellow, for an overview of SAFe, a publicly–accessible knowledge base of proven lean and agile practices for enterprise-class software development.
Dean Leffingwell, software industry veteran and Lean Systems Society Fellow, has spent his career helping software teams achieve their goals. A renowned methodologist, author, coach, entrepreneur and executive, Dean's most recent project is the Scaled Agile Framework (scaledagileframework.com), a public-facing website which describes a comprehensive system for scaling lean and agile practices to the largest software enterprises.
Andy Powell is Product Evangelist for VersionOne and Scaled Agile Framework Program Consultant. During his 12-year career in the software development industry, Andy has assisted in numerous 500+ person agile tool rollouts with companies such as Siemens, Adobe, EMC and Sabre, giving him considerable experience in leading major projects. Andy received a Bachelor of Science degree in Mechanical Engineering from the University of Notre Dame and graduated magna cum laude.
Lee Cunningham is an Enterprise Agile Coach for VersionOne focused on agile program and portfolio management. Lee has trained and consulted with hundreds of teams in organizations of all sizes in the US, Canada and the UK. Lee served in the United States Air Force and earned a Bachelor of Business Administration degree from the University of North Florida.
Scaled Agile Framework in 10 minutes (CAS2015)Unai Roldán
Scaled Agile Framework in 10 minutes (SAFe 3.0)
- Scaled: SAFe is designed for large-scale software development ecosystems of 50-125 people who need to resolve inter-dependencies
- Agile: SAFe is based on 9 Lean-Agile principles
- Framework: SAFe is a collection of a proven efficacy tools, and you only have to use what you need
https://www.youtube.com/watch?v=vysQQx7pQzg
El objetivo de la Lightning Talk es dar una visión "light" pero completa de lo que propone Scaled Agile Framework 3.0 como marco de referencia para el escalado de Agile.
Scaled Agile Framework es uno de los marcos de referencia para escalado de Agile que mayor aceptación está teniendo a día de hoy, sobre todo cuando hablamos de grandes organizaciones. El marco SAFe parte de las capas de abstracción clásicas de una organización para estructurar un cambio de perspectiva y de cultura basándose en los 4 valores y 9 principios Lean-Agile, apoyándose además en las prácticas Scrum-XP de desarrollo de productos. En la charla descubriremos de manera rápida los roles, artefactos y ceremonias que plantea el marco para conseguir un cambio de paradigma sostenible en las organizaciones.
Unai Roldán
UST Global
This document provides an overview of scaled agile portfolio management terminology and delivery model. It describes key terms like Potentially Shippable Increment (PSI), Epic, Feature, Enabler, Story, and Roadmap. It outlines the scaled agile delivery model which includes a portfolio backlog, epic roadmaps, program roadmaps, and team backlogs to plan and manage work at the portfolio, program, and team levels. It also includes a business kanban system to prioritize and allocate investment across the portfolio.
Be agile. Scale up. Stay Lean with SAFe by Michael StumpAgile ME
Today’s successful companies are recognizing that software is increasingly a competitive advantage for their business. Real, tangible software development value occurs only when end-users are successfully operating the software in their environment. To ensure a faster flow of value to the business, the Scaled Agile Framework helps teams successfully deliver a differentiated and engaging customer experience, achieve quicker time to value, and gain increased capacity to innovate. The process of deploying software builds to production is no less important than developing and testing the new functionality. As an industry, we are currently mastering more Agile, better and faster methods for incrementally developing potential user value. In practice, however, these achievements are jeopardized by poorly managed deployments that happen too late in the lifecycle and delays value delivery. Bringing deployment operations (DevOps) onboard the Agile Release Train, engaging them in the PSI planning and other program level events, and establishing environments, practices and disciplined procedures in support of a continuous deployment pipeline helps the enterprise enable faster feedback and a more predictable value delivery rhythm. Join Michael Stump (Principal Contributor to SAFe), Thought Leader from Scaled Agile Inc. and software industry veteran to get an in-depth overview of how SAFe together with DevOps can provide the most customer value and quality in the sustainable shortest lead time.
The impact of innovation on travel and tourism industries (World Travel Marke...Brian Solis
From the impact of Pokemon Go on Silicon Valley to artificial intelligence, futurist Brian Solis talks to Mathew Parsons of World Travel Market about the future of travel, tourism and hospitality.
Reuters: Pictures of the Year 2016 (Part 2)maditabalnco
This document contains 20 photos from news events around the world between January and November 2016. The photos show international events like the US presidential election, the conflict in Ukraine, the migrant crisis in Europe, the Rio Olympics, and more. They also depict human interest stories and natural phenomena from various countries.
The document discusses two types of "Agile elephants" - hiding elephants which provide little information and fighting elephants which provide contradictory information. It focuses on how to handle non-functional requirements (NFRs) and technical stories, which are often elephants in Agile projects. It recommends tracking NFRs in acceptance criteria, backlogs, definitions of done, or separate specifications. Technical stories should not be treated as user stories, and the document discusses debates around including them in velocity estimates. It also provides techniques for estimating entire projects by decomposing epics and features into user stories.
The Scaled Agile Framework (SAFe) is an agile framework for enterprise-scale organizations. It addresses challenges of architecture, integration, funding, and roles at scale. SAFe has three levels - portfolio, program, and team. At the portfolio level, investment themes drive budget allocations. The program level uses Agile Release Trains of 5-10 teams to deliver value in 10 week iterations. Teams use Scrum or Kanban with 2 week iterations. SAFe aims to apply lean-agile principles at an enterprise scale.
Leading enterprise transformation lessons adopting agile in governmentAgileDenver
The document summarizes lessons learned from adopting agile practices at the National Geospatial Technical Operations Center (NGTOC). It describes how NGTOC previously managed systems development in a disorganized way without clear processes or communication. It then explains changes made by adopting agile tools and methods like prioritizing requirements, organizing work into teams, and improving communication platforms. As a result, NGTOC saw improved code quality, workforce collaboration, planning, and ability to manage uncertainty. The document outlines leadership strategies that helped enable the agile transformation, such as allowing experimentation, spreading lessons learned, understanding what decisions to make themselves versus empowering the workforce, and facilitating cultural change.
Understanding the DevOps Tooling LandscapeXebiaLabs
The document discusses understanding the DevOps tooling landscape. It begins with introductions and an agenda. The presentation then discusses what constitutes a DevOps tool, focusing on tools related to application and service delivery. Five common categories of DevOps tools are identified: task execution, cloud/container management, system provisioning/configuration, application integration, and application deployment. Each category is described in terms of its functions, strengths, and limitations. The presentation concludes with guidance on selecting the right tools based on organizational goals and needs rather than a single solution.
This document discusses DevOps and explores whether it is a process, tool, or mindset. It describes the historical separation of development and operations teams and the problems this caused. DevOps aims to bridge this divide by promoting collaboration between teams. While tools can help, especially for large deployments, adopting a collaborative culture is most important. The document examines various aspects of DevOps including principles, processes, tools, challenges, success factors and benefits. It argues that having the right mindset is key and that infrastructure should now be treated as code.
This document discusses applying agile concepts to data warehousing projects to deliver results faster. It begins with the presenter's background and an overview of Snowflake Computing. It then covers the 12 principles of agile, explaining how each could be applied in a data warehousing context, such as having daily standups with business users, using prioritized backlogs and user stories, delivering working code/reports frequently in short iterations focused on a subject area, and using data vault modeling techniques. Retrospectives are emphasized as important for continuous improvement.
DevOps or Devops - living in silos or living as a teamVinay Krishna
DevOps aims to break down silos between development and operations teams and foster collaboration between the two as one unified team with a shared goal of continuously delivering value. While tools are part of DevOps, the cultural shift toward collaboration is more important. This involves developers and operations working together throughout the entire product development process from requirements gathering to deployment. Benefits include a common language between teams, knowledge sharing, and breaking down barriers between development and operations.
Relieveing the Testing Bottle Neck - WebinarCprime
When shifting to Agile, testing is often a bottleneck in the process, as it is the last step in the cycle. But, the responsibility to remove the bottleneck is not on the tester alone.
DevOps - an Agile Perspective (at Scale)Brad Appleton
by Brad Appleton, Agile Day Chicago 2018, October 26 2018;
This presentation gives a comprehensive introduction to DevOps, for Agile development practitioners. In 2018, there are many misunderstandings about Agile & DevOps and how they relate to one another. Too many think of Agile (development) as primarily "Scrum", and that DevOps is Continuous Integration & Delivery (both of which are wrong). This presentation describes the meaning, origin & history of DevOps from an Agile development perspective.
Kanban was originally created as a scheduling system to help manufacturing organizations determine what to produce, when to produce it, and how much to produce. Although this may not sound like software development, these lean principles can be successfully applied to development teams to improve the delivery of value through better visibility and limits on work in process.
This webinar will provide an overview of the Kanban method, including the history and motivation, the core principles and practices, and how these apply to efficiency and process improvement in software development.
Come join us for this free Webinar!
The document introduces the Scaled Agile Framework (SAFe) for helping organizations adopt agile practices at scale. It discusses how SAFe addresses the needs of large software enterprises by drawing from agile, lean principles and practices. SAFe provides a proven framework for synchronizing alignment, collaboration and delivery across multiple agile teams working on large programs and portfolios. It emphasizes values like continuous delivery of value, transparency, quality code and respect for individuals.
DevOpsGuys - How to get started with DevOps - Redgate Webinar April 2017DevOpsGroup
DevOpsGuys - How to get started with DevOps - Redgate Webinar April 2017. 9 steps to DevOps Transformation
#SystemsThinking
#MakeWorkVisible
#MeasureWhatsImportant
#ActOnFeedback
#IdentifyTheGoal
#BeAgile
#DeliverContinuously
#BuildTrust
#AlignToValue
#OptimiseForFlow
Victoria Schiffer has had a varied career spanning roles in software engineering, product management, business analysis, delivery lead, agile coaching, and leadership coaching. She shares her career journey and insights on adapting to change, embracing challenges, and maintaining a growth mindset. She emphasizes the importance of being a role model, pushing herself outside her comfort zone, and creating opportunities for other women in technology.
AgileLIVE – Accelerate Enterprise Agile with the Scaled Agile Framework®: Part IVersionOne
Interested in finding out how to scale agile faster, easier and smarter using the Scaled Agile Framework® (SAFe)? If so, make sure you watch this two-part webinar series!
Scrum, XP, Kanban and related methods have been proven to provide step changes in productivity and quality for software teams. However, these methods do not have the native constructs necessary to scale across the enterprise. What the industry desperately needs is a solution that moves from a set of simplistic, disparate, development-centric methods, to a scalable, unified approach that addresses the complex constructs and additional stakeholders in the organization – and accelerates the realization of enterprise-class product or service initiatives via aligned and cooperative solution development.
Part I: Join Dean Leffingwell, software industry veteran and Lean Systems Society Fellow, for an overview of SAFe, a publicly–accessible knowledge base of proven lean and agile practices for enterprise-class software development.
Dean Leffingwell, software industry veteran and Lean Systems Society Fellow, has spent his career helping software teams achieve their goals. A renowned methodologist, author, coach, entrepreneur and executive, Dean's most recent project is the Scaled Agile Framework (scaledagileframework.com), a public-facing website which describes a comprehensive system for scaling lean and agile practices to the largest software enterprises.
Andy Powell is Product Evangelist for VersionOne and Scaled Agile Framework Program Consultant. During his 12-year career in the software development industry, Andy has assisted in numerous 500+ person agile tool rollouts with companies such as Siemens, Adobe, EMC and Sabre, giving him considerable experience in leading major projects. Andy received a Bachelor of Science degree in Mechanical Engineering from the University of Notre Dame and graduated magna cum laude.
Lee Cunningham is an Enterprise Agile Coach for VersionOne focused on agile program and portfolio management. Lee has trained and consulted with hundreds of teams in organizations of all sizes in the US, Canada and the UK. Lee served in the United States Air Force and earned a Bachelor of Business Administration degree from the University of North Florida.
Scaled Agile Framework in 10 minutes (CAS2015)Unai Roldán
Scaled Agile Framework in 10 minutes (SAFe 3.0)
- Scaled: SAFe is designed for large-scale software development ecosystems of 50-125 people who need to resolve inter-dependencies
- Agile: SAFe is based on 9 Lean-Agile principles
- Framework: SAFe is a collection of a proven efficacy tools, and you only have to use what you need
https://www.youtube.com/watch?v=vysQQx7pQzg
El objetivo de la Lightning Talk es dar una visión "light" pero completa de lo que propone Scaled Agile Framework 3.0 como marco de referencia para el escalado de Agile.
Scaled Agile Framework es uno de los marcos de referencia para escalado de Agile que mayor aceptación está teniendo a día de hoy, sobre todo cuando hablamos de grandes organizaciones. El marco SAFe parte de las capas de abstracción clásicas de una organización para estructurar un cambio de perspectiva y de cultura basándose en los 4 valores y 9 principios Lean-Agile, apoyándose además en las prácticas Scrum-XP de desarrollo de productos. En la charla descubriremos de manera rápida los roles, artefactos y ceremonias que plantea el marco para conseguir un cambio de paradigma sostenible en las organizaciones.
Unai Roldán
UST Global
This document provides an overview of scaled agile portfolio management terminology and delivery model. It describes key terms like Potentially Shippable Increment (PSI), Epic, Feature, Enabler, Story, and Roadmap. It outlines the scaled agile delivery model which includes a portfolio backlog, epic roadmaps, program roadmaps, and team backlogs to plan and manage work at the portfolio, program, and team levels. It also includes a business kanban system to prioritize and allocate investment across the portfolio.
Be agile. Scale up. Stay Lean with SAFe by Michael StumpAgile ME
Today’s successful companies are recognizing that software is increasingly a competitive advantage for their business. Real, tangible software development value occurs only when end-users are successfully operating the software in their environment. To ensure a faster flow of value to the business, the Scaled Agile Framework helps teams successfully deliver a differentiated and engaging customer experience, achieve quicker time to value, and gain increased capacity to innovate. The process of deploying software builds to production is no less important than developing and testing the new functionality. As an industry, we are currently mastering more Agile, better and faster methods for incrementally developing potential user value. In practice, however, these achievements are jeopardized by poorly managed deployments that happen too late in the lifecycle and delays value delivery. Bringing deployment operations (DevOps) onboard the Agile Release Train, engaging them in the PSI planning and other program level events, and establishing environments, practices and disciplined procedures in support of a continuous deployment pipeline helps the enterprise enable faster feedback and a more predictable value delivery rhythm. Join Michael Stump (Principal Contributor to SAFe), Thought Leader from Scaled Agile Inc. and software industry veteran to get an in-depth overview of how SAFe together with DevOps can provide the most customer value and quality in the sustainable shortest lead time.
The impact of innovation on travel and tourism industries (World Travel Marke...Brian Solis
From the impact of Pokemon Go on Silicon Valley to artificial intelligence, futurist Brian Solis talks to Mathew Parsons of World Travel Market about the future of travel, tourism and hospitality.
Reuters: Pictures of the Year 2016 (Part 2)maditabalnco
This document contains 20 photos from news events around the world between January and November 2016. The photos show international events like the US presidential election, the conflict in Ukraine, the migrant crisis in Europe, the Rio Olympics, and more. They also depict human interest stories and natural phenomena from various countries.
Gave a talk at StartCon about the future of Growth. I touch on viral marketing / referral marketing, fake news and social media, and marketplaces. Finally, the slides go through future technology platforms and how things might evolve there.
The Six Highest Performing B2B Blog Post FormatsBarry Feldman
If your B2B blogging goals include earning social media shares and backlinks to boost your search rankings, this infographic lists the size best approaches.
1) The document discusses the opportunity for technology to improve organizational efficiency and transition economies into a "smart and clean world."
2) It argues that aggregate efficiency has stalled at around 22% for 30 years due to limitations of the Second Industrial Revolution, but that digitizing transport, energy, and communication through technologies like blockchain can help manage resources and increase efficiency.
3) Technologies like precision agriculture, cloud computing, robotics, and autonomous vehicles may allow for "dematerialization" and do more with fewer physical resources through effects like reduced waste and need for transportation/logistics infrastructure.
32 Ways a Digital Marketing Consultant Can Help Grow Your BusinessBarry Feldman
How can a digital marketing consultant help your business? In this resource we'll count the ways. 24 additional marketing resources are bundled for free.
Baksheesh Singh Gurudatta is a Scrum Master based in Shanghai, China seeking new opportunities. He has over 4 years of experience in roles such as Scrum Master, Network Engineer, IT Process Engineer, and IT Consultant. Gurudatta holds several Agile certifications including CSM, SPOAC, SMAC, and STMAC. He is skilled in Scrum practices, network management, IT management, and business analysis. Gurudatta's experience includes facilitating Scrum ceremonies and coaching teams at Bleum Incorporated in Shanghai.
The document provides an overview of the agile software development process. It begins with defining agile as an iterative and adaptive approach to software development performed collaboratively by self-organizing teams. It then discusses agile principles like valuing customer collaboration, responding to change, and delivering working software frequently. The document also covers specific agile frameworks like Scrum and Extreme Programming, the role of user stories, estimation techniques like planning poker, and ceremonies like daily stand-ups, sprint planning and retrospectives. It concludes by comparing agile to the traditional waterfall model and defining some common agile metrics.
This document discusses concepts and practices related to Scrum project management methodology. It addresses frequently asked questions about Scrum roles like Product Owner and Scrum Master. It also covers Scrum artifacts like the Product Backlog and Sprint Backlog, as well as Scrum events like the Sprint Planning meeting and Daily Scrum. The document provides guidance on properly defining acceptance criteria for user stories, estimating story points, and ensuring the Product Backlog is ready before Sprint Planning.
Agile Scrum Foundation is an entry-level Agile Project Management course that is ideal for individuals and enterprises who are looking to gain a fundamental understanding of Agile methodologies and Scrum practices and covers scrum practices with regards to cross-functional and self-managed teams to produce deliverables during each iteration.
This Agile and Scrum Foundation certification training course accredited by EXIN is ideal for software developers, project team members, team leads, architects, project managers, scrum team members, and any one who is part of IT and project management teams working on projects.
To know more about Agile Scrum Foundation Certification training worldwide,
please contact us at -
Email :support@invensislearning.com
Phone - US +1-910-726-3695,
Website : https://www.invensislearning.com
We often get asked why Scrum has only 3 roles, 3 artifacts and 3 ceremonies. In fact, our customers simply want to know why Scrum works. In these slides we try to explain the principles behind the prescriptions of Scrum, in the form of 5 Whys: Why Scrum? Why 3 Roles? Why 3 Artifacts? Why 3 Ceremonies? And Why agile engineering practices support Scrum?
This document discusses applying an agile mindset beyond software development. It covers key concepts like customer orientation, responsive planning and execution, and learning quickly through experiments. The document advocates forming cross-functional teams organized around customer journeys. Planning methods like Scrum, Kanban, and SAFe are presented as ways to support responsive adaptation. Continuous learning is emphasized through running many small experiments instead of a few large projects. Applying these agile principles in different workplaces through experiments is proposed.
EHS Conducted SCRUM Overview Session for a Corporate Company in Lahore covering Basics i.e. What is Agile & Scrum, Why to use Scrum, Benefits, Values, Artifacts, Events, Scrum Teams & Roles...
Achal Dalvi has over 7 years of experience in IT testing. He has expertise in functional, regression, and database testing. He has experience working on projects for clients in various industries using technologies like Oracle, SQL Server, ALM, and Informatica. He has held roles including team lead and software tester and has experience in the full SDLC. He has a Bachelor's degree in Computer Engineering and is proficient in languages including SQL.
Software Development Process Models (SCRUM Methodology)Muhammad Ahmed
This document provides an overview of software process models and Scrum methodology. It defines a software process model as a description of the sequence of activities carried out in a software engineering project. The key activities include specification, design & implementation, validation, and evolution. Scrum is introduced as an agile software development framework. It utilizes short development cycles called sprints, daily stand-up meetings, product backlogs to track requirements, and emphasizes self-organizing teams and adaptive planning. The benefits of Scrum are discussed as improved productivity, quality, and ability to manage changing requirements.
Learn and Grow:
We give trainings for following courses:
Selenium with Java Online Training
Selenium with C# Online Training
JMeter Online Training
CodedUI Online Training
QTP Online Training
Manual Testing Online Training
ISTQB Certification Training
Scrum Master Training
Website : http://globalsqa.com/onlineTrainings.html
Email : contact@globalsqa.com
This document provides information about business analysis training courses offered by Software Education. It lists their core courses that provide essential skills for business analysts at different stages of their career. It also describes specialty courses that build on the core training. The document discusses Software Education's trainers and their qualifications. It provides an overview of Software Education's complete business analysis training program and capabilities.
The product owner and the scrum team. Can one person do this at scale?Derek Huether
Presented at IIBA Baltimore on March 11, 2014. The last 10 years of Agile have focused on the team. The next 10 years of Agile will focus on the enterprise. That said, should the Product Owner continue to be a single person or does it need to evolve as well? Let's cover the basics and then see how LeadingAgile has been successful at leveraging the Product Owner role at scale.
Read Curriculum vitae of Shwetabh Kumar as Project Manager at Deloitteshwetabhkumar
Hello, My name is Shwetabh Kumar and I am from Hyderabad. Presently I am associated with Deloitte Company as a Project Manager. Skilled in designing and developing modules/products, managing and tracking project execution, executing test scenarios, releasing products to production.
The Agile Readiness Assessment Tool EssayHeidi Owens
This report discusses Scrum, an agile software development methodology. It describes the key roles in Scrum - Product Owner, Scrum Master, and Development Team. It also outlines the core Scrum events - Sprint Planning, Daily Scrum, Sprint Review, and Sprint Retrospective. The report examines the Scrum process and how it aims to deliver working software frequently through short development cycles called sprints. It emphasizes that Scrum provides structure through its roles, events, and artifacts while allowing flexibility through its iterative approach.
This slide share will help users to understand the agile software development methodology and how does it work. It also defines the whole process to implement scrum methodology.
This document discusses an agile project discovery process. It begins with introductions to software development life cycles and why agile is used. Scrum is explained as an agile framework using roles, ceremonies, and artifacts. The discovery process aims to find the right problem to solve through understanding objectives, existing knowledge, gathering requirements to develop hypotheses and conclusions on minimum viable products.
The career summary of Randy Spiess, a focus on customer and continuous improv...Randy Spiess
Randy Spiess is a customer-focused leader seeking a role to continuously improve processes and help teams achieve business objectives. He has over 20 years of experience in software development, quality practices, and Agile/DevOps coaching. Skills include coaching, problem solving, and applying learnings from frameworks like OKRs. Past roles include Agile coach, project manager, and quality manager helping teams improve productivity, quality, and time to market.
Isabel Evans stopped drawing and painting after being told she was not very good at it, which led to a loss of confidence in her creative and professional abilities. However, she realized that attempting creative activities is important for cognitive and emotional development, and that making mistakes and learning from failures allows for growth. By reengaging with failure through art and with support from others, Isabel was able to regain confidence in her abilities and reboot her career. The document discusses different perspectives on failure and the importance of learning from mistakes.
Instill a DevOps Testing Culture in Your Team and Organization TechWell
The DevOps movement is here. Companies across many industries are breaking down siloed IT departments and federating them into product development teams. Testing and its practices are at the heart of these changes. Traditionally, IT organizations have been staffed with mostly manual testers and a limited number of automation and performance engineers. To keep pace with development in the new “you build it, you own it” environment, testing teams and individuals must develop new technical skills and even embrace coding to stay relevant and add greater value to the business. DevOps really starts with testing. Join Adam Auerbach as he explains what DevOps is and how it relates to testing. He describes how testing must change from top to bottom and how to access your own environment to identify improvement opportunities. Adam dives into practices like service virtualization, test data management, and continuous testing so you can understand where you are now and identify steps needed to instill a DevOps testing culture in your team and organization.
Test Design for Fully Automated Build ArchitectureTechWell
This document summarizes a half-day tutorial on test design for fully automated build architectures presented by Melissa Benua of mParticle at STAREAST 2018. The tutorial covered guiding principles for test design including prioritizing important and reliable tests, structuring automated pipelines around components, packages, and releases, and monitoring test results through code coverage, flaky test handling, and logging versus counters. It also included exercises mapping test cases to functional boundaries and categories of tests to pipeline stages.
System-Level Test Automation: Ensuring a Good StartTechWell
Many organizations invest a lot of effort in test automation at the system level but then have serious problems later on. As a leader, how can you ensure that your new automation efforts will get off to a good start? What can you do to ensure that your automation work provides continuing value? This tutorial covers both “theory” and “practice”. Dot Graham explains the critical issues for getting a good start, and Chris Loder describes his experiences in getting good automation started at a number of companies. The tutorial covers the most important management issues you must address for test automation success, particularly when you are new to automation, and how to choose the best approaches for your organization—no matter which automation tools you use. Focusing on system level testing, Dot and Chris explain how automation affects staffing, who should be responsible for which automation tasks, how managers can best support automation efforts to promote success, what you can realistically expect in benefits and how to report them. They explain—for non-techies—the key technical issues that can make or break your automation effort. Come away with your own clarified automation objectives, and a draft test automation strategy to use to plan your own system-level test automation.
Build Your Mobile App Quality and Test StrategyTechWell
Let’s build a mobile app quality and testing strategy together. Whether you have a web, hybrid, or native app, building a quality and testing strategy means (1) knowing what data and tools you have available to make agile decisions, (2) understanding your customers and your competitors, and (3) testing your app under real-world conditions. Jason Arbon guides you through the latest techniques, data, and tools to ensure the awesomeness of your mobile app quality and testing strategy. Leave this interactive session with a strategy for your very own app—or one you pretend to own. The information Jason shares is based on data from Appdiff’s next-gen mobile app testing platform, lessons from Applause/uTest’s crowd, text mining hundreds of millions of app store reviews, and in-depth discussions with top mobile app development teams.
Testing Transformation: The Art and Science for SuccessTechWell
Technologies, testing processes, and the role of the tester have evolved significantly in the past few years with the advent of agile, DevOps, and other new technologies. It is critical that we testing professionals evaluate ourselves and continue to add tangible value to our organizations. In your work, are you focused on the trivial or on real game changers? Jennifer Bonine describes critical elements that help you artfully blend people, process, and technology to create a synergistic relationship that adds value. Jennifer shares ideas on mastering politics, maneuvering core vs. context, and innovating your technology strategies and processes. She explores how new processes can be introduced in an organization, what the role of organizational culture is in determining the success of a project, and how you can know what tools will add value vs. simply adding overhead and complexity. Jennifer reviews critically needed tester skills and discusses a continual learning model to evolve your skills and stay relevant. This discussion can lead you to technologies, processes, and skills you can stake your career on.
We’ve all been there. We work incredibly hard to develop a feature and design tests based on written requirements. We build a detailed test plan that aligns the tests with the software and the documented business needs. And when we put the tests to the software, it all falls apart because the requirements were changed without informing everyone. Mary Thorn says help is at hand. Enter behavior-driven development (BDD), and Cucumber and SpecFlow, tools for running automated acceptance tests and facilitating BDD. Mary explores the nuances of Cucumber and SpecFlow, and shows you how to implement BDD and agile acceptance testing. By fostering collaboration for implementing active requirements via a common language and format, Cucumber and SpecFlow bridge the communication gap between business stakeholders and implementation teams. In this workshop, practice writing feature files with the best practices Mary has discovered over numerous implementations. If you experience developers not coding to requirements, testers not getting requirements updates, or customers who feel out of the loop and don’t get what they ask for, Mary has answers for you.
Develop WebDriver Automated Tests—and Keep Your SanityTechWell
Many teams go crazy because of brittle, high-maintenance automated test suites. Jim Holmes helps you understand how to create a flexible, maintainable, high-value suite of functional tests using Selenium WebDriver. Learn the basics of what to test, what not to test, and how to avoid overlapping with other types of testing. Jim includes both philosophical concepts and hands-on coding. Testers who haven't written code should not be intimidated! We'll pair you up to make sure you're successful. Learn to create practical tests dealing with advanced situations such as input validation, AJAX delays, and working with file downloads. Additionally, discover when you need to work together with developers to create a system that's more easily testable. This tutorial focuses primarily on automating web tests, but many of the same concepts can be applied to other UI environments. Demos and labs will be in C# and Java using WebDriver. Leave this tutorial having learned how to write high-value WebDriver tests—and stay sane while doing so.
DevOps is a cultural shift aimed at streamlining intergroup communication and improving operational efficiency for development and operations groups. Over time, inclusion of other IT groups under the DevOps umbrella has become the norm for many organizations. But even broadening the boundaries of DevOps, the conversation has been largely devoid of the business units’ place at the table. A common mistake organizations make while going through the DevOps transformation is drawing a line at the IT boundary. If that occurs, a larger, more inclusive silo within the organization is created, operating in an informational vacuum and causing operational inefficiency and goal misalignment. Sharing his experiences working on both sides of the fence, Leon Fayer describes the importance of including business units in order to align technology decisions with business goals. Leon discusses inclusion of business units in existing agile processes, benefits of cross-departmental monitoring, and a business-first approach to technology decisions.
Eliminate Cloud Waste with a Holistic DevOps StrategyTechWell
Chris Parlette maintains that renting infrastructure on demand is the most disruptive trend in IT in decades. In 2016, enterprises spent $23B on public cloud IaaS services. By 2020, that figure is expected to reach $65B. The public cloud is now used like a utility, and like any utility, there is waste. Who's responsible for optimizing the infrastructure and reducing wasted expenses? It’s DevOps. The excess expense, known as cloud waste, comprises several interrelated problems: services running when they don't need to be, improperly sized infrastructure, orphaned resources, and shadow IT. There are a few core tenets of DevOps—holistic thinking, no silos, rapid useful feedback, and automation—that can be applied to reducing your cloud waste. Join Chris to learn why you should include continuous cost optimization in your DevOps processes. Automate cost control, reduce your cloud expenses, and make your life easier.
Transform Test Organizations for the New World of DevOpsTechWell
With the recent emergence of DevOps across the industry, testing organizations are being challenged to transform themselves significantly within a short period of time to stay meaningful within their organizations. It’s not easy to plan and approach these changes considering the way testing organizations have remained structured for ages. These challenges start from foundational organizational structures and can cut across leadership influence, competencies, tools strategy, infrastructure, and other dimensions. Sumit Kumar shares his experience assisting various organizations to overcome these challenges using an organized DevOps enablement framework. The framework includes radical restructuring, turning the tools strategy upside down, a multidimensional workforce enablement supported by infrastructure changes, redeveloped collaborations models, and more. From his real world experiences Sumit shares tips for approaching this journey and explains the roadmap for testing organizations to transform themselves to lead the quality in DevOps.
The Fourth Constraint in Project Delivery—LeadershipTechWell
All too often, the triple constraints—time, cost, and quality—are bandied about as if they are the be-all, end-all. While they are important, leadership—the fourth and larger underpinning constraint—influences the first three. Statistics on project success and failure abound, and these measurements are usually taken against the triple constraints. According to the Project Management Institute, only 53 percent of projects are completed within budget, and only 49 percent are completed on time. If so many projects overrun budget and are late, we can’t really say, “Good, fast, or cheap—pick two.” Rob Burkett talks about leadership at every level of a team. He shares his insights and stories gleaned from his years of IT and project management experience. Rob speaks to some of the glaring difficulties in the workplace in general and some specifically related to IT delivery and project management. Leave with a clearer understanding of how to communicate with teams and team members, and gain a better understanding of how you can be a leader—up and down your organization.
Resolve the Contradiction of Specialists within Agile TeamsTechWell
As teams grow, organizations often draw a distinction between feature teams, which deliver the visible business value to the user, and component teams, which manage shared work. Steve Berczuk says that this distinction can help organizations be more productive and scale effectively, but he recognizes that not all shared work fits into this model. Some work is best handled by “specialists,” that is people with unique skills. Although teams composed entirely of T-shaped people is ideal, certain skills are hard to come by and are used irregularly across an organization. Since these specialists often need to work closely with teams, rather than working from their own backlog, they don’t fit into the component team model. The use of shared resources presents challenges to the agile planning model. Steve Berczuk shares how teams such as those providing infrastructure services and specialists can fit into a feature+component team model, and how variations such as embedding specialists in a scrum team can both present process challenges and add significant value to both the team and the larger organization.
Pin the Tail on the Metric: A Field-Tested Agile GameTechWell
Metrics don’t have to be a necessary evil. If done right, metrics can help guide us to make better forward-looking decisions, rather than being used for simply managing or monitoring. They can help us identify trade-offs between options for what to do next versus punitive or worse, purely managerial measures. Steve Martin won’t be giving the Top Ten List of field-tested metrics you should use. Instead, in this interactive mini-workshop, he leads you through the critical thinking necessary for you to determine what is right for you to measure. First, Steve explores why you want to measure something—whether it’s for a team, a portfolio, or even an agile transformation. Next, he provides multiple real-life metrics examples to help drive home concepts behind characteristics of good and bad metrics. Finally, Steve shows how to run his field-tested agile game—Pin the Tail on the Metric. Take back this activity to help you guide metrics conversations at your organization.
Agile Performance Holarchy (APH)—A Model for Scaling Agile TeamsTechWell
A hierarchy is an organizational network that has a top and a bottom, and where position is determined by rank, importance, and value. A holarchy is a network that has no top or bottom and where each person’s value derives from his ability, rather than position. As more companies seek the benefits of agile, leaders need to build and sustain delivery capability while scaling agile without introducing unnecessary process and overhead. The Agile Performance Holarchy (APH) is an empirical model for scaling and sustaining agility while continuing to deliver great products. Jeff Dalton designed the APH by drawing from lessons learned observing and assessing hundreds of agile companies and teams. The APH helps implement a holarchy—a system composed of interacting organizational units called holons—centered on a series of performance circles that embody the behaviors of high performing agile organizations. Jeff describes how APH provides guidelines in the areas of leadership, values, teaming, visioning, governing, building, supporting, and engaging within an all-agile organization. Join Jeff to see what the APH is all about and how you can use it in your team and organization.
A Business-First Approach to DevOps ImplementationTechWell
DevOps is a cultural shift aimed at streamlining intergroup communication and improving operational efficiency for development and operations groups. Over time, inclusion of other IT groups under the DevOps umbrella has become the norm for many organizations. But even broadening the boundaries of DevOps, the conversation has been largely devoid of the business units’ place at the table. A common mistake organizations make while going through the DevOps transformation is drawing a line at the IT boundary. If that occurs, a larger, more inclusive silo within the organization is created, operating in an informational vacuum and causing operational inefficiency and goal misalignment. Sharing his experiences working on both sides of the fence, Leon Fayer describes the importance of including business units in order to align technology decisions with business goals. Leon discusses inclusion of business units in existing agile processes, benefits of cross-departmental monitoring, and a business-first approach to technology decisions.
Databases in a Continuous Integration/Delivery ProcessTechWell
The document summarizes a presentation about including databases in a continuous integration/delivery process. It discusses treating database code like application code by placing it under version control and integrating databases into the DevOps software development pipeline. This allows databases to be built, tested, and released like other software through continuous integration, delivery, and deployment.
Mobile Testing: What—and What Not—to AutomateTechWell
Organizations are moving rapidly into mobile technology, which has significantly increased the demand for testing of mobile applications. David Dangs says testers naturally are turning to automation to help ease the workload, increase potential test coverage, and improve testing efficiency. But should you try to automate all things mobile? Unfortunately, the answer is not always clear. Mobile has its own set of complications, compounded by a wide variety of devices and OS platforms. Join David to learn what mobile testing activities are ripe for automation—and those items best left to manual efforts. He describes the various considerations for automating each type of mobile application: mobile web, native app, and hybrid applications. David also covers device-level testing, types of testing, available automation tools, and recommendations for automation effectiveness. Finally, based on his years of mobile testing experience, David provides some tips and tricks to approach mobile automation. Leave with a clear plan for automating your mobile applications.
Cultural Intelligence: A Key Skill for SuccessTechWell
Diversity is becoming the norm in everyday life. However, introducing global delivery models without a proper understanding of intercultural differences can lead to difficulty, frustration, and reduced productivity. Priyanka Sharma and Thena Barry say that in our diverse world, we need teams with people who can cross these boundaries, communicate effectively, and build the diverse networks necessary to avoid problems. We need to learn about cultural intelligence (CI) and cultural quotient (CQ). CI is the ability to relate and work effectively across cultures. CQ is the cognitive, motivational, and behavioral capacity to understand and respond to beliefs, values, attitudes, and behaviors of individuals and groups. Together, CI and CQ can help us build behavioral capacities that aid motivation, behavior, and productivity in teams as well as individuals. Priyanka and Thena show how to build a more culturally intelligent place with tools and techniques from Leading with Cultural Intelligence, as well as content from the Hofstede cultural model. In addition, they illustrate the model with real-life experiences and demonstrate how they adapted in similar circumstances.
Turn the Lights On: A Power Utility Company's Agile TransformationTechWell
Why would a century-old utility with no direct competitors take on the challenge of transforming its entire IT application organization to an agile methodology? In an increasingly interconnected world, the expectations of customers continue to evolve. From smart meters to smart phones, IoT is creating a crisis point for industries not accustomed to rapid change. Glen Morris explains that pizzas can be tracked by the minute and packages at every stop, and customers now expect this same customer service model should exist for all industries—including power. Glen examines how to create momentum and transform non-IT-focused industries to an agile model. If you are struggling with gaining traction in your pursuit of agile within your business, Glen gives you concrete, practical experiences to leverage in your pursuit. Finally, he communicates how to gain buy-in from business partners who have no idea or concern about agile or its methodologies. If your business partners look at you with amusement when you mention the need for a dedicated Product Owner, join Glen as he walks you through the approaches to overcoming agile skepticism.
For the full video of this presentation, please visit: https://www.edge-ai-vision.com/2024/06/how-axelera-ai-uses-digital-compute-in-memory-to-deliver-fast-and-energy-efficient-computer-vision-a-presentation-from-axelera-ai/
Bram Verhoef, Head of Machine Learning at Axelera AI, presents the “How Axelera AI Uses Digital Compute-in-memory to Deliver Fast and Energy-efficient Computer Vision” tutorial at the May 2024 Embedded Vision Summit.
As artificial intelligence inference transitions from cloud environments to edge locations, computer vision applications achieve heightened responsiveness, reliability and privacy. This migration, however, introduces the challenge of operating within the stringent confines of resource constraints typical at the edge, including small form factors, low energy budgets and diminished memory and computational capacities. Axelera AI addresses these challenges through an innovative approach of performing digital computations within memory itself. This technique facilitates the realization of high-performance, energy-efficient and cost-effective computer vision capabilities at the thin and thick edge, extending the frontier of what is achievable with current technologies.
In this presentation, Verhoef unveils his company’s pioneering chip technology and demonstrates its capacity to deliver exceptional frames-per-second performance across a range of standard computer vision networks typical of applications in security, surveillance and the industrial sector. This shows that advanced computer vision can be accessible and efficient, even at the very edge of our technological ecosystem.
Your One-Stop Shop for Python Success: Top 10 US Python Development Providersakankshawande
Simplify your search for a reliable Python development partner! This list presents the top 10 trusted US providers offering comprehensive Python development services, ensuring your project's success from conception to completion.
[OReilly Superstream] Occupy the Space: A grassroots guide to engineering (an...Jason Yip
The typical problem in product engineering is not bad strategy, so much as “no strategy”. This leads to confusion, lack of motivation, and incoherent action. The next time you look for a strategy and find an empty space, instead of waiting for it to be filled, I will show you how to fill it in yourself. If you’re wrong, it forces a correction. If you’re right, it helps create focus. I’ll share how I’ve approached this in the past, both what works and lessons for what didn’t work so well.
"Choosing proper type of scaling", Olena SyrotaFwdays
Imagine an IoT processing system that is already quite mature and production-ready and for which client coverage is growing and scaling and performance aspects are life and death questions. The system has Redis, MongoDB, and stream processing based on ksqldb. In this talk, firstly, we will analyze scaling approaches and then select the proper ones for our system.
AppSec PNW: Android and iOS Application Security with MobSFAjin Abraham
Mobile Security Framework - MobSF is a free and open source automated mobile application security testing environment designed to help security engineers, researchers, developers, and penetration testers to identify security vulnerabilities, malicious behaviours and privacy concerns in mobile applications using static and dynamic analysis. It supports all the popular mobile application binaries and source code formats built for Android and iOS devices. In addition to automated security assessment, it also offers an interactive testing environment to build and execute scenario based test/fuzz cases against the application.
This talk covers:
Using MobSF for static analysis of mobile applications.
Interactive dynamic security assessment of Android and iOS applications.
Solving Mobile app CTF challenges.
Reverse engineering and runtime analysis of Mobile malware.
How to shift left and integrate MobSF/mobsfscan SAST and DAST in your build pipeline.
zkStudyClub - LatticeFold: A Lattice-based Folding Scheme and its Application...Alex Pruden
Folding is a recent technique for building efficient recursive SNARKs. Several elegant folding protocols have been proposed, such as Nova, Supernova, Hypernova, Protostar, and others. However, all of them rely on an additively homomorphic commitment scheme based on discrete log, and are therefore not post-quantum secure. In this work we present LatticeFold, the first lattice-based folding protocol based on the Module SIS problem. This folding protocol naturally leads to an efficient recursive lattice-based SNARK and an efficient PCD scheme. LatticeFold supports folding low-degree relations, such as R1CS, as well as high-degree relations, such as CCS. The key challenge is to construct a secure folding protocol that works with the Ajtai commitment scheme. The difficulty, is ensuring that extracted witnesses are low norm through many rounds of folding. We present a novel technique using the sumcheck protocol to ensure that extracted witnesses are always low norm no matter how many rounds of folding are used. Our evaluation of the final proof system suggests that it is as performant as Hypernova, while providing post-quantum security.
Paper Link: https://eprint.iacr.org/2024/257
Essentials of Automations: Exploring Attributes & Automation ParametersSafe Software
Building automations in FME Flow can save time, money, and help businesses scale by eliminating data silos and providing data to stakeholders in real-time. One essential component to orchestrating complex automations is the use of attributes & automation parameters (both formerly known as “keys”). In fact, it’s unlikely you’ll ever build an Automation without using these components, but what exactly are they?
Attributes & automation parameters enable the automation author to pass data values from one automation component to the next. During this webinar, our FME Flow Specialists will cover leveraging the three types of these output attributes & parameters in FME Flow: Event, Custom, and Automation. As a bonus, they’ll also be making use of the Split-Merge Block functionality.
You’ll leave this webinar with a better understanding of how to maximize the potential of automations by making use of attributes & automation parameters, with the ultimate goal of setting your enterprise integration workflows up on autopilot.
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
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!
Taking AI to the Next Level in Manufacturing.pdfssuserfac0301
Read Taking AI to the Next Level in Manufacturing to gain insights on AI adoption in the manufacturing industry, such as:
1. How quickly AI is being implemented in manufacturing.
2. Which barriers stand in the way of AI adoption.
3. How data quality and governance form the backbone of AI.
4. Organizational processes and structures that may inhibit effective AI adoption.
6. Ideas and approaches to help build your organization's AI strategy.
Conversational agents, or chatbots, are increasingly used to access all sorts of services using natural language. While open-domain chatbots - like ChatGPT - can converse on any topic, task-oriented chatbots - the focus of this paper - are designed for specific tasks, like booking a flight, obtaining customer support, or setting an appointment. Like any other software, task-oriented chatbots need to be properly tested, usually by defining and executing test scenarios (i.e., sequences of user-chatbot interactions). However, there is currently a lack of methods to quantify the completeness and strength of such test scenarios, which can lead to low-quality tests, and hence to buggy chatbots.
To fill this gap, we propose adapting mutation testing (MuT) for task-oriented chatbots. To this end, we introduce a set of mutation operators that emulate faults in chatbot designs, an architecture that enables MuT on chatbots built using heterogeneous technologies, and a practical realisation as an Eclipse plugin. Moreover, we evaluate the applicability, effectiveness and efficiency of our approach on open-source chatbots, with promising results.
What is an RPA CoE? Session 1 – CoE VisionDianaGray10
In the first session, we will review the organization's vision and how this has an impact on the COE Structure.
Topics covered:
• The role of a steering committee
• How do the organization’s priorities determine CoE Structure?
Speaker:
Chris Bolin, Senior Intelligent Automation Architect Anika Systems
The Microsoft 365 Migration Tutorial For Beginner.pptxoperationspcvita
This presentation will help you understand the power of Microsoft 365. However, we have mentioned every productivity app included in Office 365. Additionally, we have suggested the migration situation related to Office 365 and how we can help you.
You can also read: https://www.systoolsgroup.com/updates/office-365-tenant-to-tenant-migration-step-by-step-complete-guide/
Energy Efficient Video Encoding for Cloud and Edge Computing Instances
Scrum: An Experiential Workshop
1.
MJ
Half‐day Tutorial
6/3/2013 8:30 AM
"Scrum: An Experiential Workshop"
Presented by:
Mitch Lacey
Mitch Lacey & Associates, Inc.
Brought to you by:
340 Corporate Way, Suite 300, Orange Park, FL 32073
888‐268‐8770 ∙ 904‐278‐0524 ∙ sqeinfo@sqe.com ∙ www.sqe.com
2. Mitch Lacey
Mitch Lacey & Associates, Inc.
Over the past fifteen years, Mitch Lacey has managed numerous plan-driven and agile
projects. At Microsoft, Mitch honed his agile skills, successfully releasing core enterprise
services for Windows Live, and transitioned from program manager to Agile Coach, helping
others transition to agile practices. At Ascentium Corporation he became the Agile Practice
Manager, coaching customers on agile practices and adoption worldwide. As a Certified Scrum
Trainer and a registered Project Management Professional, Mitch shares his experience in
project and client management through Certified ScrumMaster courses, agile coaching
engagements, conference presentations, and his writings, including his new book The Scrum
Field Guide: Practical Advice for Your First Year.
3. SQE Agile West 2013 Reference Material
Understanding Scrum: An Experiential
Workshop
Reference Material
Mitch Lacey
SQE Agile West 2013
Las Vegas
PLEASE NOTE
These slides are for REFERENCE ONLY!
We will not be using/covering the slides.
SQE Agile West 2013 Reference Material
Copyright 2007‐2013 Mitch Lacey (mitch@mitchlacey.com). No reproduction without written
authorization.
1
4. SQE Agile West 2013 Reference Material
About Mitch Lacey
•
•
•
•
•
•
•
Author: The Scrum Field Guide
15+ years of project management experience
Agile 2012 Conference Chair, Dallas Texas
Former Agile Alliance Board Member
Former Scrum Alliance Board Member
Project Management Professional (PMP)
Certified Scrum Trainer (CST)
SQE Agile West 2013 Reference Material
Mitch Lacey Contact Info
•
•
•
•
Twitter: mglacey
Linked In: http://www.linkedin.com/in/mitchlacey
Email: mitch@mitchlacey.com
Phone: +1 206 228 3544
vcard
LinkedIn
SQE Agile West 2013 Reference Material
Copyright 2007‐2013 Mitch Lacey (mitch@mitchlacey.com). No reproduction without written
authorization.
2
7. SQE Agile West 2013 Reference Material
The Product Owner
Customer
Facing
Owns the
Budget
Owns the
ROI
Manages
Feature
Risk
Provides
Direction
SQE Agile West 2013 Reference Material
The Product Owner
Goal: Business & Customer Advocacy and
Product (or service) Guidance
Responsibilities
Optimizes the business value of the work
Represents and Manages Stakeholder interests
Owns the Product Backlog (requirements list)
Establishes, nurtures and communicates the
product vision
– Monitors the project against its ROI goals and
investment vision
– Makes decisions about when to create an
official release
–
–
–
–
SQE Agile West 2013 Reference Material
Copyright 2007‐2013 Mitch Lacey (mitch@mitchlacey.com). No reproduction without written
authorization.
5
9. SQE Agile West 2013 Reference Material
Roles in Scrum: The Team – What they Do
• Plan the work / own and update the estimates
• Place value on following a plan but value
responding to change more (values)
• Rely on the Product Owner for product
clarification questions (feature risk)
• Authority and empowerment (does what’s
needed to achieve the goal)
• Rely on the ScrumMaster to help clear
blocking issues (social risk)
• Commit to the Sprint
SQE Agile West 2013 Reference Material
Roles in Scrum: The Team – How Big?
• Six is ideal
– As little as three and as big as eight
• Co-located
• Scrum scales by adding teams, not growing
team size
SQE Agile West 2013 Reference Material
Copyright 2007‐2013 Mitch Lacey (mitch@mitchlacey.com). No reproduction without written
authorization.
7
10. SQE Agile West 2013 Reference Material
Team Consultant Model
SQE Agile West 2013 Reference Material
Roles in Scrum: The Team - Agreement and
Support
•
•
•
•
Teams are cross functional
Team members need to support each other
ScrumMaster drives the team to consensus
Fist of Five Technique:
–
–
–
–
–
5 = 100% support
4 = Good idea, wish it was mine
3 = I can live with and support this
2 = I would like to think about this more
1 = I am against this and will fight moving in this
direction
SQE Agile West 2013 Reference Material
Copyright 2007‐2013 Mitch Lacey (mitch@mitchlacey.com). No reproduction without written
authorization.
8
12. SQE Agile West 2013 Reference Material
The Product
Backlog
SQE Agile West 2013 Reference Material
Levels of Planning: Being “Done” Example
Examples:
1. Architectural
Diagrams Updated
2. Automated User
Tests Passing
Examples:
1. Stress Testing
2. User Training
Completed
Examples:
1. Failover Testing
2. Release Readiness
Review
Examples:
1. SQL Optimization
and Tuning
2. Data Security
Roles Updated
Prod
Examples:
1. Installation
Package Updated
2. > 70% Code
Coverage
Sprint
Story
Task
SQE Agile West 2013 Reference Material
Copyright 2007‐2013 Mitch Lacey (mitch@mitchlacey.com). No reproduction without written
authorization.
10
13. SQE Agile West 2013 Reference Material
SQE Agile West 2013 Reference Material
Definition of Done Exercise
Build your own definition of done!
1 – in the book
2 – on this webpage:
http://www.mitchlacey.com/introto-agile/scrum/definition-of-done
SQE Agile West 2013 Reference Material
Copyright 2007‐2013 Mitch Lacey (mitch@mitchlacey.com). No reproduction without written
authorization.
11
14. SQE Agile West 2013 Reference Material
Product Backlog: What is it?
• Ordered, prioritized list of features and work
• High level estimates (story points)
– Preferred: Story points: 1,2,3,5,8,13
– Alternatives
• Exponential: 10, 20, 40, 80
• T-shirt sizing: XS, S, M ,L, XL
• Items added at any time
• Owned and prioritized by the Product Owner
• Should reflect the vision (why the project exists and its
desire end state)
SQE Agile West 2013 Reference Material
Product Backlog Prioritization
Highest Priority
Work on it now – lots of detail
1
2
Up Next – more detail
Work that is 3‐5 sprints out – Some detail
Too far out – little detail
3
4
SQE Agile West 2013 Reference Material
Copyright 2007‐2013 Mitch Lacey (mitch@mitchlacey.com). No reproduction without written
authorization.
12
15. SQE Agile West 2013 Reference Material
User Stories
• As a <user> I can/want <action> so that <result>
• As an administrator, I can look up this month’s patient
report and am able to see who is over the user defined
threshold
• Have business value
• Are easily identifiable by the Product Owner, customers
and the team
• Rely on the 3 C’s
– Card
– Conversation
– Confirmation
SQE Agile West 2013 Reference Material
INVEST in Your Product Backlog
• Independent
– Dependencies lead to problems estimating and prioritizing
– Can ideally select one item to work on without pulling in 18 others
• Negotiable
– Product backlog items are not contracts
– Leave or imply some flexibility
• Valuable
– To users or customers, usually not to developers
– Try rewriting developer-oriented backlog items to reflect value to users or
customers
• Estimable
– Because plans are based on user stories, we need to be able to estimate
them
• Small
– Complex backlog items are intrinsically large
– Compound backlog items are multiple items in one
• Testable
– Make backlog items testable by having acceptance tests
1 Bill Wake 2003
SQE Agile West 2013 Reference Material
Copyright 2007‐2013 Mitch Lacey (mitch@mitchlacey.com). No reproduction without written
authorization.
13
16. SQE Agile West 2013 Reference Material
Make it DEEP
• Detailed Appropriately.
– Stories coming up should be understood
– Stories that will not be developed for awhile should be described
with less detail
• Estimated.
– More precise at the top
– Less at the bottom
• Emergent.
– Stories grow and change. The more you learn, the more you
tweak
• Prioritized.
– Valuable stories at the top, less so down the list
SQE Agile West 2013 Reference Material
Product Backlog Grooming
• The team should spend 5%-15% of Sprint time (1-6h)
in reviewing the Product Backlog and estimating it for
each Sprint (s)
• Similar to a specification only never out of date
• Continuously prioritized and updated
• Anyone can add to the product backlog
SQE Agile West 2013 Reference Material
Copyright 2007‐2013 Mitch Lacey (mitch@mitchlacey.com). No reproduction without written
authorization.
14
18. SQE Agile West 2013 Reference Material
Levels of Planning: Being “Done”
• What is Done?
– How do you know when your project is done?
– How do your customers and stakeholders know?
– How do you communicate it?
SQE Agile West 2013 Reference Material
Levels of Planning: Sprint Planning Meeting 1
Vision
Product(s)
Releases
Sprint
Day
• Scale duration depending on
Sprint Duration
– 1mo Sprint = 4h
– 2w Sprint = 2h
• Defines what the team will build
• Product Owner states what the
business wants (high value, high
risk)
• Agrees on the goal of the sprint
• When Team has enough
information, or time has ended,
Planning Meeting 2 begins
SQE Agile West 2013 Reference Material
Copyright 2007‐2013 Mitch Lacey (mitch@mitchlacey.com). No reproduction without written
authorization.
16
19. SQE Agile West 2013 Reference Material
Levels of Planning: Sprint Planning Meeting 2
Vision
• Scale duration depending on
Sprint Duration
– 1mo Sprint = 4h
– 2w Sprint = 2h
Product(s)
Releases
Sprint
Day
• Defines how the team will build
the stories
• Tasks are small (2-14h)
• Team owns Sprint Backlog
(builds, estimates, updates)
• Team signs up for work,
collectively commits to the work
• Attended by the Team (Product
Owner optional)
SQE Agile West 2013 Reference Material
Sample Sprint Backlog
SQE Agile West 2013 Reference Material
Copyright 2007‐2013 Mitch Lacey (mitch@mitchlacey.com). No reproduction without written
authorization.
17
20. SQE Agile West 2013 Reference Material
The Sprint Backlog
• Is the output of the planning meeting
• Is used for the team to manage themselves and their
work during the sprint
• Creates transparency between all Scrum team members
SQE Agile West 2013 Reference Material
Download my Sprint Excel Sheet
http://www.mitchlacey.com/resources/sprint‐excel‐templates
SQE Agile West 2013 Reference Material
Copyright 2007‐2013 Mitch Lacey (mitch@mitchlacey.com). No reproduction without written
authorization.
18
21. SQE Agile West 2013 Reference Material
Levels of Planning: Daily Scrum Meeting
• Occurs Daily
• Team members answer three questions:
•
•
•
•
What did you work on since the last meeting?
What will you work on today?
What impediments / blocking issues do you have?
(optional) What is your confidence that we will achieve the sprint goal?
• Timeboxed to 15m
• Same time/place daily
• No deep dive problem solving
(deal with that after)
SQE Agile West 2013 Reference Material
The Sprint: Reporting Progress - Burndown
SQE Agile West 2013 Reference Material
Copyright 2007‐2013 Mitch Lacey (mitch@mitchlacey.com). No reproduction without written
authorization.
19
22. SQE Agile West 2013 Reference Material
The Sprint: Reporting Progress - Burndown
SQE Agile West 2013 Reference Material
Release Burndowns
• Use the same sprint burndown but instead of days, use it
for sprints
• Should be updated after every sprint
• Useful to allow the Product Owner to see the overall
release plan progress
SQE Agile West 2013 Reference Material
Copyright 2007‐2013 Mitch Lacey (mitch@mitchlacey.com). No reproduction without written
authorization.
20
23. SQE Agile West 2013 Reference Material
Sprint Review Meeting
• Occurs on the last day of the Sprint
• Allows stakeholders to review the work done and provide
guidance on what to do next
• One hour per week of sprint (e.g. two week sprint is two
hour meeting)
• The team drives the meeting
• Everyone attends
• Can impact the upcoming Sprint planning sessions
– Reprioritize the backlog
– Change high level estimates of work
– Team composition may change
SQE Agile West 2013 Reference Material
What do we Review in the Review Meeting?
•
•
•
•
•
•
•
•
Review the Sprint Goal
Review the commitments made by the team
Review work accomplished
Review the work that was not accomplished
Review the decision made
Demo the work
Summarize
Asks
SQE Agile West 2013 Reference Material
Copyright 2007‐2013 Mitch Lacey (mitch@mitchlacey.com). No reproduction without written
authorization.
21
24. SQE Agile West 2013 Reference Material
Retrospective
• Occurs on the last day of the Sprint
• One hour per week of sprint (e.g. two week sprint is two
hour meeting)
• Allows the team to inspect itself to learn about & change
behavior as needed
• Facilitated by ScrumMaster
• ScrumMaster and the Team prioritize the improvements
• The sprint ends when the timebox expires,
typically after the retrospective
SQE Agile West 2013 Reference Material
Getting Started with Scrum
•
•
•
•
•
•
•
•
•
•
•
Get a senior Sponsor in the company
Get a champion to drive the effort
Agree on who will play the roles
Set a date to “start scrumming” and prep the team to that
date
Build a prioritized Product Backlog and estimate it
Build the team and clear blocking issues (like not being colocated)
Build a Sprint Backlog and start working
Use Burndowns
Conduct a demo and review
Inspect and Adapt
Repeat!
SQE Agile West 2013 Reference Material
Copyright 2007‐2013 Mitch Lacey (mitch@mitchlacey.com). No reproduction without written
authorization.
22
25. SQE Agile West 2013 Reference Material
Cadence
•
•
•
•
•
•
Set a cadence and keep it
Put all meetings in calendars on day 1
Keep your daily Scrum on track
Use planning
Work to potentially shippable code
Always demo at the end
• CELEBRATE SUCCESS AT EVERY SPRINT!
SQE Agile West 2013 Reference Material
Getting People on Board with Scrum
Be patient
Use the local network – get testimonials
Provide articles and books
Show incremental benefits
Get external speakers to talk to
management and teams
• Ensure risk will not be penalized
•
•
•
•
•
SQE Agile West 2013 Reference Material
Copyright 2007‐2013 Mitch Lacey (mitch@mitchlacey.com). No reproduction without written
authorization.
23
26. SQE Agile West 2013 Reference Material
Be Warned
•
•
•
•
•
Most projects deliver every 6-18 months.
Scrum reduces this through inspect and adapt
Things will be stressful
Fight the urge to be lazy
Stay disciplined
SQE Agile West 2013 Reference Material
What Causes Scrum to Fail?
• Making changes out of the gate
• Thinking that “this can’t work in our company”
• Not having an honest retrospective and doing
something about it
• Bad ScrumMasters
• Falling into old habits
• Lacking authority and being empowered
• Business culture does not support Scrum
SQE Agile West 2013 Reference Material
Copyright 2007‐2013 Mitch Lacey (mitch@mitchlacey.com). No reproduction without written
authorization.
24
27. SQE Agile West 2013 Reference Material
Scrum Resources
• My contact
– http://www.mitchlacey.com
– http://twitter.com/mglacey
• My book, The Scrum Field Guide
• Jeff Sutherland Scrum Papers
– The Scrum Papers (jeffsutherland.com/scrum/ScrumPapers.pdf)
• Mike Cohn & Mountain Goat Software
– http://www.mountaingoatsoftware.com/scrum
• Scrum Alliance
– http://www.scrumalliance.org
SQE Agile West 2013 Reference Material
Offshoring – Making it Work
• About 3 time zones away seems to work
• Phone/shared desktop pair-programming is essential
– Set management expectations that pairs will be based on work, not
proximity
• Use technology!
–
–
–
–
Push to talk cell phones so every team member can talk anywhere any time
Use teleconferencing for all “formal” meetings like standups
Use VNC
Get webcams
• Face time matters, travel often.
• Travel any time there are communication difficulties
• Travel any time you feel trust is breaking down between the
locations
• Do absolutely anything you can do to build a one-team culture
• Do absolutely nothing to build the perception fragmented teams
SQE Agile West 2013 Reference Material
Copyright 2007‐2013 Mitch Lacey (mitch@mitchlacey.com). No reproduction without written
authorization.
25
28. SQE Agile West 2013 Reference Material
Offshoring – Making it Work Part 2
• Have a project / team coordinator
– The coordinator has the responsibility of relaying the backlog to
the offshore team and tracking progress.
• Have in-person kick-off meetings with the entire
worldwide team
• Bring offshore people to the central office on a rotational
basis to build team cohesion
• Have offshore teams take on as much independent work
as possible, a whole feature set possibly
SQE Agile West 2013 Reference Material
Offshoring – Impediments to Manage
Time zone differences
Culture and values
Inexperienced teams
Face-to-face communication
Language barriers
Trust
Building a common development environment and
codebase
• Stronger Command & Control tradition in Asia
• Offshore turn-over
• Recruiting the right offshore workers
•
•
•
•
•
•
•
SQE Agile West 2013 Reference Material
Copyright 2007‐2013 Mitch Lacey (mitch@mitchlacey.com). No reproduction without written
authorization.
26
29. SQE Agile West 2013 Reference Material
When to Offshore
• Don’t Offshore:
– First releases of complex and high-technology-risk projects
– If your onshore development process is not in place (”CMMI
level 3”)
• Process = the daily work in the teams
• Process ≠ the corporate process guidelines
• Don’t Agile Offshore:
– If you don’t have any onshore Agile experiences
SQE Agile West 2013 Reference Material
Copyright 2007‐2013 Mitch Lacey (mitch@mitchlacey.com). No reproduction without written
authorization.
27