This document discusses how model-based testing can help enhance an agile testing process. It provides an overview of agile principles and popular agile methods like Scrum and XP. It also discusses challenges in testing during each iteration and how model-based testing involves generating test cases from a behavioral model of the system. The document demonstrates modeling the behavior of a FOREX trading application and generating tests to cover new requirements introduced in an iteration. It argues that model-based testing fits well with agile values by facilitating collaboration, responding faster to changes, and increasing test coverage.
Integrating Quality into Portfolio Management Brent Barton
Traditionally, projects are managed based on cost, schedule, and scope. This has lead to poor outcomes, unsustainable development efforts, quality issues, and less than ideal software in terms of value to its users. Our talk will go into how organizations can integrate quality and value considerations into their portfolio management strategies to have a more holistic view leading to less surprises and more valuable outcomes. The talk will go into detail about how Agile plus traditional Earned Value Management (EVM) alongside Managing Software Debt can give a more holistic view of the project portfolio.
Earned Value Management and Agile Tips for Success Brent Barton
As the Department of Defense focuses on "delivering 75% solutions in months [instead of] 100% solutions in years" Agile is finding its way into big, traditionally managed programs. This event http://www.afei.org/events/2A01/Pages/default.aspx specifically addresses Agile in Defense. This presentation was an invitation following a successful meeting at the ADAPT meeting.
Integrating SCRUM with classical Project ManagementJens Hoffmann
SCRUM and PRINCE2 integrated, is a powerfull solution to scale the agile method for large projects. The conventional and mature project management approaches like PRINCE2 or PMI PMBOK are gaining more resillience from this as the become more flexible and adabtible to changing demands and needs.
Integrating Quality into Project Portfolio ManagementChris Sterling
Traditionally, projects are managed based on cost, schedule, and scope. This continues to be insufficient and leads to poor outcomes, unsustainable development efforts, quality issues, and software that may meet requirements but not the expectations of users. This talk will go into how organizations can integrate quality and value considerations into their portfolio management strategies leading to less surprises and more valuable outcomes. The talk will go into detail about how Agile, Lean thinking, and Managing Software Debt can give a more holistic view of the project portfolio.
Integrating Quality into Portfolio Management Brent Barton
Traditionally, projects are managed based on cost, schedule, and scope. This has lead to poor outcomes, unsustainable development efforts, quality issues, and less than ideal software in terms of value to its users. Our talk will go into how organizations can integrate quality and value considerations into their portfolio management strategies to have a more holistic view leading to less surprises and more valuable outcomes. The talk will go into detail about how Agile plus traditional Earned Value Management (EVM) alongside Managing Software Debt can give a more holistic view of the project portfolio.
Earned Value Management and Agile Tips for Success Brent Barton
As the Department of Defense focuses on "delivering 75% solutions in months [instead of] 100% solutions in years" Agile is finding its way into big, traditionally managed programs. This event http://www.afei.org/events/2A01/Pages/default.aspx specifically addresses Agile in Defense. This presentation was an invitation following a successful meeting at the ADAPT meeting.
Integrating SCRUM with classical Project ManagementJens Hoffmann
SCRUM and PRINCE2 integrated, is a powerfull solution to scale the agile method for large projects. The conventional and mature project management approaches like PRINCE2 or PMI PMBOK are gaining more resillience from this as the become more flexible and adabtible to changing demands and needs.
Integrating Quality into Project Portfolio ManagementChris Sterling
Traditionally, projects are managed based on cost, schedule, and scope. This continues to be insufficient and leads to poor outcomes, unsustainable development efforts, quality issues, and software that may meet requirements but not the expectations of users. This talk will go into how organizations can integrate quality and value considerations into their portfolio management strategies leading to less surprises and more valuable outcomes. The talk will go into detail about how Agile, Lean thinking, and Managing Software Debt can give a more holistic view of the project portfolio.
2011 pmo symposium Bridging the Agile-to-PMO Communication GapBrent Barton
Traditional EVM makes no sense in software (and is potentially harmful) because claiming value earned based on intermediate work products--without an assertion of quality--does not provide reasonable forecasts. Agile provides an assertable and inspectable quality. Also, by ordering in terms of highest Business Value and risk considerations along with potentially shippable increments, I believe starts to include notions of value. Still, AgileEVM measures performance against plans (that can be re-baselined every iteration if needed). AgileEVM integrates cost management. Doing it well means not giving up what Agile offers: adaptive planning, quality.
This presentation is from Scrum Gathering 2011 in Seattle, WA, USA. Much of the presentation involved showing tools and techniques outside the slide deck along with exercises that the participants would perform for learning purposes.
Agiles 2009 - An Evolutive Approach From Cmmi Iso - Miguel InsaurraldeAgiles2009
Existen muchos mitos alrededor de Agile vs CMMI/ISO. Muchos de ellos tienen su origen en una mala o inapropiada aplicacion de dichos enfoques mas que en una real diferencia en su escencia. Si bien tienen principios diferentes y hasta alcances distintos, su mision es similar: la calidad integral del producto final, en terminos de funcionalidad y atributos no funcionales, como tambien de optimizacion de costos y tiempos. No es menos cierto que nacieron en contextos y epocas diferentes, pero a pesar de ello se encuentran muchos puntos en comun cuando no complementarios. Segun mi experiencia hemos tenido aciertos y errores en su utilizacion, sobre los que hemos evolucionado en base al aprendizaje continuo. Una de las principales conclusiones es que el mejor enfoque y conjunto de practicas y tecnicas a aplicar en un proyecto depende de cada caso particular, y tenemos que evitar la generalizacion y/o creacion de preceptos excluyentes, definiendo mas bien criterios generales de
Software debt slowly creeps into software assets if left unnoticed and can slow down delivery in ways that seemed faster initially. Fortunately, modern tools, frameworks, and software development approaches help us manage software debt effectively at a reasonable cost to implement. This program will show ways to recognize software debt in five debt areas so that you can start to manage it.
Learn about the 4 Key Steps to Application Modernization with Kevin Brearley Product Management Director, joined with our customer Troy Sheeley Senior Project Manager at CSC. This presentation took place at the Gartner Symposium ITxpo in Orlando on 23rd October 2012.”
“Learn about the 4 Key Steps to Application Modernization from Solutions Director Derek Britton along with our customer Jeroen van der Heijden, Chief Technical Officer at Raet. This presentation took place at the Gartner Symposium ITxpo in Barcelona on 7th November 2012.”
This is a 45 minute presentation I will be delivering at a company-wide meeting to discuss:
* How push-button release was used to help entire enterprise go from 6 month to 1 week release cycles
* How a "No Defect" team policy with ATDD drives greater productivity
QA is dead long live the new QA - Agile Dev and QA Conference IsraelYuval Yeret
So we've gone Agile, we've implemented "Agile Teams". How are organizations dealing with the increased forces of running faster and faster loops from need to delivery? How does it affect how QA people and QA groups look into the future?
As more and more companies are moving to the Cloud, they want their latest, greatest software features to be available to their users as quickly as they are built. However there are several issues blocking them from moving ahead.
One key issue is the massive amount of time it takes for someone to certify that the new feature is indeed working as expected and also to assure that the rest of the features will continuing to work. In spite of this long waiting cycle, we still cannot assure that our software will not have any issues. In fact, many times our assumptions about the user's needs or behavior might itself be wrong. But this long testing cycle only helps us validate that our assumptions works as assumed.
How can we break out of this rut & get thin slices of our features in front of our users to validate our assumptions early?
Most software organizations today suffer from what I call, the "Inverted Testing Pyramid" problem. They spend maximum time and effort manually checking software. Some invest in automation, but mostly building slow, complex, fragile end-to-end GUI test. Very little effort is spent on building a solid foundation of unit & acceptance tests.
This over-investment in end-to-end tests is a slippery slope. Once you start on this path, you end up investing even more time & effort on testing which gives you diminishing returns.
In this session Naresh Jain will explain the key misconceptions that has lead to the inverted testing pyramid approach being massively adopted, main drawbacks of this approach and how to turn your organization around to get the right testing pyramid.
2011 pmo symposium Bridging the Agile-to-PMO Communication GapBrent Barton
Traditional EVM makes no sense in software (and is potentially harmful) because claiming value earned based on intermediate work products--without an assertion of quality--does not provide reasonable forecasts. Agile provides an assertable and inspectable quality. Also, by ordering in terms of highest Business Value and risk considerations along with potentially shippable increments, I believe starts to include notions of value. Still, AgileEVM measures performance against plans (that can be re-baselined every iteration if needed). AgileEVM integrates cost management. Doing it well means not giving up what Agile offers: adaptive planning, quality.
This presentation is from Scrum Gathering 2011 in Seattle, WA, USA. Much of the presentation involved showing tools and techniques outside the slide deck along with exercises that the participants would perform for learning purposes.
Agiles 2009 - An Evolutive Approach From Cmmi Iso - Miguel InsaurraldeAgiles2009
Existen muchos mitos alrededor de Agile vs CMMI/ISO. Muchos de ellos tienen su origen en una mala o inapropiada aplicacion de dichos enfoques mas que en una real diferencia en su escencia. Si bien tienen principios diferentes y hasta alcances distintos, su mision es similar: la calidad integral del producto final, en terminos de funcionalidad y atributos no funcionales, como tambien de optimizacion de costos y tiempos. No es menos cierto que nacieron en contextos y epocas diferentes, pero a pesar de ello se encuentran muchos puntos en comun cuando no complementarios. Segun mi experiencia hemos tenido aciertos y errores en su utilizacion, sobre los que hemos evolucionado en base al aprendizaje continuo. Una de las principales conclusiones es que el mejor enfoque y conjunto de practicas y tecnicas a aplicar en un proyecto depende de cada caso particular, y tenemos que evitar la generalizacion y/o creacion de preceptos excluyentes, definiendo mas bien criterios generales de
Software debt slowly creeps into software assets if left unnoticed and can slow down delivery in ways that seemed faster initially. Fortunately, modern tools, frameworks, and software development approaches help us manage software debt effectively at a reasonable cost to implement. This program will show ways to recognize software debt in five debt areas so that you can start to manage it.
Learn about the 4 Key Steps to Application Modernization with Kevin Brearley Product Management Director, joined with our customer Troy Sheeley Senior Project Manager at CSC. This presentation took place at the Gartner Symposium ITxpo in Orlando on 23rd October 2012.”
“Learn about the 4 Key Steps to Application Modernization from Solutions Director Derek Britton along with our customer Jeroen van der Heijden, Chief Technical Officer at Raet. This presentation took place at the Gartner Symposium ITxpo in Barcelona on 7th November 2012.”
This is a 45 minute presentation I will be delivering at a company-wide meeting to discuss:
* How push-button release was used to help entire enterprise go from 6 month to 1 week release cycles
* How a "No Defect" team policy with ATDD drives greater productivity
QA is dead long live the new QA - Agile Dev and QA Conference IsraelYuval Yeret
So we've gone Agile, we've implemented "Agile Teams". How are organizations dealing with the increased forces of running faster and faster loops from need to delivery? How does it affect how QA people and QA groups look into the future?
As more and more companies are moving to the Cloud, they want their latest, greatest software features to be available to their users as quickly as they are built. However there are several issues blocking them from moving ahead.
One key issue is the massive amount of time it takes for someone to certify that the new feature is indeed working as expected and also to assure that the rest of the features will continuing to work. In spite of this long waiting cycle, we still cannot assure that our software will not have any issues. In fact, many times our assumptions about the user's needs or behavior might itself be wrong. But this long testing cycle only helps us validate that our assumptions works as assumed.
How can we break out of this rut & get thin slices of our features in front of our users to validate our assumptions early?
Most software organizations today suffer from what I call, the "Inverted Testing Pyramid" problem. They spend maximum time and effort manually checking software. Some invest in automation, but mostly building slow, complex, fragile end-to-end GUI test. Very little effort is spent on building a solid foundation of unit & acceptance tests.
This over-investment in end-to-end tests is a slippery slope. Once you start on this path, you end up investing even more time & effort on testing which gives you diminishing returns.
In this session Naresh Jain will explain the key misconceptions that has lead to the inverted testing pyramid approach being massively adopted, main drawbacks of this approach and how to turn your organization around to get the right testing pyramid.
Agile development poses several challenges to effectively testing software. Many myths have become "common wisdom" about how testing is much more difficult, even impossible, in an agile environment. Aricent's software testing experts look at 7 of these myths, and based on their years of experience debunk them.
Sogeti Webinar Effective Test Process Improvement 220709Sogeti Ireland
This webinar presentation briefly covered TPI and TMMi and their usefulness as process assessment frameworks. However, the main thrust of the talk was to present a proven and pragmatic way to do process improvement that gets senior management commitment AND buy-in from project practitioners.
Discusses using the Groovy dynamic language for primarily functional and acceptance testing with a forward looking perspective. Also considers polyglot options. The techniques and lessons learned can be applied to other kinds of testing and are also applicable to similar languages. Drivers and Runners discussed include: Native Groovy, HttpBuilder, HtmlUnitWebTest, Watij, Selenium, WebDriverTellurium, JWebUnit, JUnit, TestNG, Spock, EasyB, JBehave, Cucumber, Robot Framework and Slim
3 Keys to Great Customer Experience When Launching Web and Mobile ApplicationsCompuware APM
Designing a great application is only part of ensuring a great customer experience. Ensuring that the application meets business and user expectations in a way that attracts and keeps customers wanting more, yet protecting and increasing business interests is the key to a great customer experience.
Join guest speaker Margo Visitacion of Forrester Research Inc, and Mark Eshelby of Compuware for this webinar about Designing and Launching Web and Mobile Applications that delight your customers and are good business.
In this webinar learn how:
• Today’s teams must focus on a wider range of requirements to verify in complex environments
–how do web and mobile applications change the customer experience?
• Why application development professionals must use collaborative test design principles and approaches .
• How to approach testing your Web and Mobile Applications focusing on the end user experience.
Similar to Model-Based Testing to Help You Enhance Your Agile Testing Process (20)