Software Process And Measurement Cast

SPaMCAST 316 features a return visit from Dr. David Rico. We talked about the cost of quality and Agile. Does Agile impact the cost of quality? The cost of quality is a measure of the time and cost that is required to ensure that what is delivered meets quality standards. Dr. Rico walks us through the evidence that not only does Agile improve customer satisfaction, but it also improves the cost of quality. Dr. Rico has been a technical leader in support of NASA, U.S. Air Force, U.S. Navy, and U.S. Army for over 30 years. He has led numerous projects based on Cloud Computing, Lean Thinking, Agile Methods, SOA, Web Services, Six Sigma, FOSS, ISO 9001, CMMI, Baldrige, TQM, Enterprise Architecture, DoDAF, and DoD 5000. He specializes in IT investment analysis, IT portfolio valuation, and IT enabled change. He has been an international keynote speaker, presented at leading industry conferences, written seven textbooks, published numerous articles, and is a reviewer for multiple systems engineering journals. He is

SPaMCAST 315 features our essay on Scrum Masters.  Scrum Masters are the voice of the process at the team level.  Scrum Masters are a critical member of every Agile team. The team’s need for a Scrum Master is not transitory because they evolve together as a team. In this edition of the Software Process and Measurement Cast we debut a new column.  Gene Hughson brings the wisdom from his Form Follows Function blog to the SPaMCAST.  Gene appeared on SPaMCAST 268 to talk architecture, people and process.  We are glad to have him back on a regular basis.  This first column discusses the idea that quick fixes might not always be the right answer! The essay on Scrum Masters begins: The difference between facilitating and enabling is at the core of the Agile concept of self-organizing and self-managing teams. An effective scrum master should be a facilitator in a well functioning Agile team. However, when there is a breakdown in a self-organizing and self-managing team, sometimes scrum masters become enablers. This m

SPaMCAST 314 features our interview with Janet Gregory and Lisa Crispin.  We discussed their new book More Agile Testing. Testing is core to success in all forms of development.  Agile development and testing are no different. More Agile Testing builds on Gregory and Crispin’s first collaborative effort, the extremely successful Agile Testing to ensure everyone that uses an Agile frameworks delivers the most value possible. The Bios! Janet Gregory is an agile testing coach and process consultant with DragonFire Inc. Janet is the is the co-author with Lisa Crispin of Agile Testing: A Practical Guide for Testers and Agile Teams (Addison-Wesley, 2009), and More Agile Testing: Learning Journeys for the Whole Team (Addison-Wesley 2014). She is also a contributor to 97 Things Every Programmer Should Know. Janet specializes in showing Agile teams how testers can add value in areas beyond critiquing the product; for example, guiding development with business-facing tests. Janet works with teams to transition to Agile

SPaMCAST 313 features our essay on developing an initial backlog.  Developing an initial backlog is an important step to get projects going and moving in the right direction. If a project does not start well, it is hard for it to end well.  We will provide techniques to help you begin well! The essay begins: Many discussions of Agile techniques begin with the assumption that a backlog has magically appeared on the team’s door step. Anyone that has participated in any form of project, whether related to information technology, operations or physical engineering, knows that requirements don’t grow on trees. They need to be developed before a team can start to satisfy those requirements.  There are three primary ways to gather requirements based on how information is elicited. Listen to the rest on the Software Process and Measurement Cast! Call to action! What are the two books that have most influenced you career (business, technical or philosophical)?  Send the titles to spamcastinfo@gmail.com.  What will we

SPaMCAST 312 features our interview with Alex Neginsky.  Alex is a real leader and practitioner in a real company that has really applied Agile.  Alex shares pragmatic advice about to how practice Agile in the real world!   Alex’s bio: Alex Neginsky began his career in the software industry at the age of 16 as a Software Engineer for Ultimate Software. He earned his Bachelor's degree in Computer Science at Florida Atlantic University in 2006. By age 27, Alex obtained his first software patent.  Alex has been at MTech, a division of Newmarket International, since 2011. As the Director of Development he brings 15 years of experience, technical skills, and management capabilities. Alex manages highly skilled software professionals across several teams stationed all over Eastern Europe and the United States. He serves as the liaison between MTech Development and the industry. During his tenure with the MTech division of Newmarket, Alex has been pivotal in the adoption of the complete software development lifecycl

