Requirements Management - SRM

Monitoring aktuálních informací a webových zdrojů týkajících se "Software Requirements Managementu - SRM". Weblog je součástí informačního portálu AKA-MONITOR, www.akamonitor.cz, spravovaného doc. A. Katolickým. Stránka podporuje službu RSS! Vzhledem k malému počtu českých zdrojů, jsou odkazy směrovány rovněž na stránky v angličtině nebo němčině.

Moje fotka
Jméno:
Místo: Plzeň, Czechia

Internetový publicista provozující AKA-MONITOR ISSN 1804-042X www.akamonitor.cz,.

25.3.07

Agile Requirements Best Practices

Na portálu věnovaném modernímu trendu - "agilnímu modelování" - "Agile Modeling (AM)", zaměřeném na efektivní praktiky pro modelování a dokumentaci, jsem narazil na zajímavé pojednání s názvem: "Agile Requirements Best Practices". Spojení tématu agilní modelování s managementem sw požadavků, slibuje zajímavý zážitek.
Pro představu o zaměření a o jazyku, uvádím alespoň první odstavec textu:
"When you are requirements modeling the critical practice is Active Stakeholder Participation. There are two issues that need to be addressed to enable this practice – availability of project stakeholders to provide requirements and their (and your) willingness to actively model together. My experience is that when a project team doesn’t have adequate access to project stakeholders that this is by choice. You have funding for your project, don’t you? That must have come from some form of project stakeholder, so they clearly exist. Users must also exist, or at least potential users if you’re building a system you intend to provide to the public, so there clearly is someone that you could talk to. Yes, it may be difficult to find these people. Yes, it may be difficult to get them to participate. Deal with it. In the Overcoming Common Requirements Challenges section I discuss several common problems that development teams often face, including not having full access to project stakeholders. My philosophy is that if your project stakeholders are unable or unwilling to participate then that is a clear indication that your project does not have the internal support that it needs to succeed, therefore you should either address the problem or cancel your project to minimize your losses. Failing either of these strategies, you should at least stop claiming that you are taking an AM approach to development (Active Stakeholder Participation is a core practice and therefore is one that must be adopted in order to claim that you are “doing AM”)."
Struktura článku je tato:
- Stakeholders actively participate
- Adopt inclusive models
- Take a breadth-first approach
- Model storm details just in time (JIT)
- Your goal is to implement requirements, not document them
- Create platform independent requirements to a point
- Smaller is better
- Question traceability
- Explain the techniques
- Adopt stakeholder terminology
- Keep it fun
- Obtain management support
- Turn stakeholders into developers
-Treat requirements like a prioritized stack
Adresa, kde najdete nejen článek, ale i řadu cenných odkazů, je: ZDE-ZDE