Software Process And Measurement Cast

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

SPaMCAST 296 features our interview with Jeff Dalton we talked about Agile and resiliency. If Agile is resilient it will be able spring back into shape after being bent or compressed by the pressures of development and support.  In the conversation Jeff and I discussed whether Agile was resilient and how frameworks like the CMMI can be used to make Agile more resilient. Jeff is Broadsword’s President, Certified Lead Appraiser, CMMI Instructor, ScrumMaster and author of “agileCMMI,” Broadsword’s leading methodology for incremental and iterative process improvement.  He is Chairman of the CMMI Institute’s Partner Advisory Board and former President of the Great Lakes Software Process Improvement Network (GL-SPIN).  He is a recipient of the Software Engineering Institute’s SEI Member Award for Outstanding Representative for his work uniting the Agile and CMMI communities together through his popular blog “Ask the CMMI Appraiser.”  He holds degrees in Music and Computer Science and builds experimental airplanes i

SPaMCAST 295 features our essay on Test Driven Development (TDD). TDD is an approach to development in which you write a test that proves the piece of work you are working on, and then write the code required to pass the test. You then refactor that code to eliminate duplication and any overlap, then repeat until all of the work is completed. Philosophically, Agile practitioners see TDD as a tool either to improve requirements and design (specification) or to improve the quality of the code.  This is similar to the distinction between verification (are you doing the right thing) and validation (are you doing the thing right). We also have a new entry from the Software Sensei, Kim Pries. Kim addresses cognitive load theory.  Cognitive load theory helps explain how learning and change occur at personnel, team and organizational levels. Next week we will feature our interview with Jeff Dalton. Jeff and I talked about making Agile resilient.  Jeff posits that the CMMI can be used to strengthen and reinforce Agile

SPaMCAST 294 features our interview with Sean Robson. We discussed his book, Agile%20SAP: Introducing flexibility, transparency and speed to SAP implementations" target="_blank">Agile SAP: Introducing flexibility, transparency and speed to SAP implementations. SAP and Agile, some say it can’t be done and they would just be wrong. Sean’s bio reads:Sean Robson, MBA, PMP, CSM, has been working with SAP software since 1998.  He started as an ABAP Developer then moved into configuring the Enterprise Asset Management module.  From there he transitioned to Business Warehouse and Portal support and later consulting where he worked as team lead, test manager and project manager. A Project Management Professional and Certified ScrumMaster, with wide consulting and industry experience, Sean has managed a variety of SAP project types and sizes. He has worked on projects in several industries throughout North America, including manufacturing, utilities, insurance, health care, aerospace and defense, and the public sector.

SPaMCAST 293 features our essay on the Test Maturity Model Integration (TMMi). The TMMi is a maturity model focused on improving both the process and practice of testing! The TMMi covers the entire testing environment not just typical dynamic testing. The essay begins: “All models are wrong, but some are useful.”  - George E. P. Box Information Technology (IT) has many useful models for addressing the complexity of developing, delivering and running software.  Well known models include the Capability Maturity Model Integration (CMMI®), the Information Technology Infrastructure Library (ITIL®) and the Test Maturity Model Integration (TMMi®) to name a few. The TMMi delivers a framework to help practitioners and IT executives understand and improve the quality of the products they deliver through better testing.To listen to the rest listen of the essay on the Software Process and Measurement Cast 293. Thanks for the feedback on shortening the introduction of the cast this week. Please keep your feedback coming.

Listen to the Software Process and Measurement Cast 292. SPaMCAST 292 features our interview with Dr. Ginger Levin. Dr. Levin and I discussed her book, Implementing Program Management: Templates and Forms. Dr Levin and her co-author Allen Green wrote their go-to reference for program practitioners, colleges, universities, and those sitting for the PgMP. Ginger provides great advice for program managers who are interested in consistently delivering value to their clients. Note the audio is not perfect this week however the content is great. I hope you can stay with the interview! Dr. Ginger Levin is a Senior Consultant and Educator in project management with over 45 years of experience. Her specialty areas are portfolio management, program management, the PMO, metrics, and maturity assessments. She is a PMP, PgMP (second in the world), and an OPM3 Certified Professional. She presents regularly at PMI Conferences and conducts numerous seminars on various topics. She is the editor, author or co-author of 20 book

Listen to the Software Process and Measurement Cast 291. SPaMCAST 291 features our essay on splitting user stories. User stories are a powerful tool used by many Agile teams to conceptualize the value they will deliver. Generally when stories are captured they can range from granular units of work that can be accomplished in a day to gargantuan features that will require multiple sprints to complete (epics). Epics are very difficult to work with therefore all Agile teams need techniques for splitting user stories into smaller units of work. We also have another of Steve Tendons great Tame The Flow columns. Steve continues to discuss constraints, bottleneck, lean and hyper-productivity! I have shortened the introduction of the cast this week. I would like your feedback. Get in touch with us anytime or leave a comment here on the blog. Help support the SPaMCAST by reviewing and rating it on iTunes. It helps people find the cast. Like us on Facebook while you’re at it. Next week we will feature our interview wit