SPaMCAST 311 features our essay on backlog grooming. Backlog grooming is an important technique that can be used in any Agile or Lean methodology. At one point the need for backlog grooming was debated, however most practitioners now find the practice useful. The simplest definition of backlog grooming is the preparation of the user stories or requirements to ensure they are ready to be worked on. The act of grooming and preparation can cover a wide range of specific activities and can be performed at any time. We also have a new installment of Kim Pries’s Software Sensei column.  What is the relationship between the containment of diseases and bad software?  Kim makes the case that the process for dealing both are related. The Essay begins Backlog grooming is an important technique that can be used in any Agile or Lean methodology. At one point the need for backlog grooming was debated, however most practitioners now find the practice useful. The simplest definition of backlog grooming is the preparation of

Software Process and Measurement Cast 310 features our interview with Mike Burrows. This is Mike’s second visit to the Software Process and Measurement Cast.  In this visit we discussed his new book, Kanban from the Inside (Kindle).  The book lays out why Kanban is a management method built on a set of values rather than just a set of techniques. Mike explains why Kanban leads to better outcomes for projects, managers, organizations and customers! Mike is the UK Director and Principal Consultant at David J Anderson and Associates. In a career spanning the aerospace, banking, energy and government sectors, Mike has been a global development manager, IT director and software developer. He speaks regularly at Lean/Kanban-related events in several countries and his book Kanban from the Inside (Kindle)was published in September. Mike’s email is mike@djaa.comTwitter: https://twitter.com/asplake and @KanbanInsideBlog is http://positiveincline.com/index.php/about/UK Kanban conference: http://lkuk.leankanban.com/Kanba

 Software Process and Measurement Cast number 309 features our essay on Agile user acceptance testing. Agile user acceptance testing (AUAT) confirms that the output of a project meets the business’ needs and requirements. The concept of acceptance testing early and often is almost inarguable, whether you are using Agile or any other method. AUAT generates early customer feedback, which increases customer satisfaction and reduces the potential for delivering defects. While implementing an effective and efficient AUAT isn’t always easy it most certainly is possible! The essay begins: The classic definition of a user acceptance test (UAT) is a process that confirms that the output of a project meets the business needs and requirements. UAT in an Agile project generally is more rigorous and timely than the classic end of project UAT found in waterfall projects. In waterfall projects, the UAT is usually the last step in the development process.  The problem with that classic scenario is that significant defects ar

Software Process and Measurement Cast number 308 features our interview with Michael West discussing his book Return on Process.  Process improvement can have a dramatic impact to an organization's bottom line BUT ONLY with careful thought and planning.  Michael West explains that process improvements with real impact are rarely an accident. Michael’s bio . . . Michael West is a life-long practitioner and student of process improvement. He is the co-founder of Natural Systems Process Improvement (Natural SPI), a consultancy specializing in designing, developing, and deploying process systems that enable measurable business performance improvement gains. Mr. West’s process insights and innovations have helped many organizations in various sectors of the economy achieve real process and performance improvement. His process consulting clients include ATK, Autodesk, AVL, BAE, BB&T, Crane Aerospace, DCS, Deloitte, Sandia National Labs, Reliability First, and the US Navy. Mr. West frequently presents and speaks

Software Process and Measurement Cast number 307 features our essay on integration testing and Agile. Integration testing is defined as testing in which components (software and hardware) are combined to confirm that they interact according to expectations and requirements.  Good integration testing is critical to effective development whether you are using Agile techniques or not. Link and pictures noted in the essay: Beer glass logo screen   Application Diagram We also have a new installment from the Software Sensei.  Kim Pries, the Software Sensei, discusses layered process audits and software inspections.  The techniques are a powerful approach to deliver high quality software. Next SPaMCAST 308 features our interview with Michael West author of Return On Process (ROP): Getting Real Performance Results from Process Improvement and more! We had a great discussion about why some process improvements impact the organization’s bottom line and some don’t. Impacting the bottom line is not accident.   Upcoming E

