Intellectual property protection impacts almost everyone whether they are aware of it or not.  Trademarks, copyrights, patents, and trade secrets are all part of a wide-ranging discussion of IP protection in the software environment. Rick provides great insight into a rapidly evolving field. 

Rick Martin is the owner and founder of Martin IP Law Group which is based in Evansville, Indiana but serves clients throughout the United States. He is a graduate of the Purdue University School of Industrial Engineering and the Catholic University of America, Columbus School of Law. 

Prior to beginning his career as an Intellectual Property Attorney, Rick worked as a patent examiner at the U.S. Patent & Trademark Office. Rick has obtained hundreds of patents for inventors in a variety of fields, including timing systems, mine safety devices, broadband antennas, RFID, electronics, ranging, oil & gas, semiconductors, and other mechanical and electro-mechanical devices. 

For over 25 years, he has been helping entrepreneurs and businesses protect their ideas, inventions, and identities through patents, trademarks, copyrights, trade secrets, and related contracts, licenses, and agreements.




Re-Read Saturday News 

Chapter 15 in Fixing Your Scrum, Practical Solutions to Common Scrum Problems, by Ryan Ripley and Todd Miller, covers the retrospective. The retrospective, I think, is the most important part of Scrum. Helping it to work well is important. 

Next week we will conclude our re-read with a few closing remarks. Make sure I have your input on what to re-read next by voting in the poll that can be found in the show notes.   Don’t like polls?  Email me your choice at

If you have not bought your copy — what are you waiting for? Fixing Your Scrum: Practical Solutions to Common Scrum Problems 

This Week’s Installment 

Week 15: The Retrospective 

Previous Installments

Week 1: Re-read Logistics and Front Matter 

Week 2: A Brief Introduction To Scrum, and Why Scrum Goes Bad 

Week 3: Breaking Bad Scrum with a Value-Driven Approach 

Week 4: The Product Owner 

Week 5: The Product Backlog 

Week 6: The Development Team 

Week 7: Embracing The Scrum Master Role – 

Week 8: Management 

Week 9:  Thinking In Sprints 

Week 10: Sprint Planning 

Week 11: Sprint Backlog 

Week 12 – Reclaiming The Daily Scrum 

Week 13: Deconstructing the Done Product Increment – 

Week 14: The Sprint Review 


The next Software Process and Measurement Cast will feature a longer essay titled, Work Entry: An Introduction.  This essay brings together a number of concepts to focus on what work entry is and why it is the single most important part of determining whether a team is dependable and predictable. 

We will also have a visit from Jon M Quigley and his Alpha and Omega of Product Development.