| Course Code: |
MQ 416 |
| Course Abstract: |
This course provides the expected savings from application development outsourcing, especially offshore, by reducing misinterpretation of requirements and gaining efficiencies in process. Global teams must learn how to adapt their project methodology to meet the communication needs of global application development. Content in this seminar starts after requirements have been gathered and documented but ready for refining and validating so they can be communicated to global resources who are ready to design and develop the solution. Compliant with BABOK® Version 2.
|
| Audience: |
This course is designed for business analysts, project managers, designers, architects, engineers, RFP and proposal writers, and application team members responsible for communicating or managing requirements to global or vendor resources.
|
| Duration: |
2 days |
| Learning Outcomes: |
Upon completion of this course, the participant will be able to:
> Gain agreement on communication protocols and processes to promote understanding across cultures
> Assess and select appropriate requirements communication techniques to match the needs of offshore resources for appropriate level of detail and methods
> Uncover and validate hidden assumptions impacting requirements with offshore resources
> Refine requirements to be more quantifiable and measurable assuring more effective validation
> Plan and conduct mock virtual reviews
> Determine the extent of traceability and change control needed based on project needs and your relationship with global resources
|
| Course Topics: |
1. Frameworks for Level Setting
An overview of various frameworks and models are introduced and discussed to provide the foundation for future workshop activities.
a. Business Analysis (BABOK®)
b. Project Management (PMBOK®)
c. Software Development Life Cycle
d. Offshore Maturity
2. Gaining Team Agreement on the Requirements Process
Process consistency is critical to improving requirement communication. The Requirements Management Plan will be introduced.
a. Providing Project Context to Offshore Resources
b. Requirements Management Plan for Requirement Process Consistency
c. Team Orientation Package for Building the Right Team Climate
3. Hints and Tips to Avoid Requirement Misinterpretation
What influences how well translation occurs? As organizations have more cross-organizational, externally sourced and global teams, the gaps between assumptions become greater and harder to manage.
a. Requirements Communication Planning
b. Uncovering Hidden Assumptions
c. Cross-cultural Impacts to Communicating Requirements
d. Natural Language and Level of Detail Challenges
e. Core Skills for Better Reviews with Your Offshore Resources
4. Validation Tools and Techniques
Sometimes we get stuck in our silos – we live and breathe the System Development Lifecycle role we are in. But this poses many challenges when we handoff deliverables over a virtual wall (or ocean). What happens to these requirements?
a. Documenting and Organizing for the Offshore Audience
b. Technology Impacts to Communicating Virtually
c. Tools for Communication (e.g. Use Cases , Decision Trees and Models)
d. Reviews with Offshore Liaisons, Project Managers, Liaisons, Designers and Developers
e. Communicating Requirement Risks in an Offshore Staffing Model
5. Offsite Team Involvement in Tracing Requirements and Managing Change
How do we ensure requirements are addressed throughout the lifecycle – especially when the work is being done offshore? How are changes to requirements handled?
a. Working the Traceability & Change Process with Offshore Teams
b. Alignment to Previous Agreements (Business Case, Project Charter, Statement of Work, etc) and Managing Expectations
c. Tool Features Most Useful for Requirements Collaboration
|
| Prerequisites: |
None |