Software Process and Measurement Cast number 306 features our interview with Luis Gonçalves.  We discussed getting rid of performance appraisals.  Luis makes the case that performance appraisals hurt people and companies.  Luis’s Bio . . . Luis Gonçalves is an Agile coach, author, speaker and blogger.Luis has been working in the software industry since 2003, as an Agile practitioner since 2007. He has experience in integrating sequential project phases like localization into an Agile framework and pioneering Agile adoption at different companies and in different contexts.Luis is the co-author of the book, Getting Value Out of Agile Retrospectives. He has a technical background and is Management 3.0 passionate. Mr Gonçalves likes to write and share ideas with the world and is a passionate blogger. Inspiration comes from his professional life and from the books he reads. Follow his blog at  http://lmsgoncalves.com/ Luis asks for SPaMCAST listeners to provide feedback on his new book, Get Rid of Performance Appr

Software Process and Measurement Cast number 305 features our essay on Estimation.  Estimation is a hot bed of controversy. We begin by synchronizing on what we think the word means.  Then, once we have a common vocabulary we can commence with the fisticuffs. In SPaMCAST 305 we will not shy away from a hard discussion. The essay begins: Software project estimation is a conflation of three related but different concepts. The three concepts are budgeting, estimation and planning.  These are typical in a normal commercial organization, however these concepts might be called different things depending your business model.  For example, organizations that sell software services typically develop sales bids instead of budgets.  Once the budget is developed the evolution from budget to estimate and then plan follows a unique path as the project team learns about the project. Next Software Process and Measurement Cast number 306 features our interview with Luis Gonçalves.  We discussed getting rid of performance appr

Software Process and Measurement Cast number 304 features our interview with Jamie Lynn Cooke. Jamie Lynn Cooke is the author of The Power of the Agile Business Analyst. We discussed the definition of an Agile business analyst and what they actually do in Agile projects.  Jamie provides a clear and succinct explanation of the role and huge value of Agile business analysts bring to projects! Jamie Lynn’s Bio:Jamie Lynn Cooke has 24 years of experience as a senior business analyst and solutions consultant, working with more than 130 public and private sector organizations throughout Australia, Canada, and the United States. She is the author of The Power of the Agile Business Analyst: 30 surprising ways a business analyst can add value to your Agile development team, which details how Agile business analysts can increase the relevance, quality and overall business value of Agile projects; Agile Principles Unleashed, a book written specifically to explain Agile in non-technical business terms to managers and exe

Software Process and Measurement Cast number 303 features our essay titled “Topics in Estimation.” This essay is a collection of smaller essays that cover wide range of issues effecting estimation.  Topics include estimation and customer satisfaction, risk and project estimates, estimation frameworks and size and estimation.  Something to help and irritate everyone, we are talking about estimation – what would you expect? We also have a new installment of Kim Pries’s Software Sensei column.  In this installment Kim discusses education as defect prevention.  Do we really believe that education improves productivity, quality and time to market?   Next Software Process and Measurement Cast number 304 will feature our long awaited interview with Jamie Lynn Cooke, author The Power of the Agile Business Analyst. We discussed the definition of an Agile business analyst and what they actually do in Agile projects.  Jamie provides a clear and succinct explanation of the role and value of Agile business analysts. Upcom

Software Process and Measurement Cast number 302 features our interview with Larry Maccherone of Rally Software. We talked about Agile and metrics.  Measuring and challenging the folklore of Agile is a powerful tool for change!  Measurement and Agile in the same sentence really is not an oxymoron. Larry’s Bio: Larry is an industry recognized Agile speaker and thought leader. He is Rally Software's Director of Analytics and Research. Before coming to Rally Software, Larry worked at Carnegie Mellon with the Software Engineering Institute for seven years conducting research on software engineering metrics with a particular focus on reintroducing quantitative insight back into the agile world. He now leads a team at Rally using big data techniques to draw interesting insights and Agile performance metrics, and provide products that allow Rally customers to make better decisions. Larry is an accomplished author and speaker, presenting at major conferences for the lean and agile markets over the last several years,

