Category: Agile & Scrum

Agile in general, and Scrum in particular, relies for success on self-organizing teams. The eleventh of the principles behind the Agile Manifesto states that “the best architectures, requirements, and designs emerge from self-organizing teams”(1). Empowering the team is one of the seven principles of Lean. One of the central Scrum patterns is ‘Stable Teams’ (2). […]

If business analysts were just people who”analyze businesses” they would have, at most, a passive role that wouldn’t contribute to their organizations’ achieving their goals. The real role of the business analyst is a far more active one and provides the essential link between the organization’s goals and its IT projects. Wikipedia defines four kinds […]

Fortunately for the organizations they work for,  development teams are smart enough not to build the original project’s design — which is why we have Scrum and Agile. But, even with Scrum, good estimating may be the least important thing you have to do: Adopting Scrum, Kanban, or any Agile methodology means that you have […]

Project Management Institute published the sixth edition of the PMBOK® Guide back in September 2017. As such, the Project Management Professional PMP® certification exam was updated to comply with the new release of the guide on March 26, 2018. While there have been significant changes to the guide, which you can read about on the […]

“Requirements engineering” was supposed to ensure that development teams delivered applications that users wanted. That didn’t happen (as the process of requirements engineering itself demonstrated). The answer to giving users what they want turns out to be getting rid of requirements altogether. Requirements exist because everyone recognizes that users aren’t developers. On that understanding, requirements […]