Agile initiatives always begin with high expectations—accelerate delivery, meet customer needs, and improve software quality. The truth is that many agile projects do not deliver on some or all of these expectations. If you want help to ensure the success of your agile project or to get an agile project back on track, this tutorial is for you. Jeffery Payne discusses the most common causes of agile project failure and how you can avoid these issues—or mitigate their damaging effects. Poor project management, ineffective requirements development, failed communications, software development problems, and (non)agile testing can all contribute to project failure. Jeffery shares practical tips and techniques to identify early warning signs that your agile project might be in trouble and offers suggestions for getting your project back on track. Gain the knowledge you need to guide your organization toward agile project implementations that serve both the business and the stakeholders.
Jeffery Payne
Jeffery Payne is CEO and founder of Coveros, Inc., a software company that builds secure software applications using agile methods. Since its inception in 2008, Coveros has become a market leader in secure agile principles and recognized by Inc. magazine as one of the fastest growing private companies in the country. Prior to founding Coveros, Jeffery was chairman of the board, CEO, and co-founder of Cigital, Inc., a market leader in software security consulting. He has published more than thirty papers on software development and testing, and testified before Congress on issues of national importance, including intellectual property rights, cyber terrorism, and software quality.
Many organizations use the terms quality assurance and software testing interchangeably to describe their testing activities. But true quality assurance is much, much more than testing alone. Quality assurance encompasses a planned set of tasks, activities, and actions used to provide management with information about the quality of software so appropriate business decisions can be made. Jeffery Payne discusses the differences between software testing and quality assurance, examining the typical activities performed during a true quality assurance program. Topics discussed include evaluating software processes, validating software artifacts (requirements, designs, etc.), presenting a quality case to management, and how to start implementing a true quality assurance program. Leave with a working knowledge of quality assurance and a framework for incrementally improving your overall software quality assurance program.
Everywhere we look these days we see the word continuous—continuous delivery, continuous integration, continuous deployment, continuous testing, continuous security, and continuous ______ (fill in the blank). It’s continuous everything! So, what’s happening in our industry? Will a move toward more continuous practices result in better software? Will agile have any long-lasting effect on how software is built, tested, delivered, and maintained? Join Jeffery Payne as he discusses the link between agile and continuous software engineering capabilities. Learn how operating in a continuous manner not only speeds things up but also results in better software quality and security. Discover how the continuous nature of agile is changing our world. Leave with an understanding of what this change means for us as software professionals. Take back knowledge about how we can get more involved in the continuous processes that surround our work.