Log in

goodpods headphones icon

To access all our features

Open the Goodpods app
Close icon
Software Process and Measurement Cast - SPaMCAST 409 - Team Structure, QA Presentations, Eliciting Requirements

SPaMCAST 409 - Team Structure, QA Presentations, Eliciting Requirements

09/04/16 • 48 min

Software Process and Measurement Cast
Special Note - SPAMCAST 409 was due to be posted last week, but bad things happened to my main computer and my backup decided to air-gap itself from the Internet. That said, #409 is going up a week later so the Re-read Saturday news is a week out of date. This week we talk about Chapters 22 and 23. I have declared that last weekend was a very stressful vacation from posting. Now the show goes on! In Software Process and Measurement Cast 409, we feature our essay on advice I recently provided to a listener to the podcast on whether a team is really one or two teams. While the essay is a result of answering a friend’s question, the ideas in the essay can be applied when you are building any sort of team. Our second column this week features a visit to Jeremy Berriault’s QA Corner. Jeremy and I discussed how QA should communicate with other leaders in the organization. In the third and final column, Jon M. Quigley begins a three-part arc on requirements in “The Alpha-Omega of Product Development.” This week on discusses the elicitation of requirements. Re-Read Saturday News This week we continue our re-read of ’s , Second Edition with a discussion of Chapters 20 and 21. Chapter 20 is a discussion of applying XP. The short version is that there is no one perfect way to apply XP, which dovetails nicely with Chapter 21 which addresses the concept of purity and certification. IF there is no one perfect way to apply XP, how can there be an absolute litmus test for XP purity? Use the link to X in the show notes when you buy your copy to read along to support both the blog and podcast. Visit the Software Process and Measurement Blog (www.tcagley.wordpress.com) to catch up on past installments of Re-Read Saturday. Next we are going to read . This will be a new book for me, therefore an initial read, not a re-read! Steven Adams suggested the book and it has been on my list for a few years. Click the link (), buy a copy, and in a few weeks we will begin to read the book together. Next SPaMCAST In the next Software Process and Measurement Cast, we will feature our interview of Jessica Long. Jessica and I discussed storytelling. Storytelling is useful in all types of organizations for both projects and as a tool in organizational transformations. Jessica and I will both be presenting on using stories at the Agile Philly, Agile Tour 2016 on October 10th. Shameless Ad for my book! co-authored by Murali Chematuri and myself and published by J. Ross Publishing. We have received unsolicited reviews like the following: “This book will prove that software projects should not be a tedious process, for you or your team.” Support SPaMCAST by buying the book nglish and Chinese.
plus icon
bookmark
Special Note - SPAMCAST 409 was due to be posted last week, but bad things happened to my main computer and my backup decided to air-gap itself from the Internet. That said, #409 is going up a week later so the Re-read Saturday news is a week out of date. This week we talk about Chapters 22 and 23. I have declared that last weekend was a very stressful vacation from posting. Now the show goes on! In Software Process and Measurement Cast 409, we feature our essay on advice I recently provided to a listener to the podcast on whether a team is really one or two teams. While the essay is a result of answering a friend’s question, the ideas in the essay can be applied when you are building any sort of team. Our second column this week features a visit to Jeremy Berriault’s QA Corner. Jeremy and I discussed how QA should communicate with other leaders in the organization. In the third and final column, Jon M. Quigley begins a three-part arc on requirements in “The Alpha-Omega of Product Development.” This week on discusses the elicitation of requirements. Re-Read Saturday News This week we continue our re-read of ’s , Second Edition with a discussion of Chapters 20 and 21. Chapter 20 is a discussion of applying XP. The short version is that there is no one perfect way to apply XP, which dovetails nicely with Chapter 21 which addresses the concept of purity and certification. IF there is no one perfect way to apply XP, how can there be an absolute litmus test for XP purity? Use the link to X in the show notes when you buy your copy to read along to support both the blog and podcast. Visit the Software Process and Measurement Blog (www.tcagley.wordpress.com) to catch up on past installments of Re-Read Saturday. Next we are going to read . This will be a new book for me, therefore an initial read, not a re-read! Steven Adams suggested the book and it has been on my list for a few years. Click the link (), buy a copy, and in a few weeks we will begin to read the book together. Next SPaMCAST In the next Software Process and Measurement Cast, we will feature our interview of Jessica Long. Jessica and I discussed storytelling. Storytelling is useful in all types of organizations for both projects and as a tool in organizational transformations. Jessica and I will both be presenting on using stories at the Agile Philly, Agile Tour 2016 on October 10th. Shameless Ad for my book! co-authored by Murali Chematuri and myself and published by J. Ross Publishing. We have received unsolicited reviews like the following: “This book will prove that software projects should not be a tedious process, for you or your team.” Support SPaMCAST by buying the book nglish and Chinese.

Previous Episode

undefined - SPaMCAST 408 - Kupe Kupersmith, Business Analysis and Agile

SPaMCAST 408 - Kupe Kupersmith, Business Analysis and Agile

