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.
Email: rick@ipsolutionslaw.com
Website: https://ipsolutionslaw.com/
LinkedIn: linkedin.com/in/rickmartinlaw
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 tcagley@tomcagley.com.
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 – https://bit.ly/3bOK2Vg
Previous Installments
Week 1: Re-read Logistics and Front Matter – https://bit.ly/3mgz9P6
Week 2: A Brief Introduction To Scrum, and Why Scrum Goes Bad – https://bit.ly/37w4Dv9
Week 3: Breaking Bad Scrum with a Value-Driven Approach – http://bit.ly/3stGc9Q
Week 4: The Product Owner – https://bit.ly/3qpKvSn
Week 5: The Product Backlog – http://bit.ly/3cAEk9c
Week 6: The Development Team – http://bit.ly/2OLVAAs
Week 7: Embracing The Scrum Master Role – https://bit.ly/3m0HB5D
Week 8: Management – https://bit.ly/31Kv39l
Week 9: Thinking In Sprints – https://bit.ly/321wXTg
Week 10: Sprint Planning – https://bit.ly/3stWOhx
Week 11: Sprint Backlog – https://bit.ly/3njezit
Week 12 – Reclaiming The Daily Scrum – https://bit.ly/3eNzMgz
Week 13: Deconstructing the Done Product Increment – https://bit.ly/3bedTGc
Week 14: The Sprint Review – https://bit.ly/3huZvgP
Next SPaMCAST
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.