Listen to the Software Process and Measurement Cast 290. SPaMCAST 290 features our interview with Jan Beaver, author of The Agile Team Handbook. Jan’s book provides team members with the resources needed not only to become Agile but to practice Agile. Jan Beaver is a Ph.D. educator with over 25 years of experience in the software industry. His experience covers the gamut of management, development, QA, and technical writing. His first practical exposure to Scrum was a dramatic eye-opening experience that for the first time demonstrated that there really was a better way not just to develop software, but a better way to work in general. Jan is an expert Agile trainer and coach who has worked with a wide variety of companies in an equally wide variety of industries including telecommunications, medical, insurance, financial, media, utilities, and smart-grid energy. He specializes in bringing Scrum and broader Agile and Lean principles and practices to teams, helping them to become effective, productive, and sel

Listen to the Software Process and Measurement Cast 289. SPaMCAST 289 features our essay on sprint planning.  The essay begins: It is often said that well begun is half done. In other words a good start contributes to a good finish (at least according to Mary Poppins). In Agile projects sprint planning is an important first step towards delivering value effectively. The planning process provides teams with an understanding of what needs to be delivered in the next increment of time and provides a platform for deciding on the approach they will take based on the up-to-date knowledge they developed during the previous sprint. Well started might not be the whole battle but it certainly makes the rest easier. Listen to the rest of the essay on the SPaMcast 289. Also on the SPaMCAST 289 Kim Pries is back with his “The Software Sensei” column. In this installment Kim’s essay is titled Schedule Cycles.  In the essay Kim talks about tasks and scheduling. I have shortened the introduction of the cast this week. I woul

Listen to the Software Process and Measurement Cast 288. SPaMCAST 288 features our interview with Susan Atkinson on Agile contracts, governance and trust.  Quite a set of topics that get at the heart of why governance of Agile projects requires different tools than we use today. Susan Atkinson is a Consultant Solicitor at Keystone Law. She is a commercial lawyer, focusing on IT, outsourcing, e-commerce, intellectual property and payment services. She has over 15 years of legal experience, and has typically worked on high-value, complex commercial contracts, primarily in the technology, financial services and public sector, and often in an international context. Email:   susan.atkinson@keystonelaw.co.uk Twitter: satkinson42 Get in touch with us anytime or leave a comment here on the blog. Help support the SPaMCAST by reviewing and rating it on iTunes. It helps people find the cast. Like us on Facebook while you’re at it. Next week we will feature our essay on sprint planning. If you don’t start a sprint well y

Listen to the Software Process and Measurement Cast 287.  SPaMCAST 287 features our essay on Scrum. Scrum is the nearly ubiquitous project management process that has become the face of Agile to many people. The essay begins: When most people think of Agile, they really mean Scrum.  Scrum is a fairly simple framework whose origin is attributed to Jeff Sutherland and Ken Schwaber. There are numerous overviews of the history and evolutions of the framework; those at Scrum.org and Scrumalliance.org (where my CSM certification comes from) are two good ones.  The framework is simple. In its basic form it is comprised of three roles, five events and four deliverables. We also have the next installment of Steve Tendon’s column, Tame the Flow.  Steve revisits constraints and bottlenecks. Get in touch with us anytime or leave a comment here on the blog. Help support the SPaMCAST by reviewing and rating it on iTunes. It helps people find the cast. Like us on Facebook while you’re at it. Next week we will feature our in

Listen to the Software Process and Measurement Cast 286. SPaMCAST 286 features our interview with Brian Wernham, author of Agile Project Management for Government. Agile government does not have to be an oxymoron. Brian Wernham has more than 30 years of experience in adaptive change program leadership.  He is an independent consultant and works in both the public and private sector.  He has extensive international experience in the USA, UK, Canada, Hong Kong, Germany and offshore development in Bangalore. By the time that the term ‘Agile leadership’ was first coined, Brian had already been successfully leading iterative, adaptive projects for over 10 years on both sides of the Atlantic.  He works as a hands-on program director and has real-world implementation expertise together with a comprehensive understanding of the related international research.  He has consulted for major strategic international organizations such as Deloitte, PwC, Gartner Group, the National Audit Office in London and Seer Technologie

Listen to the Software Process and Measurement Cast 285. SPaMCAST 285 features a compilation of frequently asked questions of a consulting kind.  Working as a traveling consultant, podcaster and blogger provides me with a fabulous mix of experiences. Meeting new people and getting to participate in a wide range of real life experiences is mind expanding and invigorating. Many of the questions that I have been asked during a client engagement, on the blog or in response to a podcast have similar themes. Since most of the answers were provided in one-on-one interactions I have compiled a few of the questions to share. If these questions spark more questions I promise to circle back and add to the FAQ list! The SPaMCAST 285 also features Kim Pries’s column, The Software Sensei. In this edition, Kim tackles the concept of failure mode and effects. Get in touch with us anytime or leave a comment here on the blog. Help support the SPaMCAST by reviewing and rating it on iTunes. It helps people find the cast. Like us

Listen to the Software Process and Measurement Cast 284. SPaMCAST 284 features our interview with Evan Leybourn, author of Directing the Agile Organization. We had a wide-ranging discussion on Agile business management. Agile is not just for IT anymore! Evan’s Bio Evan is an experienced leader, coach and published author in the developing field of Agile Business Management; applying the successful concepts and practices from the Lean and Agile movements to corporate management. Evan has a passion for building effective and productive organizations, filled with actively engaged and committed staff while ensuring high-levels of customer satisfaction. Evan's experiences when holding executive and board positions in both private industry and government has driven his passion for lean business management. His background in Agile Project Management and Business Intelligence informed his understanding of the need for evidence-based decision making and quantitative analysis, to measure corporate success. As well as w