Be a Great Company
Broadsword helps you build better technology products with Process Innovation solutions that help you do what you do, only better.
Why do companies choose Broadsword?
Our solutions leverage proven frameworks such as CMMI, ISO, and Scrum, and feature an integrated mix of appraisals, training, consulting, and workshops to ensure that you receive the value that these frameworks are intended to provide – higher quality, faster delivery, and predictable, repeatable results.
What is CMMI?
We are a CMMI Institute Partner certified to conduct CMMI Appraisals, Training, and Consulting. But that’s only the beginning.
Our services include:
Visit here to learn about what we do. Then contact us to start doing what you do … better.
Click here for our CMMI Books, eBooks, and videos about CMMI.
14 July 2014, 4:21 pm
How much bidirectional requirements traceability is enough to satisfy REQM SP1.4, and do we have to include both vertical and horizontal traceability?
[Dear Readers, our good friend Pat O’Toole, CMMI expert and seasoned consultant, is collaborating with us on a new monthly series of CMMI-related posts, "Just the FAQs." Our goal with these posts is to provide answers to the most frequently asked questions about the CMMI, SCAMPI, engineering strategy and software process improvement. This month Pat talks about bidirectional requirements traceability. Take it away, Pat! ~ the CMMI Appraiser]
Requirements Management (REQM) SP1.4, the practice that focuses on bidirectional traceability of requirements, is like the obnoxious sibling that demands to be the center of everyone's attention, to the detriment of that very special child who is much quieter and certainly much better behaved. In the case of REQM, the well-behaved child is SP1.5 - Ensure Alignment Between Project Work and Requirements. So let’s pause for a moment and give that angelic child the attention she so rightly deserves…
There are essentially two ways for things to get out of alignment with requirements. First, since most of us are human, every once in a while we make mistakes. Perhaps the designs/test cases don't cover a requirement or two, and perhaps they include a design element/test case that isn't directly tied to any of the requirements – thereby representing defects of both omission and commission. Typically such issues are detected through peer reviews or some other verification technique. To rectify such issues, the designs/test cases are simply corrected or otherwise knocked back into alignment with the requirements.
The second case occurs when everything is in glorious alignment with the requirements (cue the harp), but then that blasted requirement change is accepted. Given the change, something now has to be realigned with this updated set of requirements.
The specific goal supported by these sibling practices is, “Requirements are managed and inconsistencies with project plans and work products are identified.” That latter half of this goal statement – the bit in bold – is the “glass half empty” view of the SP1.5 practice statement: “Ensure that project plans and work products remain aligned with the requirements.”
So here’s the punch line – although SP1.4’s expectation of “bidirectional traceability” gets all the attention and, with its discussion of “horizontal and vertical traceability,” more than its share of angst, it is merely the ENABLER of SP1.5 – the “maintain alignment” practice. The thinking is that by establishing such traceability, the engineers are much more likely to cover all the requirements in the first place or, if not, to have their peers use the traceability mechanism to uncover errors of omission and commission when reviewing their work products. In addition, bi-directional traceability enables more efficient analysis of candidate change requests, as well as more effective realignment of any and all affected work products with the new set of requirements. And THAT’s why the model suggests we implement traceability – it’s simply a tool to help us keep things aligned.
And which project work products should be kept aligned with the requirements? Absolutely EVERYTHING – after all, if it weren’t for the requirements we wouldn’t have a project! So the project plan, schedule, issues log, risk list, emails, use cases, prototypes, design elements, code, test cases, deployment plans, etc. etc. should all be targeted at meeting the project requirements. However, although everything the project team does should be focused squarely on satisfying the requirements, not all of the work products they generate will gain efficiencies by being traceable to them. Which ones do? Ah, now THAT depends!
So if you only focus on the obnoxious problem child, you may establish a bi-directional requirements traceability mechanism so intricate and academically beautiful that it warrants a patent, but one that may not best serve its intended purpose. The engineers, who abhor doing non-value-added, administratively burdensome busy work, may begrudgingly use the thing, but their hearts won’t be in it.
On the other hand, if you encourage the engineers to exercise professional judgment by establishing mechanisms that ensure that the key work products stay aligned with the requirements, they’ll get it, they’ll build it and, more importantly, they’ll USE it! I don’t know about you, but I would much rather have smart engineers do smart things to help themselves than to force them to do something they don’t want to do just because some model tells them that it’s good for them – whether they believe it or not. Remember – when it comes to engineers, improvement is best done with them and for them, not to them!
© Copyright 2014: Process Assessment, Consulting & Training and Broadsword Solutions
“Just the FAQs” is written/edited by Pat O’Toole and Jeff Dalton. Please contact the authors at firstname.lastname@example.org and email@example.com to suggest enhancements to their answers, or to provide an alternative response to the question posed. New questions are also welcomed!
2 July 2014, 5:21 pm
Software Process and Measurement Program Features Broadsword President
WATERFORD, MI – Jeff Dalton, President of Broadsword Solutions, revealed how a more resilient approach is needed to meet the challenges facing organizations adopting agile methods. During an interview with Thomas Cagley, host of the Software Process and Measurement Cast (SPaMCAST), Dalton also discussed the importance of values and how frameworks such as the Capability Maturity Model Integration (CMMI) can be used to make agile more resilient.
Dalton said that project teams are increasingly adopting agile, while other parts of the organization are running the business in ways that conflict with agile. In addition, large-scale adopters such as the DoD and Federal government are requiring agile for projects without understanding and embracing agile values, methods and techniques. Dalton says that these large scale adopters are driving change that will be detrimental to the future of agile.
Dalton also discussed the impact of values.
“We are seeing agile values being adopted at the team level. Where they should be adopted is in the C-Suite,” Dalton said. “They should be adopted by CEOs, CIOs, and CTOs in companies, then driven down throughout the organization so that the culture of the company adopts those values.”
Dalton said there is a type mismatch organizationally between agile and process improvement methods.
“Process improvement methods like CMMI, which are operational in nature, are being driven from the C-Suite and not being driven at the lowest part of the organization where the operational activities take place,” Dalton said. “This is adding tons of overhead and tons of unneeded activity. We have to start working with our executive teams to start not on agile, not on CMMI, but on values. Values drive everything in a company.”
About Jeff Dalton
Jeff Dalton 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 President of the Great Lakes Software Process Improvement Network (GL-SPIN). Jeff has been named the Keynote Speaker for the PMI Great Lakes 2013 Symposium. In 2008, Jeff coined the term Process Debt to describe the crushing over-bearing processes too many companies employ to achieve a CMMI rating. He is a recipient of the prestigious 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 in his spare time. You can reach Jeff at firstname.lastname@example.org.
Broadsword is a Process Innovation firm that helps engineering and software companies do what they do, better. You can learn more about Broadsword at www.broadswordsolutions.com
23 June 2014, 8:46 pm
Broadsword Keynote Speakers Offer Critical Insights on Performance Innovation and Process Improvement
Speakers Group helps companies solve performance issues through results-focused presentations and workshops
WATERFORD, MI. June 24, 2014 -- Broadsword, one of North America's leading engineering and software performance innovation firms, has launched the Broadsword Speakers Group to help companies improve performance, build better products and create high performing teams.
Faced with competitive pressures, quality concerns, and significant operational challenges, companies are seeking innovative ideas to improve performance and increase profitability. Broadsword’s speakers meet that need by sharing information and lessons built on years of real-world experience working with clients in software development, design engineering, aerospace, automotive, manufacturing, and state and federal government.
“Teams want practical, useable ideas they can implement right away,” said Jeff Dalton, President of Broadsword Solutions
. “Theory is great, but we share proven approaches built upon evidence-based models that can help a company quickly transform the way they do their work. We help them to do what they do, only better.”
Building on their experience working with clients on performance innovation, process improvement and organizational change, Broadsword keynote speakers tailor their presentations to meet the business goals of each company or organization. They strive to create an entertaining experience that is relevant, timely and actionable.
Frequently requested topics include the following:
Agile Resiliency: How to Scale Software Development with Agile Methods reveals how to strengthen and reinforce Agile values, methods, and techniques in an environment increasingly under pressure to meet the needs of large corporations and the Federal government.
Values-based Engineering: How Real Corporate Values Either Make or Break Your Company explores the mismatch that often occurs between corporate values and operational excellence, and explores how implementing proven architecture tools can solve the issue.
Organizational Change Management: Managing People in an Era of Constant Change reveals the key elements of an organizational change management strategy that will result in long-term, sustainable performance improvement and higher-performing teams.
Dalton leads the roster of Broadsword speakers, and is recognized for his thought leadership in Performance Innovation and Agile software methods. He is President of Broadsword, conference speaker, author, and management consultant with more than twenty-five years of technology and software process improvement experience. He is a certified CMMI SCAMPI Lead Appraiser, Scrum Master, CMMI Instructor, and Scrum product owner.
Broadsword is a Performance Innovation firm and the world-leader in using Agile and Lean methods to drive high performance engineering using Broadsword's AgileCMMI methodology and collaborative consulting and coaching solutions. Broadsword is both a Software Engineering Institute Partner and CMMI Institute Partner. Working with great clients like Boeing, Chrysler, Compuware, L-3 Communications, and others Broadsword's methods have a proven record of success throughout North America.
For more information about the Broadsword Speakers Group, go to