Hits for your search: requirement engineering
-
Prioritize and Say No Properly – A First-Hand Report
For [user] the [requirement, benefit, opportunity] is [company/product/service] the [category] the [core benefit]. In contrast to [competition, alternative] is [differentiator]. Once this step was done, the team could use it to define their classes of service and SLA’s. (SLA= Service Level Agreement, i.e. a contractually guaranteed service, e.g. a product is shipped within 24 h).
-
Certified Scrum Master (CSM) or Professional Scrum Master (PSM)? An honest comparison.
The requirements to become a licensed trainer are also similar. However, a CSM training must always be conducted by a licensed trainer of the Scrum Alliance. A “CSM Training” is thus a certain seal of quality for the training. The risk with an apparent “PSM training” is that it is not necessarily an official training.
-
Certified Scrum Product Owner Training (CSPO)
You will experience how to define requirements, plan releases, forecast deadlines, manage budgets and increase return on investment. Participants will receive a range of real-world tips and approaches. InteractiveExperience-based, interactive training with simulations and flipcharts, no slides. AccreditedScrum Alliance accredited trainers who explain real applicable Scrum, not an interpretation.
-
Leading SAFe 6.0 Training (SA)
Requirements, release and test managers or project managers will learn where these roles are found in an agile organization. Contents of the Leading SAFe Training In this training you will learn how a Lean-Agile organization works.
-
A tricky slide about Story Points and Capacity in SAFe® – and how to get it right.
Aligning is an option in SAFe, but not a requirement (“can be”). Also, the algorithm “Find a small story that would take a day to develop […]. Call it a ‘one.’” is “one approach” and not mandatory. All quotes are from the article on Iteration Planning. To get it right, refer to the Iteration Planning article on the SAFe® website.
-
Agile transformation: When can it make sense for companies?
Typical goals are, for example, greater customer centricity and thus higher customer satisfaction, faster development cycles or greater flexibility in adapting to changing requirements. There should be a willingness in the organization to establish an agile mindset and to find its own way in doing so. There are no blueprints that fit all organizations.
-
Chapter 1
This has always enabled me to work well with the various departments and, above all, to come to a common prioritization of the requirements for our product. I'm afraid that my successor won't find it so easy to keep the threads together. I think we need to systematize the issue of stakeholders and prioritization.
-
Chapter 2
The fact that the POs coordinate their requirements is certainly also a criterion. And if the three of them start to act as a committee, then that's an indication that things are going wrong." "That's true, if the decisions take longer than before," Manfred remembers. "I really have to go now. I don't want to be late for the budget meeting. We have to continue next week.