Software Process and Measurement Cast number 301 features our essay on technical debt. Technical debt is the work not done or the shortcuts taken when delivering a product. We all take shortcuts, but at what cost? The essay begins: Technical debt is a term coined by Ward Cunningham to represent the work not done or the shortcuts taken when delivering a product. In almost every circumstance there are multiple paths than can be taken to deliver a functional product.  For example, when documenting the code you are writing there is a difference between explaining exactly what the code does in detail and being terse and a bit oblique (I can hear the rationalization, “they can just read the code”). The code runs, but if there is ever a problem it will take longer to diagnose the problem. Whether fixing a defect or rewriting the code, if there is a delay caused by figuring out the code, that represents the 'debt' of technical debt.  Technical debt is applied to software, but the phrase can be extended to any deliver

Show 300! Show Zero was published on January 7, 2007. 2,738 days later, we feature our interview with Vasco Duarte. We discussed #NoEstimates, which evokes a great deal of passion.  The interview will embraces that passion and we sort through the noise to get to the core of the idea which is highly useful despite all of the controversy. #NoEstimates asks teams, product owners and leaders to rethink how they predict project performance.  Change is hard but Vasco describes a less painful path to predicting delivery. Vasco’s Bio: Product manager, scrum master, project manager, director, and Agile coach are only some of the roles that Vasco has taken in software development organizations. That experience has been gained by having worked in the software industry since 1997, and being an Agile practitioner since 2004. Vasco has worked in small, medium and large software organizations as an Agile Coach or leader in Agile adoption. He was one of the leaders and catalysts of Agile methods and Agile culture adoption at

SPaMCAST 299 features our essay on systems thinking.  Many process improvement programs falter despite our best efforts because they don't improve the overall performance of IT. The impact of fixing individual processes can easily get lost in the weeds, the impact overtaken by the inertia of the overall systems. Systems thinking is a way to view the world, including organizations, from a broad perspective that includes structures, patterns, and events, rather than simply based on a single event.  The essay begins: In a world made up of interlocking systems, understanding requires defining a set of general principles independent of the system being measured. At a more finite level, such as a company or product, understanding systems is crucial for being effective and efficient.  Many process improvement programs falter when, despite our best efforts, they don't improve the overall performance of IT. More? Listen to SPaMCAST 299! Next week is show 300!  We will feature our interview with Vasco Duarte. We discus

Listen to SPaMCAST 298 SPaMCAST 298 features our interview with Brian Federici.  Brian discussed continuous integration and nearly continuous delivery from a practitioner’s point of view. Continuous integration and delivery are at the heart of fast, better and higher customer satisfaction promised by Agile methods however, in many environments, continuous integration and nearly continuous delivery are still a merely interesting theory.  Brian discussed how these concepts affect how work is delivered. Brian has been programming professionally since 2003, focusing primarily on C# and Web technologies.  He's a big proponent of test-driven and behavior-driven development.  He has contributed to the NuGet open source project as well as created some of his own.  He is also an active member of Agile Philly, Philly .NET, Philly GameWorks, and Philly Application Lifecycle Management groups.  In his free time, he enjoys video games, drumming, tennis, and dodge ball. You can interact with Brian in many different ways!  

SPaMCAST 297 features our essay on IPFUG Function Points. IFPUG Function Points are a measure of the functionality delivered by the project or application being counted based on a set of rules documented in the IFPUG Counting Practices Manual (CPM). The measure of delivered functionality is a proxy for size which can be used in estimating and measuring work. An analogy for function points is the measure of the number of square feet (or square meters) of a house. Next week we will feature our interview with Brian Federici.  We discussed working in an environment with a nearly continuous delivery model from the point of view of a practitioner. Does what sounds good in theory really work when it is implemented? Upcoming Events Upcoming DCG Webinars: July 24 11:30 EDT - The Impact of Cognitive Bias On TeamsCheck these out at www.davidconsultinggroup.com   I will be attending Agile 2014 in Orlando, July 28 through August 1, 2014.  It would be great to get together with SPaMCAST listeners, let me know if you are at