Saturday, March 25, 2017

Entries for the 'Requirements Process' Category

09

The optimal path to mature requirements practices is often obscured by misinformation. Register now to see how to make significant operational improvement in requirements maturity and select a path based on a strong foundation of research and quantified success.

[Read the rest of this article...]

18

This session provides attendees with hands on techniques for determining the outcome of their projects before the project really gets rolling. This session is about facts, and presents extensive research from IAG’s new Business Analysis Benchmark Study to help business analysts and project managers build a predictive risk assessment model. This session puts the intake and requirements gathering process of the project lifecycle under the microscope to determine what actions Business Analysts and Project Managers can take to more consistently achieve a successful outcome on their projects.

[Read the rest of this article...]

21

 Why should it take months to determine project scope and gather requirements? Register now to look at the underlying problems that impede the collection of business requirements and make projects less successful.

[Read the rest of this article...]

21

 Managing Requirements Operational Excellence is about making significant change in requirements discovery and management performance.
This session is for the business analyst leadership and development executive looking to make long term, systematic improvement to their business analyst organization.

[Read the rest of this article...]

28

Requirements gathering activities should be scheduled by your project plan like any other project related activities. If these activities don't track to the schedule, whether because the schedule isn't feasible or some other reason, it will cause all the dependant activities to slip. Once you've chosen your requirements gathering approach and the stakeholders you'll meet with to gather the requirements, you can schedule the meetings, or interviews, or other methods for soliciting the requirements.

[Read the rest of this article...]

31

A company with poor requirements practices is just asking for over-budget costs and regular failure, according to a new report by IAG Consulting. The report, entitled Business Analysis Benchmark, examined 110 enterprise technology projects at 100 companies to determine just how important project requirements really are.

[Read the rest of this article...]

06

Agile development practices introduced, adopted and extended the XP-originated "User Story" as the primary currency for expressing application requirements within the agile enterprise. The just-in-time application of the user story simplified software development and eliminated the prior waterfall like practices of overly burdensome and overly constraining requirements specifications for agile teams.

However, as powerful as this innovative concept is, the user story by itself does not provide an adequate, nor sufficiently lean, construct for reasoning about investment, system-level requirements and acceptance testing across the larger software enterprises project team, program and portfolio organizational levels.

[Read the rest of this article...]

Copyright 2009-2014 by Modern Analyst Media LLC