Skip to content

Maintaining an Overview


The article “Maintaining an Overview” by Dr. Peter Hruschka and Dr. Gernot Starke empha­sizes the impor­tance of having a struc­tured overview in software projects to effec­tively manage detailed requirements, suggesting a method to prior­itize archi­tec­turally signif­icant requirements early on.

Read More

Act, Don’t Whine:

In many consulting projects over the last few years, we have seen devel­opment teams complain about two things: that they suffer from a lack of good requirements or that they have not received important requirements or have received them much too late. They then blame requirements engineers, business analysts, or product owners who “didn’t do…

Read More

Stay Up-to-Date with the iSAQB® Newsletter!

Scroll To Top