The Software Process and Measurement Cast 408 features our interview with Kupe Kupersmith. Kupe and I discussed the role of the business analyst in today’s dynamic environment. It is critical to defining and facilitating the delivery of value. Weighty topics, but we also had a bit of fun. “Kupe” Kupersmith, President, B2T Training, possesses over 18 years of experience in software systems development. He has served as the lead Business Analyst and Project Manager on projects in the energy, television and sports management and marketing industries. Additionally, he serves as a mentor for business analysis professionals. Kupe is the co-author of Business Analysis for Dummies, a Certified Business Analysis Professional (CBAP®) and a former IIBA® Board Member. Kupe is a requested speaker and has presented at many conferences around the world. Being a trained improvisational comedian, Kupe is sure to make you laugh while you’re learning. For a feel for Kupe’s view on business analysis topics check out his blog on . Kupe is a connector and has a goal in life to meet everyone! Contact Information https://www.b2ttraining.com/ Re-Read Saturday News This week we continue our re-read of ’s , Second Edition with a discussion of . Chapters 18 and 19 provide a view into two very different management philosophies that shaped software development in general and have had a major impact on XP. Chapter 18 discusses Taylorism and scientific management; a management knows best view of the world. Chapter 19 talks about the Toyota Production System, which puts significant power back in the hands of the practitioner to deliver a quality product. Use the link to X in the show notes when you buy your copy to read along to support both the blog and podcast. Visit the Software Process and Measurement Blog (www.tcagley.wordpress.com) to catch up on past installments of Re-Read Saturday. Next, we are going to read by Jossey-Bass. This will be a new book for me, therefore, an initial read, not a re-read! Steven Adams suggested the book and it has been on my list for a few years! Click the link (), buy a copy and in a few weeks, we will begin to read the book together. Next SPaMCAST In the next Software Process and Measurement Cast, we will feature essay on whether a team is really one or two teams. While the essay is a result of answering a friend’s question, the ideas in the essay can be applied when you are building any sort of team. We will also have columns from Jeremy Berriault’s QA Corner and Jon M. Quigley’ column, “The Alpha-Omega of Product Development.” Shameless Ad for my book! co-authored by Murali Chematuri and myself and published by J. Ross Publishing. We have received unsolicited reviews like the following: “This book will prove that software projects should not be a tedious process, for you or your team.” Support SPaMCAST by buying the book nglish and Chinese.

Next Episode

undefined - SPaMCAST 410 - Jessica Long, Storytelling in Agile

SPaMCAST 410 - Jessica Long, Storytelling in Agile

In Software Process and Measurement Cast 410, we feature our interview with Jessica Long. Jessica and I discussed storytelling. I find that storytelling is a useful tool to help individuals, teams, and organizations. Projects can use stories to generate user stories and as a tool in retrospectives. Stories are also a tool in generating a vision of the future in organizational transformations. Those are just a few of the multitude of uses for storytelling in changing how value is delivered! Jessica and I will both be presenting on using stories at the Agile Philly, Agile Tour 2016 on October 10th. Jessica’s bio:Jess Long is an Agile Coach, a writer, a speaker and a mother with a passion for driving meaningful stories across multiple iterations in all facets of life. Transforming Corporate America and living to tell about it is no small feat. She keeps some level of sanity by finding humor in otherwise absurd situations. Twitter: Blog: LinkedIn: Re-Read Saturday News This week we reach the penultimate week in our re-read of ’s , Second Edition with a discussion of Chapters 24 and 25. Chapter 24 discusses the value and power in communities. Chapter 25 is Beck’s conclusion and reflection on the book: XP is about people! Next week we'll wrap this re-read up and get ready to to read by Patrick Lencioni (published by Jossey-Bass). This will be a new book for me, therefore an initial read, not a re-read! Steven Adams suggested the book and it has been on my list for a few years. Click the link (), buy a copy, and in a few weeks we will begin to read the book together. Next SPaMCAST The Software Process and Measurement Cast 411 will be a big show featuring our thoughts on servant leadership. In SPaMCAST 411 we will have a visit from the Kim Pries, the Software Sensei. We will have more from Steve Tendon on the Tame The Flow: Hyper-Productive Knowledge-Work Performance, The TameFlow Approach and Its Application to Scrum and Kanban published J Ross (). And anchoring the cast will be Gene Hughson with an entry from his Form Follows Function Blog. Shameless Ad for my book! co-authored by Murali Chematuri and myself and published by J. Ross Publishing. We have received unsolicited reviews like the following: “This book will prove that software projects should not be a tedious process, for you or your team.” Support SPaMCAST by buying the book nglish and Chinese.

Episode Comments

Generate a badge

Get a badge for your website that links back to this episode

Select type & size
Open dropdown icon
share badge image

<a href="https://goodpods.com/podcasts/software-process-and-measurement-cast-117188/spamcast-409-team-structure-qa-presentations-eliciting-requirements-5988089"> <img src="https://storage.googleapis.com/goodpods-images-bucket/badges/generic-badge-1.svg" alt="listen to spamcast 409 - team structure, qa presentations, eliciting requirements on goodpods" style="width: 225px" /> </a>

Copy