The transition from waterfall-based software development to an agile, iterative model carries with it well-known challenges and problems-entrenched cultures, skill gaps, and organizational change management. For a large, globally distributed software development organization, an entirely different set of practical challenges comes with scaling agile practices. Last year the Dell Enterprise Solutions Group applied agile practices to more than forty projects ranging from a collocated single team project to projects that consisted of fifteen Scrum teams located across the US and India. Geoff Meyer and Brian Plunkett explain how Dell mined these real-life projects for their empirical value and adapted their agile practices into a flexible planning model that addresses the project complexities of staffing, scale, interdependency, and waterfall intersection. Join Geoff and Brian to see how they tackled the tough, real-life problems scaling agile at Dell: functional-based organizational boundaries, globally distributed teams, contractor challenges, multi-team projects, and dependencies on teams that continued to develop using waterfall methods.
This guide summaries a successful Agile transformation in Telco with a related case study.
Do not take the described steps of this guide as the only way to be successful, there can be many other alternatives for sure. However, this guide explains a way thats experienced to be successful in many companies and under different circumstances.
Looking forward to hear your comments & suggestions
Thanks
Easily define & implement your Digital Transformation Strategy & Plan by leveraging this 10-step Template. Created by ex-McKinsey, Deloitte and BCG Consultants specialized in Digital Strategy, after more than 600 hours of work. Don’t reinvent the wheel. Download Now. To download the whole template, go to www.slidebooks.com.
Many organisations that we encounter in New Zealand are keen on what Agile promises. Why then are they not realising the promises sought at the scale necessary to make a substantial difference for an overall customer offering or line of business? Why are many organisations on their 2nd, 3rd or 4th attempt at “Agile Transformation”? Why are so many Scrum Masters and Agile Coaches still frustrated by many of the same ongoing frictions experienced before the pandemic with even less ability to address them?
Many years of experiences across the Tasman and consultation with change agents around the world reveal clear answers. There is a set of relatively straightforward choices that make the difference between whether an organisation struggles for years with the problems above or finds the path of sustainable, world class agility at scale. For a commercial organisation, this means competitive advantage. For a public sector organisation, this means stakeholder trust and delightful experiences. For employees it means less friction and more engagement.
During this session we will share insights around the following questions with reference to experience reports.
Why do many scaled Agile adoptions stall out after the first 1-2 years rather than improve continuously?
Why does the most popular way to scale incur high coordination overheads and fall short of high agility?
Is there a way to eliminate dependencies and have knowledge and skills be the constraint on agility, rather than structure and process?
Why does setting up Scrum Teams for each component of a product make it unlikely that everyone is working on the right things?
Why does delegating responsibility for Agile transformation outcomes to internal Agile Coaches or external management consultants result in “change theatre”?
What are the key leadership questions that can unlock up to 95% of your organisation’s performance?
What changes are necessary for your scaled Agile adoption to be sustained beyond the tenure of the leader who introduced it?
What is an alternative scaling model and adoption approach addressing all of the above issues that New Zealand is yet to benefit from?
See more clearly what’s limiting the effectiveness and longevity of your scaled Agile adoption. Discover options never experienced before in New Zealand.
This guide summaries a successful Agile transformation in Telco with a related case study.
Do not take the described steps of this guide as the only way to be successful, there can be many other alternatives for sure. However, this guide explains a way thats experienced to be successful in many companies and under different circumstances.
Looking forward to hear your comments & suggestions
Thanks
Easily define & implement your Digital Transformation Strategy & Plan by leveraging this 10-step Template. Created by ex-McKinsey, Deloitte and BCG Consultants specialized in Digital Strategy, after more than 600 hours of work. Don’t reinvent the wheel. Download Now. To download the whole template, go to www.slidebooks.com.
Many organisations that we encounter in New Zealand are keen on what Agile promises. Why then are they not realising the promises sought at the scale necessary to make a substantial difference for an overall customer offering or line of business? Why are many organisations on their 2nd, 3rd or 4th attempt at “Agile Transformation”? Why are so many Scrum Masters and Agile Coaches still frustrated by many of the same ongoing frictions experienced before the pandemic with even less ability to address them?
Many years of experiences across the Tasman and consultation with change agents around the world reveal clear answers. There is a set of relatively straightforward choices that make the difference between whether an organisation struggles for years with the problems above or finds the path of sustainable, world class agility at scale. For a commercial organisation, this means competitive advantage. For a public sector organisation, this means stakeholder trust and delightful experiences. For employees it means less friction and more engagement.
During this session we will share insights around the following questions with reference to experience reports.
Why do many scaled Agile adoptions stall out after the first 1-2 years rather than improve continuously?
Why does the most popular way to scale incur high coordination overheads and fall short of high agility?
Is there a way to eliminate dependencies and have knowledge and skills be the constraint on agility, rather than structure and process?
Why does setting up Scrum Teams for each component of a product make it unlikely that everyone is working on the right things?
Why does delegating responsibility for Agile transformation outcomes to internal Agile Coaches or external management consultants result in “change theatre”?
What are the key leadership questions that can unlock up to 95% of your organisation’s performance?
What changes are necessary for your scaled Agile adoption to be sustained beyond the tenure of the leader who introduced it?
What is an alternative scaling model and adoption approach addressing all of the above issues that New Zealand is yet to benefit from?
See more clearly what’s limiting the effectiveness and longevity of your scaled Agile adoption. Discover options never experienced before in New Zealand.
These case studies can help readers to practices many simulated scenarios. These are case studies will be asked in Transformation related interviews.
All these case studies are from my 4 books, The Agilis's Guidebook, The Scrum Master Guidebook, Personal Leadership & Self-Coaching Guidebook, and A Guidebook of Coaching High-Performance team.
Grab the first 150 pages of all these books from here
1. https://www.slideshare.net/patarychandan/the-agilists-guidebook-first-150-pages
2. https://www.slideshare.net/patarychandan/the-scrum-master-guidebook-150-pages
3. https://www.slideshare.net/patarychandan/we-can-lead-a-guidebook-of-personal-leadership-and-selfcoaching
4. https://www.slideshare.net/patarychandan/a-guidebook-of-coaching-high-performance-team-200-pages
PLEASE DOWNLOAD FROM HERE:https://drive.google.com/file/d/1vHAmAU4x-hH7X1SaZwIpudeIbR6kfvmB/view?usp=sharing
The case study optimizes the HP DeskJet printer supply chain by redesigning the network using component commonality and risk pooling. The redesign leads to considerable savings to the business.
Haier: Taking a chinese company global in 2011Ilaria Fiore
Corporate strategy for HAIER business case. This presentation is based exclusively on informations and data provided in Harvard Business School's case study "Haier: Taking a chinese company global in 2011" and Wikipedia.
The presentation provides information about Haier, evaluates the situation, problems and opportunities of the company; then it describes the possible options avaiable to Haier and selects the best, according to the group's ideas.
Design, Build and Run an Effective IT (Service) Strategy to Business NeedsFlevy.com Best Practices
This Slideshare presentation is a partial preview of the full business document. To view and download the full document, please go here:
http://flevy.com/browse/business-document/design-build-and-run-an-effective-it-service-strategy-to-business-needs-279
The "Deliver Business Value with IT" series provides a good overview and actionable material of the ways a CIO can provide valuable and effective support to your company strategy and leverages business model concepts to deliver business value from IT. Martin Palmgren propose an extremely solid piece of work that comes across as the A-Z reference of how to execute and implement IT strategy from a CEO and CIO level perspective."
Executive Summary:
The CIO and the IT Department need to position as premium provider of IT services and focus on value to cost.
In order to avoid the "do we really need a CIO and IT department to bother us with technology when we can use the cloud?" the CIO has to ensure that the business strategy and business objectives are supported by IT (from a Business and IT architecture perspective). Where the IT Strategy support Strategy execution, "Time to Market", Cost Effectiveness and stakeholder expectations from an Executive, Business Unit, IT Management and IT Risk Management perspective.
Leading a large-scale agile transformation isn’t about adopting a new set of attitudes, processes, and behaviors at the team level… it’s about helping your company deliver faster to market, and developing the ability to respond to a rapidly-changing competitive landscape. First and foremost, it’s about achieving business agility. Business agility comes from people having clarity of purpose, a willingness to be held accountable, and the ability to achieve measurable outcomes. Unfortunately, almost everything in modern organizations gets in the way of teams acting with any sort of autonomy. In most companies, achieving business agility requires significant organizational change. Join @Mike Cottmeyer live from #Agile2017 during this workshop.
cPrime is an Atlassian Platinum and Enterprise expert that offers a wide range of Atlassian training on numerous platforms. In this webinar, we will provide a synopsis and preview of our most popular course, JIRA System Admin.
cPrime has developed a JIRA Administrators course that will challenge you to understand why there is a full time role dedicated to Jira Administration in companies. You will learn every object in the tool from the ground up to formulate a mind map of the entire architecture that makes this tool unique, customizable and a focal point of value. You will learn how to scale the product, how to build items for reuse and to articulate needs of clients to the technical implementation.
The New York Times Paywall is a case study based on the business transition from the traditional to digital shift of e-newspapers. The launch of digital devices favoured the growth of The Times as well as the advantages of accessibility had escalated its demands and the viewership. They adopted the Paywall strategy for additional revenue generation through subscription plans. However, the dilemma was for the long term sustenance of the latest The New York Times business model.
Dell has built their business:
- Build-to-order manufacturing
- Mass customization
- Partnerships with suppliers
- Just-in-time components inventories
- Direct sales
- Market segmentation
- Customer service
- Extensive data and information sharing with both supply partners and customers.
Based on:
The McGraw-Hill Companies. (1997). Dell Computer Corporation Online Case. Retrieved 3 6, 2011, from McGraw Hill Higher Education: http://www.mhhe.com/business/management/thompson/11e/case/dell5.html
Business recommendations and statistical analysis based on previous patient data using excel. Used a simple linear regression and a multiple linear regression to find out the specific quantitative relationship between the target variable and the explanatory variables. The multiple regression analysis provided insights on which explanatory variables have a major influence on the target variable, the Total Cost to the Hospital. Previous patient data was not enough to determine the cost to hospital.
Learn JIRA Quickly
Plan, track, work – smarter and faster
http://www.udemy.com/learn-jira-quickly
Enhance your resume skills and improve your productivity quickly
JIRA is the project management and issue tracking software. It is used by teams in all types of products and industries. It's used by Agile teams, bug tracking, helpdesk tickets and thousands of companies!
It's a must skill to have in today's industry and this course will get you started with JIRA in under 2 hours.
Presentation based on Harvard Business Review article: "What is Disruptive Innovation?", by Clayton M. Cristensen, Michael E. Raynor, and Rory McDonald – December, 2015 issue.
The theory of disruptive Innovation was introduced in the article: "Disruptive Technologies: Catching the Wave", by Joseph L. Bower and Clayton M. Christensen from the HBR january–february 1995 issue.
The Four Dimensions of Performance ImprovementTechWell
Once upon a time, in a land far, far away, a team dealt with unrealistic deadlines, impossible stakeholders, and demotivated testers, who had no time to do things smarter and faster, just hammering away on the project “hamster wheel.” Then one day, as if heaven sent, a magical, but systematic approach to performance improvement, solving performance problems, and enhancing testing service delivery arrived in the form of the Four Dimensional Performance Improvement model. Marisa Müller describes this model that recognizes that performance relies on more than just people. Four dimensions of performance improvement—worker, workplace, work, and world—make up the total system. Marisa shares how her organization went about identifying and closing gaps, and provided empirical evidence that raised the understanding of the important value added by software testing. Join Marisa in exploring practical ways to apply to your own team what they did and empower you to transform testing’s value add and service delivery.
Testing in the Age of Distraction: Flow, Focus, and Defocus in TestingTechWell
We live in interesting times. Knowledge is available at our fingertips, no matter where we are. Social networks enable communication around the world. However, along with these marvels of the information age come weapons of mass distraction. With so many things competing for our attention—and so little time to focus on real work—it’s a wonder we get anything done at all. What does this mean for testers? A common belief is that only focused concentration leads to productive work—and conversely, that distraction causes procrastination and stifles creativity. While it is important that testers find flow and maintain focus, Zeger Van Hese believes that a state of defocus—guilt-free play—can also be helpful in testing. Zeger shares tips, tricks, and tools that have helped him focus and defocus while testing. He explains not only how to benefit from distraction but also how to return to flow and focus when needed. Learn to make the most of these techniques in your testing.
These case studies can help readers to practices many simulated scenarios. These are case studies will be asked in Transformation related interviews.
All these case studies are from my 4 books, The Agilis's Guidebook, The Scrum Master Guidebook, Personal Leadership & Self-Coaching Guidebook, and A Guidebook of Coaching High-Performance team.
Grab the first 150 pages of all these books from here
1. https://www.slideshare.net/patarychandan/the-agilists-guidebook-first-150-pages
2. https://www.slideshare.net/patarychandan/the-scrum-master-guidebook-150-pages
3. https://www.slideshare.net/patarychandan/we-can-lead-a-guidebook-of-personal-leadership-and-selfcoaching
4. https://www.slideshare.net/patarychandan/a-guidebook-of-coaching-high-performance-team-200-pages
PLEASE DOWNLOAD FROM HERE:https://drive.google.com/file/d/1vHAmAU4x-hH7X1SaZwIpudeIbR6kfvmB/view?usp=sharing
The case study optimizes the HP DeskJet printer supply chain by redesigning the network using component commonality and risk pooling. The redesign leads to considerable savings to the business.
Haier: Taking a chinese company global in 2011Ilaria Fiore
Corporate strategy for HAIER business case. This presentation is based exclusively on informations and data provided in Harvard Business School's case study "Haier: Taking a chinese company global in 2011" and Wikipedia.
The presentation provides information about Haier, evaluates the situation, problems and opportunities of the company; then it describes the possible options avaiable to Haier and selects the best, according to the group's ideas.
Design, Build and Run an Effective IT (Service) Strategy to Business NeedsFlevy.com Best Practices
This Slideshare presentation is a partial preview of the full business document. To view and download the full document, please go here:
http://flevy.com/browse/business-document/design-build-and-run-an-effective-it-service-strategy-to-business-needs-279
The "Deliver Business Value with IT" series provides a good overview and actionable material of the ways a CIO can provide valuable and effective support to your company strategy and leverages business model concepts to deliver business value from IT. Martin Palmgren propose an extremely solid piece of work that comes across as the A-Z reference of how to execute and implement IT strategy from a CEO and CIO level perspective."
Executive Summary:
The CIO and the IT Department need to position as premium provider of IT services and focus on value to cost.
In order to avoid the "do we really need a CIO and IT department to bother us with technology when we can use the cloud?" the CIO has to ensure that the business strategy and business objectives are supported by IT (from a Business and IT architecture perspective). Where the IT Strategy support Strategy execution, "Time to Market", Cost Effectiveness and stakeholder expectations from an Executive, Business Unit, IT Management and IT Risk Management perspective.
Leading a large-scale agile transformation isn’t about adopting a new set of attitudes, processes, and behaviors at the team level… it’s about helping your company deliver faster to market, and developing the ability to respond to a rapidly-changing competitive landscape. First and foremost, it’s about achieving business agility. Business agility comes from people having clarity of purpose, a willingness to be held accountable, and the ability to achieve measurable outcomes. Unfortunately, almost everything in modern organizations gets in the way of teams acting with any sort of autonomy. In most companies, achieving business agility requires significant organizational change. Join @Mike Cottmeyer live from #Agile2017 during this workshop.
cPrime is an Atlassian Platinum and Enterprise expert that offers a wide range of Atlassian training on numerous platforms. In this webinar, we will provide a synopsis and preview of our most popular course, JIRA System Admin.
cPrime has developed a JIRA Administrators course that will challenge you to understand why there is a full time role dedicated to Jira Administration in companies. You will learn every object in the tool from the ground up to formulate a mind map of the entire architecture that makes this tool unique, customizable and a focal point of value. You will learn how to scale the product, how to build items for reuse and to articulate needs of clients to the technical implementation.
The New York Times Paywall is a case study based on the business transition from the traditional to digital shift of e-newspapers. The launch of digital devices favoured the growth of The Times as well as the advantages of accessibility had escalated its demands and the viewership. They adopted the Paywall strategy for additional revenue generation through subscription plans. However, the dilemma was for the long term sustenance of the latest The New York Times business model.
Dell has built their business:
- Build-to-order manufacturing
- Mass customization
- Partnerships with suppliers
- Just-in-time components inventories
- Direct sales
- Market segmentation
- Customer service
- Extensive data and information sharing with both supply partners and customers.
Based on:
The McGraw-Hill Companies. (1997). Dell Computer Corporation Online Case. Retrieved 3 6, 2011, from McGraw Hill Higher Education: http://www.mhhe.com/business/management/thompson/11e/case/dell5.html
Business recommendations and statistical analysis based on previous patient data using excel. Used a simple linear regression and a multiple linear regression to find out the specific quantitative relationship between the target variable and the explanatory variables. The multiple regression analysis provided insights on which explanatory variables have a major influence on the target variable, the Total Cost to the Hospital. Previous patient data was not enough to determine the cost to hospital.
Learn JIRA Quickly
Plan, track, work – smarter and faster
http://www.udemy.com/learn-jira-quickly
Enhance your resume skills and improve your productivity quickly
JIRA is the project management and issue tracking software. It is used by teams in all types of products and industries. It's used by Agile teams, bug tracking, helpdesk tickets and thousands of companies!
It's a must skill to have in today's industry and this course will get you started with JIRA in under 2 hours.
Presentation based on Harvard Business Review article: "What is Disruptive Innovation?", by Clayton M. Cristensen, Michael E. Raynor, and Rory McDonald – December, 2015 issue.
The theory of disruptive Innovation was introduced in the article: "Disruptive Technologies: Catching the Wave", by Joseph L. Bower and Clayton M. Christensen from the HBR january–february 1995 issue.
The Four Dimensions of Performance ImprovementTechWell
Once upon a time, in a land far, far away, a team dealt with unrealistic deadlines, impossible stakeholders, and demotivated testers, who had no time to do things smarter and faster, just hammering away on the project “hamster wheel.” Then one day, as if heaven sent, a magical, but systematic approach to performance improvement, solving performance problems, and enhancing testing service delivery arrived in the form of the Four Dimensional Performance Improvement model. Marisa Müller describes this model that recognizes that performance relies on more than just people. Four dimensions of performance improvement—worker, workplace, work, and world—make up the total system. Marisa shares how her organization went about identifying and closing gaps, and provided empirical evidence that raised the understanding of the important value added by software testing. Join Marisa in exploring practical ways to apply to your own team what they did and empower you to transform testing’s value add and service delivery.
Testing in the Age of Distraction: Flow, Focus, and Defocus in TestingTechWell
We live in interesting times. Knowledge is available at our fingertips, no matter where we are. Social networks enable communication around the world. However, along with these marvels of the information age come weapons of mass distraction. With so many things competing for our attention—and so little time to focus on real work—it’s a wonder we get anything done at all. What does this mean for testers? A common belief is that only focused concentration leads to productive work—and conversely, that distraction causes procrastination and stifles creativity. While it is important that testers find flow and maintain focus, Zeger Van Hese believes that a state of defocus—guilt-free play—can also be helpful in testing. Zeger shares tips, tricks, and tools that have helped him focus and defocus while testing. He explains not only how to benefit from distraction but also how to return to flow and focus when needed. Learn to make the most of these techniques in your testing.
Test Status Reporting: Focus Your Message for ExecutivesTechWell
Test status reporting is a key factor in the success of test projects. Stephan Obbeck shares some ideas on how to communicate more than just a red-yellow-green status report to executive management and discusses how the right information can influence their decisions. Testers often create reports that are too technical, losing crucial information in a mountain of detailed data. Management needs to make decisions—based on data they do understand—that support the test project. Stephan explains how stakeholder and risk analysis helps you identify recipients of a report and what information is of interest to them. Learn different ways of presenting data to support your message and to get the most possible attention from the executive level. Discover how to avoid pitfalls when generating reports from test automation. Produce a summary of statistics that provides insight into a test project.
Twelve Heuristics for Solving Tough Problems—Faster and BetterTechWell
As infants, we begin our lives as problem solving machines, learning to navigate a strange and complex world in which others communicate in ways we don’t understand. Initially, we hone our problem solving talents; then many of us find our explorations thwarted and eventually stop using and then begin losing our natural problem solving ability. But it doesn’t have to be that way. Psychologists tell us that people can regain lost skills and learn new ones to become better problem solvers. Payson Hall shares techniques and skills that apply to situations in real life. Specifically, learn techniques to better define problems, and explore twelve heuristics for generating solutions that can help when you and your team are staring at a blank paper and struggling to find candidate solutions for further consideration. Learn when random search is appropriate, how binary search can help with diagnostics, strategies for identifying and overcoming opposition—and when transferring the problem to someone else might be the best strategy of all.
Test Automation Patterns: Issues and SolutionsTechWell
Automating system level test execution can result in many problems. It is surprising to find that many people encounter the same problems, yet they are not aware of common solutions that have worked well for others. These problem/solution pairs are called “patterns.” Seretta Gamba recognized the commonality of these test automation issues and their solutions and, together with Dorothy Graham, has organized them into Test Automation Patterns. Although unit test patterns are well known, Seretta and Dorothy’s patterns address more general issues. They cover management, process, design, and execution patterns to help you recognize common test automation issues and show you how to identify appropriate patterns to solve the problems. Issues such as No Previous Automation, High ROI Expectations, and High Test Maintenance Cost are addressed by patterns such as Maintainable Testware, Tool Independence, and Management Support. Laptop required (with USB access). An offline version of the wiki will be available to copy to your laptop from a USB stick to use during the session.
Agile Code Reviews for Better Software—SoonerTechWell
Code reviews are often thought of as anti-agile, cumbersome, and disruptive. However, done correctly, they enable agile teams to become more collaborative and effective, and ultimately to produce higher quality software faster. Mark Hammer describes how lightweight code review practices succeed where more cumbersome methods fail. Mark offers tips on the mechanics of lightweight code reviews and compares five common styles of review. He looks at real-world examples and reveals impressive results. Gain new insights into how much time to spend in review, how much code to review in one session, and how author preparation practices can increase the efficiency of a review. Learn how peer code review can improve the performance of individual developers, their teams, and the software they produce. Mark shares the specific benefits of peer code review, including ROI and the ultimate goal of producing higher quality software faster.
The question of how much design to do up-front on a project is an engaging one. Too much design often results in overkill, complexity, and wasted effort. Too little design results in insufficient system structures that require later rework, additional complexity, and wasted effort. How can we know what the right balance is? Ken Pugh shows how to use advice taken from Design Patterns, coupled with the attitude of not building what you don’t need from agile. The trick is in observing potential variation, how it may affect you in the future, and then how to isolate these risks in a simple manner. Ken describes the essence of emergent design – that is, start with a simple design and let it evolve as the requirements evolve. He also demonstrates how to refactor to achieve better designs and how this is different from refactoring bad code.
Your test strategy is the design behind your plan—the set of big-picture ideas that embodies the overarching direction of your test effort. It captures the stakeholders’ values that will inspire, influence, and ultimately drive your testing. It guides your overall decisions about the ways and means of delivering on those values. The weighty test strategy template mandated in many organizations is not conducive to thinking through the important elements of a test strategy and then communicating its essentials to your stakeholders. A lightweight medium like a mindmap is far more flexible and direct. In this interactive session Fiona Charles works with you to develop your own strategic ideas in a mindmap, exploring along the way what really matters in a test strategy and how best to capture it using a mindmap. Fiona shares tips on how to use your mindmap to engage your stakeholders’ interest, understanding, and buy-in to your strategy.
The Leadership Tutorial: Improving Your Ability to Stand and DeliverTechWell
In this highly interactive tutorial, Andy Kaufman helps you wrestle with real-world leadership issues we all face—influencing without authority, motivating your team, and dealing with conflict. Explore the difference between leadership and management—and why it matters—and get a clear picture of a leader’s responsibilities, including the balance between short- and long-term focus and the need to deliver results while developing organizational capability. Discuss the importance of developing your team members’ leadership skills, including practical ways to do so even with a limited training budget. Andy delves into the importance of one-on-one relationships and delivers proven insights on managing upward, dealing with peers, and developing stronger bonds both inside and outside your organization. Accelerate your ability to influence your organization, your projects, and your career to become the leader your team needs and demands. Take away practical tools to help you lead your team, including a template for formalizing a team charter and a reproducible survey to solicit leadership feedback from bosses, peers, stakeholders, and team members.
It's a Phone First! How to Test Your Five-star Mobile AppsTechWell
Mobile application development shares many similarities-and some stark differences-with traditional web-based development. To build, test, and deploy five-star mobile applications, your organization needs-from inception-a focused test strategy to drive quality. Employing the wrong approaches and tools can leave your business sponsors and clients wondering what went wrong. Will Hurley outlines the current mobile landscape and explains what can and cannot be controlled in the mobile lifecycle. He explores the current landscape and limitations on tools for testing mobile apps, and offers guidance on what-and what not to-automate. With Will's guidance, you’ll learn how to establish a mobile lifecycle test strategy that is both leading edge and practical. From high-level feature classifications that are meaningful to your business to low-level test types and approaches that practitioners need to know, Will shares the knowledge you need to release a five-star app.
A Rapid Introduction to Rapid Software TestingTechWell
You're under tight time pressure and have barely enough information to proceed with testing. How do you test quickly and inexpensively, yet still produce informative, credible, and accountable results? Rapid Software Testing, adopted by context-driven testers worldwide, offers a field-proven answer to this all-too-common dilemma. In this one-day sampler of the approach, Michael Bolton introduces you to the skills and practice of Rapid Software Testing through stories, discussions, and "minds-on" exercises that simulate important aspects of real testing problems. The rapid approach isn't just testing with speed or a sense of urgency; it's mission-focused testing that eliminates unnecessary work, assures that the most important things get done, and constantly asks how testers can help speed up the successful completion of the project. Join Michael to see how rapid testing focuses on both the mind set and skill set of the individual tester who uses tight loops of exploration and critical thinking skills to help continuously re-optimize testing to match clients' needs and expectations.
Reduce Release Cycle Time: Nine Months to a Week - Nice!TechWell
Picture this scene from three years ago: Employing the corporately mandated processes, a software engineering team is delivering system updates about once every nine months. When their senior user suddenly demands the next delivery in twenty-two weeks-half the current cycle duration-the team realize that they must quickly change development practices. Mathew Bissett describes how Her Majesty's Government did precisely that-and much, much more. First, they reduced delivery cycles from unpredictable dates every nine months to predictable releases every six weeks. Then, they cut releases cycle time to once every week. By identifying and mitigating risks early in the work intake process, enforcing quality gates, executing multiple test levels concurrently-and more-they dramatically increased throughput with the same or better quality. Today, these new processes provide their teams the best balance of structure versus agility. Join Mathew to see if what works for Her Majesty's Government might just work for you and your company.
Exploratory Testing on Agile Projects: Combining SBTM and TBTMTechWell
Exploratory testing provides both flexibility and speed—characteristics that are vitally important with the quick pace of short agile iterations. With session-based test management (SBTM), exploratory testing is structured and documented in pre-defined sessions. A newer approach, thread-based test management (TBTM), organizes test efforts by threads of activities rather than sessions. So, how do you retain the traceability of SBTM without losing the creativity offered by TBTM? The answer is xBTM—a combination of SBTM and TBTM. After introducing SBTM and TBTM, Christin shows how she uses xBTM on projects to obtain maximum efficiency—only creating test documentation that actually adds value. Using a mock example, Christin describes the xBTM workflow on an agile project, covering all the steps from test planning and performing the tests through reporting. Her focus is on sharing practical examples and providing a range of flexible tools that you can immediately apply on almost any project.
Beyond Processes and Tools: What about Ethics?TechWell
Too often we focus only on the latest headline-grabbing processes and products. While recognizing that we must respond to ever-changing business needs, deep down we know we must live by a few absolutes as we approach our daily work. At the core is a standard of ethical conduct that we always uphold. With an ethical underpinning, we will earn the trust and respect of our peers and those we serve. Jackie Pulley presents a framework for professional ethics within the IT development profession, including key practices from her experiences gained during more than twenty years in IT software development. Drawing on the PMI ethics standards, her personal lessons learned, and conversations with other leaders, Jackie offers a thought-provoking session for C-Level executives, freshly degreed software developers, and everyone in between. Based on a personal assessment you take in the session, you can walk away with a personal standard of ethical conduct to live by everyday.
Meet Big Agile: Testing on Large-Scale ProjectsTechWell
Are you embarking on a large-scale, globally distributed, multi-team scrum project? Have you already identified the potential testing challenges that lie ahead? Or have you belatedly encountered them and are now working on them in real-time? Five years and more than 200 projects into its agile journey, Dell Enterprise Solutions (ESG) has empirically determined that once a project extends beyond three scrum teams, interesting testing challenges arise—inconsistent “done” criteria, integration testing underscored by epic/story interdependencies across teams, test automation inconsistency, and uncoordinated regression testing. Worse yet, the more teams involved, the less likely it is that a single scrum team has the visibility to validate the overall product from a customer usage perspective as the product evolves through sprints. Geoff Meyer serves up some lessons learned from within the Dell ESG Validation organization as it evolved its agile testing and automation strategies from a waterfall-based environment to one that fully embraced agile Scrum across its entire software product portfolio.
Large-Scale Agile Test Automation Strategies in PracticeTechWell
After providing an introduction to several key agile testing concepts—including the Automation Triangle and the Test Automation Quadrants—Geoff Meyer discusses approaches to effectively deliver automated testing. Geoff shares practical insights and demonstrates how they were employed in the test automation strategies developed for several large-scale agile projects at Dell. He shows how the overall test strategy and implementation of each underlying agile concept was influenced by the realities of the project’s organization structure, application architecture, incumbent tools, and tester skillsets. Geoff explores the similarities of the projects from their common goals of establishing automated regression suites, achieving in-sprint automation, and test staffing approaches. More importantly, he delves into the implications of organizational structures and how they led to divergent approaches to test strategy from the choice of automation frameworks to the decisions to automate at the REST/SOAP-based API level or UI level.
Automation Culture: Essential to Agile SuccessTechWell
For organizations developing large-scale applications, transitioning to agile is challenging enough. If your organization has not yet adopted an automation culture, brace yourself for a big surprise because automation is essential to agile success. From the safety nets provided by automated unit and acceptance tests to the automation of build, build verification, and deployment processes, the iterative nature of agile demands a culture of automation across your engineering organization. Geoff Meyer shares lessons learned in adopting a test automation culture as the Dell Enterprise Systems Group simultaneously adopted Scrum and agile processes across its entire software product portfolio. Learn to address the practical challenges of establishing an automation culture at the outset by ensuring that your organizational makeover incorporates changes to your hiring, staffing, and training practices. Find out how you can apply automation beyond the Scrum team in areas including continuous integration, scale and stress testing, and performance testing.
DevOps, sibling of Agile is born of the need to improve IT service delivery agility to the more stable environment.
DevOps movement emphasizes tearing the boundaries between makers (Development) & caretakers (Operations) of IT services/products.
Agile Project Management in a Waterfall World: Managing Sprints with Predicti...John Carter
Applying Agile methods in a waterfall world seemed impossible until we discovered the 10 essential skills and tools. Five of these skills are organizational, while others translate the short intervals characteristic of Agile to the world outside of Software. User Stories becomes Boundary Conditions; Burn-down charts becomes Deliverable Hit Rate charts; Sprints become HW intervals; Sprint Retrospectives become Event Timeline Retrospectives, while the project as a whole is managed using Boundary Conditions. This presentation shows examples of these tools and shows examples of how they are applied.
Mind the Gap: How to bridge the gap between development and operations with release management
The release management process remains challenging for large IT organizations due to the continuing disconnect between development, QA, and operations teams. The challenge faced by these large enterprises is that process maturity, methodology, and platforms vary greatly across teams, organizations and business units. These challenges often produce gaps between development and operations teams. Release management is still being done, but with very inconsistent results and at a high cost, providing minimal insight and a lack of audit compliance.
Join us as Julian Fish, Director of Products at Serena Software, demonstrates how the unique integration framework and process capabilities of Serena Release Control can deliver a consistent and repeatable process that provides complete traceability, audit and compliance across Waterfall, Progressive and Agile processes, for both ITIL and DevOps approaches, and supporting Mainframe to mobile platforms.
• Overall 19 years of IT experience, with 17 years as Oracle Core/Apps DBA
• Have International work experience at Singapore for 3 years at client location
• Have good exposure on implementing Industry best practice through ITIL, Lean and PRINCE2
• Have experience in managing large Global teams on Oracle Managed service as DBA Delivery Lead/Manager for more than 10 years from multiple locations, onsite/offshore model
• Have good exposure to work on client facing role, with customer satisfaction (CSAT), change control board, vendor management and handling multiple stake holders
• Have working knowledge under diversified Oracle Apps environments and versions
• Have good exposure in Project planning, scheduling and delivery
• Collaborate with Project Managers and Technical Directors to work on capacity planning etc
• Develop overall implementation solution plan, and serve as a lead as required, to implement the installation, customization, and integration efforts
• Able to take challenges and meeting SLA during Crisis period, building team and implementing process for smooth delivery
• Worked with major clients like GE, CISCO, SONY etc. at client facing role
• Worked with Pre-sales team for preparing proposals, analyzing clients process and deciding the right solution
Technical Webinar: By the (Play) Book: The Agile Practice at OutSystemsOutSystems
In 2001, the Agile Manifesto took the world by storm, and it changed how software is built forever. Also in 2001, OutSystems, another disruptive force in the world of traditional waterfall software development, was born.
Not coincidentally, OutSystems has been using Agile Practices all along. However, because of the sheer speed at which we’re able to respond, we’ve had to come up with a few twists in our approach. We’re even putting it into a services delivery playbook.
In our webinar, “By the (Play)Book: The Agile Practice at OutSystems,” Engagement Guild Master and Expert Nuno Fernandes will show you how OutSystems approaches Agile Development and makes sure nothing slips.
In this session you will:
- Learn roles and respective responsibilities.
- Understand project phases with a clear focus on sprint development.
- Discover how we approach the user story life cycle in particular.
- See how a really solid structure, calendar and organization help maximize productivity.
Webinar: https://www.outsystems.com/learn/courses/59/webinar-the-agile-practice-at-outsystems/
Free Online training: https://www.outsystems.com/learn/courses/
Follow us on Twitter http://www.twitter.com/OutSystemsDev
Like us on Facebook http://www.Facebook.com/OutSystemsDev
Session on evaluation of DevSecOps. This tutorial is made the very basic process of the DevOps cycle for the beginner level. So sometimes we won’t use very deep technical terms to understand.
DevOps is a set of practices that aims to provide superior quality software quickly by integrating the processes between the development and the operation teams. DevOps is an agile relationship between development and IT operations. DevOps is the abbreviation for Development and Operations. The development includes Plan, Create, Verify and Package. Operations include Release, Configure, and Monitor.
DevOps, SAFe and critical information bearers: A practical approach for plann...Bosnia Agile
A lot of enterprises have successfully adopted agile practices and are now challenged by the questions: How do we scale it? How will we know what is going on in development, product management and deployment? How do we know that we develop according to business priorities? How do we make the quicker development cycles lead to faster market response and more frequent releases? To answer these some companies have turned to a DevOps approach and use concepts like the Scaled Agile Framework (SAFe). Join us in this session to look at the critical information bearers in such a setup and how information from business planning, portfolio management, program management and release planning are connected.
Is Agile Development right for you? Many proponents would say, of course it is. But it can also be a little scary, especially if you come from a traditional approach. This presentation describes two case studies in which Agile development was successful, and some situations in which it may not be the best choice.
As more organizations begin to adopt agile on multiple, interdependent teams, how do we ensure that the success within a team can translate to success at the enterprise level?
Presented by: Sanjiv Augustine, President of LitheSpeed
Do you ever feel you have lost confidence in your own abilities? Why does this happen? Isabel Evans spends a lot of time painting. Someone once commented, “Why are you doing this, when you are not very good at it?” And gradually she stopped drawing and painting, after being intimidated by a conventional vision of what good art should look like. At the same time, she experienced a parallel loss of confidence in her professional abilities. Attempting creative pursuits like drawing and painting is essential to cognitive, emotional, creative abilities and she began to understand the correlation between her creative activities and her confidence. Making errors, being wrong, failing – that is a generous gift we receive when we practice outside our skill level. By staying in a comfort zone and repeating successes, we stagnate. As Isabel started to create again she thought “I don’t feel good at it, I do feel good doing it” The difference was that she was learning, having ideas and the act of re-engaging with failure, together with the comradeship of friends and colleagues, including at Women Who Test, Isabel has regained her confidence in her professional abilities, and been able to reboot her career and joy. Join Isabel to share a journey from self-perceived failure, to recovery and renewed learning.
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
Imagine this … As soon as any developed functionality is submitted into the code repository, it is automatically subjected to the appropriate battery of tests and then released straight into production. Setting up the pipeline capable of doing just that is becoming more and more common and something you need to know about. But most organizations hit the same stumbling block—just what IS the appropriate battery of tests? Automated build architectures don't always lend themselves well to the traditional stages of testing. In this hands-on tutorial, Melissa Benua introduces you to key test design principles—applicable to organizations both large and small—that allow you to take full advantage of the pipeline's capabilities without introducing unnecessary bottlenecks. Learn how to make highly reliable tests that run fast and preserve just enough information to let testers and developers determine exactly what went wrong and how to reproduce the error locally. Explore ways to reduce overlap while still maintaining adequate test coverage. Take back ideas about which test areas could benefit from being combined into a single suite and which areas could benefit most from being broken out altogether.
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
DevOps is transforming software development with many organizations adopting lean development practices, implementing continuous integration (CI), and performing regular continuous deployment (CD) to their production environments. However, the database is largely ignored and often seen as a bottleneck in the DevOps process. Steve Jones discusses the challenges of database development and why many developers find the database to be an impediment to the CD process. Steve shares the techniques you can use to fit a database into the DevOps process. Learn how to store database code in a version control system, and the differences between that and application code. Steve demonstrates a CI process with SQL code and uses automated testing frameworks to check the code. Steve then shows how automated releases with manual gates can reduce the stress and risk of database deployments while ensuring consistent, reliable, repeatable releases to QA, UAT, and production.
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.
GDG Cloud Southlake #33: Boule & Rebala: Effective AppSec in SDLC using Deplo...James Anderson
Effective Application Security in Software Delivery lifecycle using Deployment Firewall and DBOM
The modern software delivery process (or the CI/CD process) includes many tools, distributed teams, open-source code, and cloud platforms. Constant focus on speed to release software to market, along with the traditional slow and manual security checks has caused gaps in continuous security as an important piece in the software supply chain. Today organizations feel more susceptible to external and internal cyber threats due to the vast attack surface in their applications supply chain and the lack of end-to-end governance and risk management.
The software team must secure its software delivery process to avoid vulnerability and security breaches. This needs to be achieved with existing tool chains and without extensive rework of the delivery processes. This talk will present strategies and techniques for providing visibility into the true risk of the existing vulnerabilities, preventing the introduction of security issues in the software, resolving vulnerabilities in production environments quickly, and capturing the deployment bill of materials (DBOM).
Speakers:
Bob Boule
Robert Boule is a technology enthusiast with PASSION for technology and making things work along with a knack for helping others understand how things work. He comes with around 20 years of solution engineering experience in application security, software continuous delivery, and SaaS platforms. He is known for his dynamic presentations in CI/CD and application security integrated in software delivery lifecycle.
Gopinath Rebala
Gopinath Rebala is the CTO of OpsMx, where he has overall responsibility for the machine learning and data processing architectures for Secure Software Delivery. Gopi also has a strong connection with our customers, leading design and architecture for strategic implementations. Gopi is a frequent speaker and well-known leader in continuous delivery and integrating security into software delivery.
UiPath Test Automation using UiPath Test Suite series, part 4DianaGray10
Welcome to UiPath Test Automation using UiPath Test Suite series part 4. In this session, we will cover Test Manager overview along with SAP heatmap.
The UiPath Test Manager overview with SAP heatmap webinar offers a concise yet comprehensive exploration of the role of a Test Manager within SAP environments, coupled with the utilization of heatmaps for effective testing strategies.
Participants will gain insights into the responsibilities, challenges, and best practices associated with test management in SAP projects. Additionally, the webinar delves into the significance of heatmaps as a visual aid for identifying testing priorities, areas of risk, and resource allocation within SAP landscapes. Through this session, attendees can expect to enhance their understanding of test management principles while learning practical approaches to optimize testing processes in SAP environments using heatmap visualization techniques
What will you get from this session?
1. Insights into SAP testing best practices
2. Heatmap utilization for testing
3. Optimization of testing processes
4. Demo
Topics covered:
Execution from the test manager
Orchestrator execution result
Defect reporting
SAP heatmap example with demo
Speaker:
Deepak Rai, Automation Practice Lead, Boundaryless Group and UiPath MVP
Smart TV Buyer Insights Survey 2024 by 91mobiles.pdf91mobiles
91mobiles recently conducted a Smart TV Buyer Insights Survey in which we asked over 3,000 respondents about the TV they own, aspects they look at on a new TV, and their TV buying preferences.
DevOps and Testing slides at DASA ConnectKari Kakkonen
My and Rik Marselis slides at 30.5.2024 DASA Connect conference. We discuss about what is testing, then what is agile testing and finally what is Testing in DevOps. Finally we had lovely workshop with the participants trying to find out different ways to think about quality and testing in different parts of the DevOps infinity loop.
Essentials of Automations: Optimizing FME Workflows with ParametersSafe Software
Are you looking to streamline your workflows and boost your projects’ efficiency? Do you find yourself searching for ways to add flexibility and control over your FME workflows? If so, you’re in the right place.
Join us for an insightful dive into the world of FME parameters, a critical element in optimizing workflow efficiency. This webinar marks the beginning of our three-part “Essentials of Automation” series. This first webinar is designed to equip you with the knowledge and skills to utilize parameters effectively: enhancing the flexibility, maintainability, and user control of your FME projects.
Here’s what you’ll gain:
- Essentials of FME Parameters: Understand the pivotal role of parameters, including Reader/Writer, Transformer, User, and FME Flow categories. Discover how they are the key to unlocking automation and optimization within your workflows.
- Practical Applications in FME Form: Delve into key user parameter types including choice, connections, and file URLs. Allow users to control how a workflow runs, making your workflows more reusable. Learn to import values and deliver the best user experience for your workflows while enhancing accuracy.
- Optimization Strategies in FME Flow: Explore the creation and strategic deployment of parameters in FME Flow, including the use of deployment and geometry parameters, to maximize workflow efficiency.
- Pro Tips for Success: Gain insights on parameterizing connections and leveraging new features like Conditional Visibility for clarity and simplicity.
We’ll wrap up with a glimpse into future webinars, followed by a Q&A session to address your specific questions surrounding this topic.
Don’t miss this opportunity to elevate your FME expertise and drive your projects to new heights of efficiency.
Securing your Kubernetes cluster_ a step-by-step guide to success !KatiaHIMEUR1
Today, after several years of existence, an extremely active community and an ultra-dynamic ecosystem, Kubernetes has established itself as the de facto standard in container orchestration. Thanks to a wide range of managed services, it has never been so easy to set up a ready-to-use Kubernetes cluster.
However, this ease of use means that the subject of security in Kubernetes is often left for later, or even neglected. This exposes companies to significant risks.
In this talk, I'll show you step-by-step how to secure your Kubernetes cluster for greater peace of mind and reliability.
Epistemic Interaction - tuning interfaces to provide information for AI supportAlan Dix
Paper presented at SYNERGY workshop at AVI 2024, Genoa, Italy. 3rd June 2024
https://alandix.com/academic/papers/synergy2024-epistemic/
As machine learning integrates deeper into human-computer interactions, the concept of epistemic interaction emerges, aiming to refine these interactions to enhance system adaptability. This approach encourages minor, intentional adjustments in user behaviour to enrich the data available for system learning. This paper introduces epistemic interaction within the context of human-system communication, illustrating how deliberate interaction design can improve system understanding and adaptation. Through concrete examples, we demonstrate the potential of epistemic interaction to significantly advance human-computer interaction by leveraging intuitive human communication strategies to inform system design and functionality, offering a novel pathway for enriching user-system engagements.
Transcript: Selling digital books in 2024: Insights from industry leaders - T...BookNet Canada
The publishing industry has been selling digital audiobooks and ebooks for over a decade and has found its groove. What’s changed? What has stayed the same? Where do we go from here? Join a group of leading sales peers from across the industry for a conversation about the lessons learned since the popularization of digital books, best practices, digital book supply chain management, and more.
Link to video recording: https://bnctechforum.ca/sessions/selling-digital-books-in-2024-insights-from-industry-leaders/
Presented by BookNet Canada on May 28, 2024, with support from the Department of Canadian Heritage.
Generating a custom Ruby SDK for your web service or Rails API using Smithyg2nightmarescribd
Have you ever wanted a Ruby client API to communicate with your web service? Smithy is a protocol-agnostic language for defining services and SDKs. Smithy Ruby is an implementation of Smithy that generates a Ruby SDK using a Smithy model. In this talk, we will explore Smithy and Smithy Ruby to learn how to generate custom feature-rich SDKs that can communicate with any web service, such as a Rails JSON API.
State of ICS and IoT Cyber Threat Landscape Report 2024 previewPrayukth K V
The IoT and OT threat landscape report has been prepared by the Threat Research Team at Sectrio using data from Sectrio, cyber threat intelligence farming facilities spread across over 85 cities around the world. In addition, Sectrio also runs AI-based advanced threat and payload engagement facilities that serve as sinks to attract and engage sophisticated threat actors, and newer malware including new variants and latent threats that are at an earlier stage of development.
The latest edition of the OT/ICS and IoT security Threat Landscape Report 2024 also covers:
State of global ICS asset and network exposure
Sectoral targets and attacks as well as the cost of ransom
Global APT activity, AI usage, actor and tactic profiles, and implications
Rise in volumes of AI-powered cyberattacks
Major cyber events in 2024
Malware and malicious payload trends
Cyberattack types and targets
Vulnerability exploit attempts on CVEs
Attacks on counties – USA
Expansion of bot farms – how, where, and why
In-depth analysis of the cyber threat landscape across North America, South America, Europe, APAC, and the Middle East
Why are attacks on smart factories rising?
Cyber risk predictions
Axis of attacks – Europe
Systemic attacks in the Middle East
Download the full report from here:
https://sectrio.com/resources/ot-threat-landscape-reports/sectrio-releases-ot-ics-and-iot-security-threat-landscape-report-2024/
Connector Corner: Automate dynamic content and events by pushing a buttonDianaGray10
Here is something new! In our next Connector Corner webinar, we will demonstrate how you can use a single workflow to:
Create a campaign using Mailchimp with merge tags/fields
Send an interactive Slack channel message (using buttons)
Have the message received by managers and peers along with a test email for review
But there’s more:
In a second workflow supporting the same use case, you’ll see:
Your campaign sent to target colleagues for approval
If the “Approve” button is clicked, a Jira/Zendesk ticket is created for the marketing design team
But—if the “Reject” button is pushed, colleagues will be alerted via Slack message
Join us to learn more about this new, human-in-the-loop capability, brought to you by Integration Service connectors.
And...
Speakers:
Akshay Agnihotri, Product Manager
Charlie Greenberg, Host
Connector Corner: Automate dynamic content and events by pushing a button
Scaling Agile at Dell: Real-life Problems - and Solutions
1.
AT5
Concurrent Session
11/8/2012 2:15 PM
"Scaling Agile at Dell:
Real-life Problems—and Solutions"
Presented by:
Geoff Meyer & Brian Plunkett
Dell, 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. Geoff Meyer
Dell, Inc.
A test architect in the Dell Enterprise Solutions group, Geoff Meyer has more than twenty-six
years of experience as a software developer, manager, and business analyst. Although Geoff’s
early “agile experience” came while playing peewee ice hockey, it wasn’t until 2008 that he first
applied agile techniques in a software development setting as a product owner. Geoff is an
active member of the Agile Austin community and co-chair of the Agile Steering committee in
Dell Enterprise Solutions Group. He works tirelessly to promote the one-team concept and
continually root out the organizational anti-patterns that prospered under the waterfall regime.
Brian Plunkett
Dell, Inc.
A director of software development in the Dell Enterprise Solutions Group, Brian Plunkett has
more than thirty-six years of experience in software development. He honed his skills running
very large, very regimented, very frustrating waterfall software projects in a large organization.
Brian then ran agile-ish projects in small startups and was impressed with the dramatic
improvement in productivity. Brian introduced the agile methodology to Dell’s System
Management Software organization five years ago with a small project, and he has been
steadily refining techniques with larger and larger projects.
3. Scaling Agile @ Dell
Real-life Problems – and Solutions
Agile East 2012
Geoff Meyer, geoffrey_meyer@dell.com
Brian Plunkett, brian_plunkett@dell.com
8 November 2012
Last updated: August 30, 2012
Agenda
• Introductions
Dell s
• Dell’s Agile Journey
• Agile @ Dell Model
– Adaptations for Large-Scale Agile
– Planning & Forecasting
– The Automation Culture
• The Lessons of Large
2
1
4. Introductions
3
Geoff Meyer
• Dell Inc, 1998 – present
– Responsibilities:
› Agile Steering co-chair
› Systems Management Software
› Software Globalization / Localization
› Offshore Development
– Roles:
› SW Manager, Program Manager, Test Architect
Corp.
• NCR Corp 1984 – 1998
– SW developer, Project Lead, SW Manager
• B.S. Computer Science, San Diego State University
• Masters Engineering Management - NTU
4
2
5. Brian Plunkett
• Dell Inc,: 2006 – present
– SW Director
– Systems Management Software
• Startups: 2000 – 2006
• Tandem Inc/Compaq: 1988 – 2000
• Solar Cell research, Computer Graphics Peripherals:
1978 - 1988
– SW developer, Architect
• MSEE Brown University/University of
Minnesota/University of Vermont
5
Dell’s Agile Journey
6
3
6. Global Design and Development
Taiwan Design
Center
Nashua Design
Center
Minnesota
Design
Center
Silicon Valley
Design Center
Israel Design
Center
Austin
Design Center
Bangalore
Design Center
7
Agile @ Dell
3-day training
sessions
Education
Hired Agile
Coach
Agile @ Dell
incorporated into
Training
Monthly Rally
Training
Tools/Process
T l /P
PilotDeployed Rally
2008
Projects
Pilot Project
(Dev only)
Org/Culture/
Community
Adopt
Test Automation
2009
Agile Dell
A il @ D ll
model
Steering
committee
Integrated Test into
Agile
TFS ALM
Pilot
Agile
A l @ Dell
ll
refresh
Optimize
2011
2010
Broad
adoption
Agile Refresher
Workshops
2012
X-Large Project
(15)
Large Project (9)
Agile Dallas
Agile Austin
Collaborative seating
Agile @ Dell Brownbags
8
4
7. Signs of Trouble
• Thursday’s Build
• Planning more stories into sprint than team’s
velocity
• High % of carry-overs
• Inability to Automate Acceptance Tests
within Sprint
• “Engineering” Stories
• Assessing Project Progress by Story Points completed
get credit’
• Story Splitting at the end of the sprint to ‘get credit
• User Story Blinders
• Insufficient Product Owner bandwidth
Large-Scale
Culture Transition
• Early commitment on Requirements
• Insufficient Detail in Requirements
• Development vs. Test
l
• A different “School” of Test1
• Fail Early, Inspect & Adapt
1 – Scott Barber “Approaches to Software Testing: An Introduction “
10
5
8. Agile @ Dell Adaptations
11
Agile @ Dell
Core Activities
• Pre-Sprint activities:
– Staffing
– Training - Project tools and p
g
j
processes
– CI/Build environment
– Automation Framework and BVT
• Establish Project-wide ‘Done’ criteria
• End-to-end, short duration User Stories
• Test Automation is included User Story acceptance criteria
y p
• Scrum Teams are responsible for regression
• Refresher Workshops for new projects
12
6
9. Base Model - Agile @ Dell
Feature
Complete
Release Plan
Pre-sprint activities
Sprints
EDG (Usability)
Wireframes
Pre-sprints
1
1
2
2
Development
Architecture
Release Planning
Pre-sprints
HW resources
1
2
Test
Code Freeze
3
3
…
3
…
N-1
N-1
N
N
N-1
Release
Exit
N
Hardening
Automation FW/Tools
Pre-sprints
HW resources
PRP
Define
Plan
Develop
Launch
13
Project Complexity
Key Characteristics
Characteristic
Description
Large-Scale
Project consists of more than 4 Scrum
teams
Interdependency
Requirements implemented across
multiple Scrum teams
Extensive Configuration
Matrix
Extensive HW or SW configurations
Waterfall Intersection
One or more components are managed
using Waterfall
Geography
Project members are Geographically
dispersed
14
7
10. Agile @ Dell with Adaptations
Feature
Complete
Release Plan
Pre-sprint activities
1
1
2
2
Development
Architecture
Release Planning
Pre-sprints
HW resources
1
2
Test
3
3
…
3
Automation FW/Tools
Pre-sprints
HW resources
PRP
Define
Code Freeze
Sprints
EDG (Usability)
Wireframes
Pre-sprints
Plan
Release
Exit
N
N
N-1
…
Stability
N-1
N-1
N
Hardening
Stability
Extended Sprint Test
y
Software System Test
Develop
Launch
15
Agile @ Dell
Large-Scale
• High-Level Architecture is completed prior to first sprint
• Conduct Follow-on Release Planning sessions
• Assign Product Owner Proxy to each Scrum Team
• Measure Project Progress by Earned Business Value (EBV)
• Incorporate Stabilization Sprints into Release Plan
8
11. Agile @ Dell
Interdependency
• Minimize the dependencies across Scrum teams
• Release Planning synch-up is conducted after each Sprint
• Solution System Test(SST) effort staffed and resourced
– Ensures fidelity of intended customer usage
– Enabler for Customer Beta testing
What is Solution System Test (SST)?
IS
IS NOT
Requirements-based
Functional testing
Customer-usage based
Build verification
Workflow-based Interoperability validation
First time integration
Three phased approach
Performance benchmark testing
1.
2.
3.
Test Design/Development
Test Execution and Regression
Final Regression
Pre-SST
•
•
•
•
18
Workflow Design
Test Analysis
Test Design
Test Development
SST
• Automation Development
• Test Execution
• Regression Testing
Hardening
Test Regression
FV
Final Validation
Confidential
9
12. Agile @ Dell
Extensive Configuration Matrix
• Establish ‘reference’ configuration(s) to be used for Scrum Test efforts
• For HW-extensive configurations, staff Test-only Extended Sprints
• E d d S i T b i work on previously accepted user stories across extended
Extended Sprint Test begins k
i l
d
i
dd
configurations
19
Extended Sprint Test
Primarily used on SW for HW projects
• Scrum team establishes Acceptance criteria
• Scrum Test members identify all Test scenarios
• Scrum team owns all test case execution against
reference configuration(s)
• Extended Sprint Test team is delegated the Test
Execution
Configurations
Positive
X
Negative
X
X
X
X
Boundary
d
X
Stress
X
Scalability
X
Globalization
X
X
X
Concurrency
X
X
X
X
X
X
X
X
X
• Defects are top priority of the Scrum team
Candidate for Extended
Sprint Test
20
10
13. Agile @ Dell
Waterfall Intersection
• Perform iterative planning cycle with the Waterfall team:
1. Use initial external teams design/schedules as input into Release Planning
g
g
2. Identify User Stories that have external Dependencies
3. Update Release Plan to align all User Stories which have external Dependencies
4. Interlock on schedule misalignment
5. Repeat steps 3-4 until dependency issues are resolved.
21
Agile @ Dell
Geography
• Co-location of a Scrum team is always
preferred
• Limit geographical distribution of
Scrum team to no more than two timezones
• Scrum teams within a project can be
distributed
22
11
14. Agile @ Dell
Project Self-Assessment
Key Questions
Does my Scrum team consist of Development and Test?
Does my Scrum team exit Sprint Planning with confidence that they can deliver what they committed to?
At the end of a sprint does my Scrum team deliver “Working Software”
Is Test Automation included in Acceptance Criteria of a User Story
Does my Scrum team conduct Retrospectives at the end of each Sprint with actionable improvements to make
in the next?
Does my Project “keep the pipeline full” by having a Prioritized Release Backlog?
Does my Project conduct Release Planning meetings?
Does my Project have an Automated Build Process which includes UT and BVT?
Does my Project execute nightly Automated Regression Tests?
23
Planning and Forecasting
24
12
15. Staffing Guidelines
• PG Enterprise is organized into Functional
Organizations
• Funding of an Agile Project needs to encompass
team membership
• Guidelines for early stages of project concept
and planning:
Phase
Organization
Scrum
Measure
Ratio
Test
Dev : Test
2:1
Usability
Usability: Scrum Teams
1 : 1.5
Documentation
Doc : Scrum Teams
1:3
Extended Sprint Test
Test
Test : Scrum Teams
1.5 : 1
Solution System Test
Test
Test : Scrum Teams
1: 1.5
25
Roles/Responsibilities
Product Owner Council (Customer Team1)
Product Owner
Product Management
Epic Prioritization & Business Value
Cascade Vision & Themes to team
Represents Customer - Profiles/Roles
Requirement Acceptance
q
p
User Story Development
Customer rep. for Scrum team
Story Acceptance
Product Owner Proxy
1 per Scrum
Scrum Master
Facilitate, Remove Scrum impediments
Development
Architecture, Design, Development, Unit Test
1 per Scrum
4-5 per Scrum
T
Test
Test Design, Automation Development
1 : 1.75
InfoDev
User-facing text, error messages, online help
1 per 3 scrum team
UI
UI Design, Development, Unit Test
1 per Scrum
26
Scrum teams
Customer Team is the term used by Lisa Crispin and Janet Gregory in their book: “Agile Testing: A Practical
Guide for Testers and Agile Teams”
13
16. The Automation Culture
27
Automation Culture
• Unit Test Automation
• Web-services led Test Automation for Functional
Testing
• In-Sprint, Automated Acceptance Tests
• UI automation on Customer Usage workflows
• Automated CI (UT, Build, BVT)
• Subsystem Integration Verification Test (IVT)
y
g
• Automation-driven, Large-Scale performance
characterization
28
14
17. Success Factors for Test Automation
Critical Tasks
Dev
Identification of Acceptance Tests for a User Story that are automatable within Sprint
Test
Shared
Design completeness and artifact updates early in Sprint
g
p
p
y p
Primary
y
Feature Design/Development that enables Test Automation (hooks, object ID’s, etc)
Shared
Automate-first mindset during Test Case analysis and design
Primary
Unit Test Development and execution (automation preferable)
Primary
Daily Testable builds and Build Verification
Backup
Shared
Notification of changes that could impact automation
Primary
SW Development skill-set within Validation organizations
Primary
Test Automation Design reviews
Shared
Functional Test Development and Execution
Backup
Primary
29
3 week Sprint Lifecycle Example
Week 1
Week 2
Week 3
#1
Demo
Demo
Accept
Accept
Retrospective
Sprint
Planning
Demo
Accept
Demo
Demo
Accept
Accept
Automated
Regression
Sprint
Review
Demo
Accept
Automated
Regression
Automated
Regression
Automated
Regression
Automated
Regression
Manual Regression
15
18. The Lessons of ‘Large’
Courtesy: Gulliver's Travels (2010)
31
The Lessons of ‘Large’
1.
Whole Team approach
2.
Embrace Inspect and Adapt
3.
Co-location is essential
Collaborative space is even better
4.
Establish a Culture of Automation
Across Development and Test
5.
Establish Dev/Test ratio
6.
Focus on Earned Business Value
7.
Scale the Product Owner
16
19. Resources
• Agile Manifesto
• Articles:
– Agile Adoption – Vital Behaviours and Influence Strategies by Steven Rogalsky
g
p
g y
g y
– Scrum Primer – Scrum Foundation
• Books:
– Scaling Software Agility: Best Practices for Large Enterprises – Dean Leffingwell
– Agile Project Management: Creating Innovative Products – Jim Highsmith
– Drive – Daniel Pink
– Agile Testing: A Practical Guide for Testers and Agile teams – Lisa Crispin, Janet Gregory
• Presentations:
– Scaling Software Agility: Agile Portfolio Management – Dean Leffingwell
– Approaches to Software Testing: An Introduction – Scott Barber
33
Questions?
34
17
20. Backup
35
Sprint Planning
• Used to identify the work that the team is going to perform during the sprint
• During Sprint Planning, the scrum team will review the Release Backlog and select stories that could be
p
g p
g priority
candidates for inclusion in the upcoming sprint based on it’s assigned p y
• The team should determine if the story is ready for development by reviewing the narrative and acceptance
criteria and discussing the story with the business owner as necessary.
• Sprint Planning is one of the most important activities in Agile methods
Agile @ Dell Recommendation:
The Sprint Planning session should account for 5% of your sprint
duration.
36
18
21. Retrospective
• During this process, the team inspects every aspect of their work together and looks for improvement
opportunities
• The team should review their velocity trends, the achieved velocity from the most recent sprint and reach
y
y
p
consensus on the velocity that they will commit to for the upcoming sprint.
• The team should look critically, and sometimes painfully, at their sprint results and should remind
themselves:
– The value of Agile is to allow a team to “fail early” – to efficiently identify actions and behaviors that can be improved and to
identify
– To Implement changes that can yield a more efficient and enjoyable process that results in delivering increased business value for
the organization.
• The Retrospective is at the core of the Agile philosophy.
Agile @ Dell Recommendation:
The Retrospective session should account for 5% of your sprint
duration.
37
Product Owner Proxy
Responsibilities
Skill profile of Good PO Proxy
• Understands the customer needs and value of each
story
• Respected by the Product Owner
• Agent of Product Owner
– Is empowered to make decisions
• Develops User Stories
• Reviews & prioritizes backlog
• Available for further story elaboration
• Participates:
• E j collaborating with team
Enjoys ll b i i h
• Understands what is really important to customer
• Ability to balance features, costs, time and quality
for optimal outcome.
• Good negotiation skills
• Understands the technical process and
technologies
– Sprint Planning
– Scrum standups
– Retrospectives
38
19
22. Earned Business Value
• Allows us to track the actual business
value delivered during development
• Requirements are assigned Business Value
points
• Business Value points are earned at
requirement completion
• The release plan projects when
requirements will be completed
The Bottom Line
• EBV gives us a way to track release progress in terms the business understands
• BV gives a finer granularity of prioritization of requirements and aids in scheduling
• Using EBV to talk to executives focuses attention on the value delivered, rather than on defects
outstanding or effort expended
• If something slips, the EBV curve gives a summary view of how important that is, and guides
discussion on what action to take
20