MB5-858, SURE STEP 2010

1) A prospect customer asks your sales person to prove to support specific industry requirements. Ensure due
diligence achieved. What do you recommend? 2 applied
A. A joint application design or prototyping session where the software values tables are configured or populated in
the session
B. A system test or demonstration of exactly how the software will be used at the customer site; participants must
have an expectation that the project is still in desing and feedback on key points is needed.
C. A demonstration of the software and processes and realistic Customer Bussiness Scenarios that include
representative customer data
D. A scripted and well prepared proof of concept
RESPUESTA: C, D

2) Which three customer benefits and objectives are achieved by conducting a Fit Gap and Solution Blueprint
during the pre-sales process? (3)
A) Increased understanding of the “Degree of fit”
B) Increased visibility into the business and IT requirements and how they will be addressed
C) Increased understanding of the effort required to configure and customize the project solution
D) Increased understandin of the proposal

Respuesta: A, B, C

3) You are about to roll-out a new MSD implementation with no custom and very limited data migration. Which
activities should you plan for in Deployment phase? (2)
A. Conduct User Training
B. Finalize Configuration/Setup
C. Transition to Support
D. Go-live
RESPUESTA: A, D

4) In a rapid approach, how detailed scope documents should be?

For rapid implementation projects, develop a detailed scope document to help make sure that the proposed solution is a good fit for
the customer.
Because a rapid implementation bypasses many of the detailed design activities, there is less opportunity for the customer to learn
about the solution and its associated functionality. This makes a detailed and clear scope statement that is especially important in
rapid implementation projects.

5) The prospect customer wants a business software system, but has no formal requirements. What do you
advise your sales representative?
Diagnostic Phase
During the high-level diagnostic activities, the project team can determine that a more detailed analysis of business processes is
required, a proof of concept of the solution, or an assessment of the customer infrastructure is desired. In such situations, the
Microsoft Dynamics Sure Step Diagnostic phase provides Decision Accelerator (DA) offerings to help the customer with their due
diligence process; you can start by creating a new proposal for this activity.
The Diagnostic phase consists of the following activities:
• Diagnostic preparation:
- Microsoft Dynamics Solutions
- Industry Solutions
- Cross Industry/Horizontal Solutions
• Optional Decision Accelerator offerings:
- Requirements and process review
- Upgrade Assessment
- Fit Gap and solution blueprint
- Architecture Assessment
- Scoping Assessment
- Proof of Concept
- Business Case
• Proposal Generation
• Final Licensing and Services Agreement
• Project Mobilization

Microsoft Dynamic Solutions

This activity introduces the suite of Microsoft Dynamics products as comprehensive business management solutions including end-
to-end, industry specific functionality. The Microsoft line of business (LOB) management Microsoft Official Training Materials for
Microsoft Dynamics ® solutions provide Enterprise Resource Planning (ERP) and Customer Relationship Management (CRM)
capabilities, to help customers automate their unique business processes for the core Microsoft Dynamics applications:
MB5-858, SURE STEP 2010

• Microsoft Dynamics® AX • Microsoft Dynamics® CRM • Microsoft Dynamics® GP • Microsoft Dynamics® NAV
• Microsoft Dynamics® SL
This activity consists of the following tasks:
• Conduct meetings with the customer to understand:
- The business requirements (if the Requirements and Process Review DA and Fit Gap and Solution Blueprint DAs were
executed, the output of that will be reviewed by the team).
- How Microsoft Dynamics will support the business.
• Analyze key data points.
• Create a formal recommendation for the customer's production deployment infrastructure and hardware requirements.
• Review the recommendation with the client and incorporate input.
The key benefits gained by performing this activity are:
• An understanding of the infrastructure required and the associated costs.
• Assurance that the solutions will scale to meet the client's needs.

6) You are responsible for implementing a Microsoft Dynamics solution. Your company’s Sales Manager has a
signed proposal and has made all project information available to you. You notice that infrastructure was
discussed during the pre-sales activities. What are the next steps related to infrastructure proposed in the
sure step infrastructure cross-phase?
A) Gather functional and no functional requirements and create an infrastructure design document.
B) Install the testing and production environments. This need to be done when testing and production environments are
needed at the customer site.
C) Install the appropriate Microsoft Dynamics Core Product, including required hotfixes and rollups
D) Sure Step does not recommend subsequent steps that are related to the infrastructure domain.

Respuesta: C

7) Your team started a pilot roll-out scenario to implement and deploy MD. The customer continually adjusts the
solution and the project stuck in analysis phase. How can you ensure this project move forward?
A. Adhere to a clear and strict timeline
B. Make change request for every adjustment that the customer make
C. Start new budget negotitations for the extra analysis time spend
D. Make extra analysys resources available to this project
RESPUESTA: A

8) You are preparing a proposal to leverage info already been gathered in pre-sales activities in the diagnostic
phase. Which documents contains information that you should include in your proposal? (2)
a. Project charter x
b. Statement of Work
c. Solution design documents
d. High level project plan x

9) What is the first customer requirement that you shoud verify before starting an upgrade assestment?
a) Whether the upgrade from the customer’s current implementation version to the targeted version of Microsoft Dynamics is
supported
b) Whether there are additional business requirements that must be accounted for
c) Whether customizations were implemented in the current version and how well these are documented
d) Whether the customer wants a technical or major upgrade

Respuesta: A

10) Your company's Sales Manager approaches you with an opportunity for selling a Microsoft Dynamics?
business solution. You are responsible for quickly finalizing the sale of the solution. Which one of the following
provides guidance to help close the sale and provide a structured due-diligence process?
a. Optimization offering
b. Industry playbook
c. Desition accelerator x
d. Project initiation and planning

11) You need to transfer knowledge of MD to customer resources. You also need to train people who will be
using and maintaining the system after go-live. Which sure step cross phase provides info about this
dependencies?
MB5-858, SURE STEP 2010

a. Training cross phase x

b. Communication cross phase
c. Deployment cross phase
d. Quality and test cross phase
Microsoft Dynamics Sure Step has nine key cross phase processes, which are further grouped into three areas.
The Organization cross phase processes is: • Program Management • Training • Business Process Analysis
The Solution cross phase processes is: • Requirements and Configuration • Custom Coding • Quality and Testing
The Technology cross phase processes is: • Infrastructure • Integration and Interfaces • Data Migration

12) Your customer wants to ensure their business software does not contain undocumented code. What can you
do to ensure your team will not deliver undocumented code?
A. Explain that this demand complies with your company’s strategy, and state that developers must produce documented
code that is easily read and understood.
B. Invite your customer to work with your development team to create code development standards.
C. Share requirements and design documents from previous projects to demonstrate that documentation is a priority in your
company.
D. List this demand as a formal project requirement.
RESPUESTA: B

13) Your team has gathered relevant project details by means of pre-sales activities and high level requirements
gatherings, including workshops, demonstrations, and interview sessions. All relevant information was
documented thorugh this activities. You need to centralize this information in one document that will be used
to authorize the project start. This document will outline the overall goals and objectives, define the
interactions of all project participants, list the approved scope, document assumptions and risk and provide
high level project schedule and approach. Which document do you create?
14)
a. Functional Requirements Document
b. Project charter x
c. Final licence agreement
d. Scoping assessment report

15) You are creating a Project Charter. Which information should you include in this document? Choose the3 that
apply.
A. Information about in-scope and out-of-scope areas.
B. Project approach and governance that describe the approach, key milestones, timeline, deliverables, and key stakeholders.
C. The proposed solution and estimated fees that describe what needs to be implemented and the related cost analysis.
D. Business and project objectives that describe the desired output and effect for the customer organization.
Answer: A, B, D

16) Your team needs to implement a Microsoft Dynamics solution for a large enterprise business that hascomplex
business requirements and four globally distributed sites. Although each site has unique business needs, the
company wants to implement a uniform solution across all sites. Which implementation approach does Sure
Step typically recommend?

A. The Enterprise Project Type with a Single Site Build approach

B. The Enterprise Project Type with a Multi Site Core Build approach
C. The Agile Project Type with an iterative, incremental process for developing Microsoft Dynamics
solutions
D. The Standard Project Type
RESPUESTA: B

17) During conversations with the customer in the early sales stage, you discussed the current availability of
compliant hardware and infrastructure at the customer site. You also learned that your customer has doubts
about the infrastructure being ready for a new system, and is concerned about the level of infrastructure
changes that may be required. What should you do?
A. Reassure the customer that your company infrastructure specialists will be handling all infrastructure issues during the
deployment phase.
B. Document this as a risk to the project and advise the customer that extra budget will be needed to resolve these issues.
MB5-858, SURE STEP 2010

C. Propose to execute an architecture assessment.

D. Focus on the quantifiable business value and investment and show the direct and indirect benefits that a Microsoft
Dynamics implementation will create.
Answer: C

18) You need to map requirements in the Fit Gap Analysis worksheet to appropiatly categorize to help scope the
level of effort required. Which of the following categorizations provide the most insights from a project scoping
and cost analysis perspective?
A. Fit, Gap
B. Finance, Sales and Marketing, Purchase, Warehouse, Manufacturing, Service, Marketing, Customer service
C. Critical, Non critical, Important, Optional, Out of scope
D. Standard feature, Configuration, Workflow, Customization, ISV solution, Other
RESPUESTA: D

19) You collaborate with the solution sales team to strategize how to execute a Business Case Assessment.
Which customer benefits do you realize when you execute a Bus. Case Assess.? (2)
A. Estimates on Return On Investment (ROI)
B. A detailed project plan
C. Total cost of ownership (TCO)
D. Bussines process re-ingeneering
RESPUESTA: A, C

20) You are a consultant for a company. You need to review the scope of the implementation process. Which of
the following activities are within the scope of the Requirements and Process Review? Choose the 3 that
apply.
A. Analyze the customer business processes against those in Microsoft Dynamics and highlight any process gaps.
B. Identify the customer required integrations to identify those that do not fit the Microsoft Dynamics integration
recommendations.
C. Generate detailed functional and technical specifications.
D. Review any additional Technical requirements, or IS/IT strategies, defined by the customer.
Answer: A, B, D

21) You are an implantation consultant in an IT company. The management team has decided to implement a
Microsoft Dynamics product. You need to conduct the Fit Gap and Solution Blueprint assessment. Which of
the following tasks are within the scope of the Fit Gap and Solution Blueprint? Choose the 3 that apply

a. Estimate the labor required to configure and customize each requirement

b. Create detailed “To-be” process maps
c. Create a prioritized list of requirements
d. Review requirements against current system
Respuesta: A, C, D

22) Which of the following are pre-conditions for Requirements and Process Review Desition Accelerator? (2)
a. A qualified opportunity for selling a business solution exists
b. Customer Mission & Goals for implementation
c. Results from the Fit Gap and Solution blue print are available
d. Scoping assessment has been completed and results are available
RESPUESTA: A,B

23) Select the most appropriate descriptions of Business Proc. Analysis as defined by Sure Step Proc. Analysis
cross phase? (2)
Purpose
Business Process Analysis provides the activities and process model templates required to craft the future state business processes upon which
the solution will be built.

Description
MB5-858, SURE STEP 2010

Business Process Analysis begins with workshops designed to explore the current state processes, improve efficiencies, suggest
automations/workarounds and design the future state processes. The workshops use process model templates modeled on the standard system
functionality to provide users with an understanding of the baseline system.
Customers may have documented current state processes and it is important to use these when available in the workshops to level set
expectations.
The future state processes are documented as an output from these workshops and these processes form the basis of requirements gathering,
design, training guides and deployment. These flows are important to the customer as they help the key users understand the end to end
scenarios in the system, which in turn helps in the development of training guides and user acceptance test scenarios.
In the Design and Development phases, the Business Process Analysis activities involve reviewing and updating the documented future state
business process flows.

24) You are planning a project and find that stakeholders often have varying objectives
andrequirements.This makes it difficult for you to summarize a plan in a way that all objectives will
be identified or known inadvance. Your customer communicates that they expect their business priorities to
change. You are certainthat this will be a single site implementation requiring specific features and
complex customizations. Whichimplementation approach is suitable for the project?

a. Standard Project Type

b. Agile Project Project Type
c. Enterprise Project Type
d. Rapid Project Project Type
RESPUESTA: B

25) To close the sales process, you need document that defines formal services agreements and outlines
engagement with enough detail to make desition. Which document can the sales team use to support
implementation proposal?
a. Statement of Work x
b. Project charter
c. Project plan
d. Microsoft Dynamics pricelist

26) You are planning for a project that does not contain customizations and that will be implemented with an
accelerated approach. How should you plan to migrate data?
Project type: Rapid
Purpose
The purpose of Data Migration involves the analysis of external data sources, mapping of these data sources, design of data load
scripts, and final execution of the data loads into the production environment to enable the solution deployment. It also includes the
analysis of requirements and creation of the Master Data Management process.
--------------------------------------------------------------------------------
Description
It is very important to define the master data elements and gain consensus on their meaning and usage with the customer. The
Data Entity and related Taxonomy includes the master data elements, their definitions, and how they will be used in the new
solution. Master Data Management is another important factor in an implementation. Data owners need to be identified and the
processes of how, where, and by whom data should be maintained and managed after go-live need to be defined and put in place
at the onset of the implementation. These activities are included in Organization Change Management (OCM) because they play an
important role in ensuring accuracy of data and understanding of data across the organization and because they drive successful
user adoption of the solution.
Most Microsoft Dynamics implementations will involve some level of data migration. Data Migration is crucial to implementation
success. It is highly recommended to start planning for data migration early in the implementation project. Without well-planned,
tested, and validated data migration processes, new solutions can fail because legacy components introduce risks that were never
accounted for during planning. It is also important to gain customer commitment for allocating appropriate resources to work with the
consulting team on data mapping and defining the necessary data conversions.
The analysis of data migration involves identifying the source systems and the overall data requirements for each of these source
systems.
The design of data migration involves mapping the source system fields to the destination fields and designing the transformation
that needs to happen between the systems. The design is captured in the Data Design document that feeds into the Solution
Design.
Data Migration development involves the construction of the data migration and transformation scripts that load data from the
source systems into the configured solution. The data migration development culminates with the Data Acceptance Test (DAT)
activity performed in the Development phase. During DAT, the customer not only verifies the data migrated but also validates that
the data can be queried, reported upon, and transacted upon.
In the Deployment phase, data migration processes are used to load data into the system and user acceptance test environment.
This provides another opportunity to validate the processes. Just prior to go-live, the final data migration of all required, existing
production data will be performed along with a final data validation.
--------------------------------------------------------------------------------
MB5-858, SURE STEP 2010

Pre-conditions
Project Kickoff

The design of data migration involves mapping the source system fields to the destination fields and designing the transformation
that needs to happen between the systems. The design is captured in the Data Design document that feeds into the Solution
Design.
Data Migration development involves the construction of the data migration and transformation scripts that load data from the
source systems into the configured solution. The data migration development culminates with the Data Acceptance Test (DAT)
activity performed in the Development phase. During DAT, the customer not only verifies the data migrated but also validates that
the data can be queried, reported upon, and transacted upon.
In the Deployment phase, data migration processes are used to load data into the system and user acceptance test environment.
This provides another opportunity to validate the processes. Just prior to go-live, the final data migration of all required, existing
production data will be performed along with a final data validation.

27) You are working on an Upgrade project type. Business requirements include implementing new product
features and new customizations. You need to define your approach. Which approach is recommended to
Microsoft Dynamics upgrade projects?
a. The Upgrade project type for functional updates
b. The Upgrade project type for technical updates
c. The Rapid project type approach, including an Upgrade assessment
d. The Agile project type executed by means of Sprints
Respuesta: A

28) After completing the diagnostic assessment, you have the following project data: There are at least 50 users,
one ISV solution is included, additional business process workflow mapping is required, an estimate od
250hrs of customization and complex data migration is needed, the implementation is planned for one site.
Which implementation approaches are recommended by Sure Step? Choose 2 that apply

a. The Rapid project type

b. The Standard project type
c. The Enterprise project type
d. The Agile project type

Respuesta: B, D

29) Using sure step requirements and configuration cross phase. When should you begin your configurations
activities?
a. Design

Requirements and Configuration

Purpose
To capture the functional requirements for the deployment of the Microsoft Dynamics™ solution and any ISV solution(s), and to
design and configure the Microsoft Dynamics™ solution and ISV solution(s) based on the identified business requirements.

Description
During the Analysis phase, gathering and documenting the customer’s business requirements is the most important set of activities
that must be undertaken when implementing Microsoft Dynamics™. These requirements are documented in the Functional
Requirements Document (FRD) which is an input to the Fit Gap Workshop. The Fit Gap Workshop produces the Fit Gap
Spreadsheet which is used to determine the business requirements that are a “Fit” for either the Microsoft Dynamics™ or the ISV(s)
solutions, and the ones that are “Gaps’ that will need customization.
In the Design phase, the Application Consultant will work hand in hand with the appropriate Key User to begin the design and
configuration of the Microsoft Dynamics™ solution and ISV solution(s). This will provide the Key User with reinforcement on the
training received on the applications during Core Team Training. The Functional Design Document will capture all configurations
settings and is a key deliverable in the Design phase. The Functional Design Document becomes the document to control the
system configurations. The Key User will also provide the business scenario to properly test the selected design and configuration.
These business scenarios will be documented in the Process Test Scenarios for use in the corresponding activity of the Quality and
Testing cross phase.

30) As a program manager in a complex blended engagement with several partners and ISV. Reliable and
optimized performance is business critical. What should you do? (1 ó 2….)

a. Optimization offering + performance review before go-live in deployment phase (si es 1 es esta)
MB5-858, SURE STEP 2010

b. Optimization offering + design review as soon as design documents are available

Optimization Offerings
Purpose
Optimization offerings are designed to help reduce risk and improve customer satisfaction for complex blended engagements that
include consultants from several partners and ISV’s. The Optimization Offerings provide:
- Functional design guidance for reviewing the proposed design for business and industry solution fit and functionality,
- Technical design guidance for reviewing the proposed technical design for performance, scalability, integration with other
systems and third party software, and
- Proactive quality management with access to expert technology specialists at appropriate checkpoints in the Sure Step
implementation to mitigate integration risk across the complete technology stack

31) You need to review the benefits of a scoping assessment whit a customer. Which benefits of this assessment
might you discuss? (2)

The purpose of the Scoping Assessment is to more fully understand the customer's requirements. Based on this information,
determine which customizations are within the scope of the project, and recommend how those customizations can be
implemented.

Purpose
To work together with the Solution Sales team to further analyze Customer requirements and Fit Gap and Solution Blueprint
findings, and use them as a basis for recommending an approach for the implementation scope, schedule, cost, and resource
allocation.

Description
The Scoping Assessment is an important activity in the Solution stage of the Opportunity Management process within the Microsoft
Solution Selling Process (MSSP). It traditionally follows a Fit Gap and Solution Blueprint activity and may also occur alongside an
Architecture Assessment. The aim of the Scoping Assessment is to understand the requirements of the Customer in sufficient detail
to determine the bounds of an implementation and to outline how to implement the recommended requirements.

The recommended approach will detail how to implement Microsoft Dynamics in an efficient manner while reducing risk and keeping
costs to a minimum. To achieve this, the Assessment team will:

Analyze the Customer requirements to gain an insight on the scope of the project.
Analyze the results from any other diagnostic service offerings that have been completed.
Analyze inherent constraints in the processes to understand the logical way things are done.
Impose constraints on processes that are based on the Microsoft Dynamics approach to similar processes.

The Scoping Assessment should result in a detailed report consisting of several documents in which an overall recommendation is
made about how the project should proceed. The deliverables include documents providing an implementation cost model, resource
plan, high-level implementation plan, and organization and role breakdowns. Additionally, alternative options may be provided
where elements of the implementation are re-sequenced or broken down into more manageable components.
The report is presented along with a presentation where the main points of the Scoping Assessments findings are reviewed and
approved by the Customer.

32) You selected the Standard Project Type as the most appropriate approach for successful
implementation. Your team is engaged in the Analysis phase and they finished gathering the business
requirements after conducting the Detailed Business Process Analysis. Which activity should the team
perform next?

A. Identify and document gaps between the business solution and the customer requirements based on a Fit Gap
Analysis.
B. Begin System Configuration and ISV Solution Setup.
C. Educate the Customer’s Core Implementation team by means of a Solution Overview training.
D. Start making technical and functional designs in the correct Sure Step Design documents.
RESPUESTA: A

33) Your company is preparing a proposal for a large and complex implementation that will require significant
customizations in an enterprise organization. One of the elements that you plan to address is testing and
creating a test plan. When is the best time to create a high level test plan that includes the general standards
MB5-858, SURE STEP 2010

and procedures that must be followed when conducting software testing and validation?

a. During the beginning of the deployment phase

b. After design specifications are finalized
c. During the custom code activity
d. During project scoping and planning in the Analysis phase
Respuesta: D

34) There is uncertity about mayority of requirements, significant gap between a large set of requirements, your
project team is not familiar with customer industry, and your customer is not familiar with projects
implementation and business software. Which contract type do you recommend?

a. Variable en el análisis y fijo luego

35) There is multiple ways to manage project documents. Which option allows you to collaborate more effectively
and efficiently? (2)

a. Creating diagnostic offerings on a share point site X

b. Creating a project type on a shared server location X
c. Storing documents off-line in hard drive
d. Printed copies

Sharing Microsoft Dynamics Sure Step Projects

To work efficiently with Microsoft Dynamics Sure Step, all members of the project team will require access to at least some of the
project files so that they can make updates as the project progresses. Make the relevant projects available by sharing the project
repository.

Specify the Project Repository Location

A project repository is a location for storing all the files related to a particular project. It is possible to have as many project
repositories as required. For example, a repository can be defined for a set of related projects for the same customer, since it can
be used in a phased implementation. Alternatively, a repository can be defined on a shared location, such as a network drive or
SharePoint, so that members of project teams can access the project documents.

Managing Microsoft Dynamics Sure Step Projects Using SharePoint

Microsoft SharePoint can be used as a document repository to share documents and collaborate on projects within Microsoft
Dynamics Sure Step.
Microsoft SharePoint provides document management capabilities to:
• Store, organize, and locate documents
• Ensure the consistency of documents
• Help protect documents from unauthorized use or access
• Ensure consistent business processes (workflows) for how document are handled

36) With a Standard project type approach. In which phase you plan to start configuring Microsoft Dynamics
applications?
a. Analysis
b. Design x
c. Development
d. Deployment

37) With an Agile type approach. How can you be able to quickly change the direction of solution development to
adapt to changed business needs?
Purpose
The Agile project type represents a flexible and collaborative approach to implementing Microsoft Dynamics Solutions at a single
site requiring specific features and moderate-to-complex customizations.
MB5-858, SURE STEP 2010

Description
The Agile Project Type is associated with an iterative, incremental process for developing Microsoft Dynamics Solutions. This
Project Type gives customers greater control over the final solution because they can quickly change the direction of solution
development and implementation from one sprint cycle to the next. This means that they are better placed to respond to their
businesses needs as development of the solution progresses.
This Project type can be attractive to customers, but it does come with its own set of risks and potential problems that must be
carefully explained to a customer before embarking on this implementation approach. This project type requires clear guidance from
the customer and strong management from the implementation team. The frequency and intensity of communication associated
with an Agile Project type is normally very high, resulting in a solution that reflects the customer’s business needs clearly.
Additionally, because of the dynamic nature of the project approach, documentation is kept to a minimum throughout the project and
is delivered with a barely-good-enough approach during requirement design.

The Agile Project Type is typically used in implementation projects where one or more of the following circumstances exist:
Customer requirements are not fully defined or known up front.
Customer requires implementation to be flexible to accommodate changing business priorities.
Customer focus is on the delivery of solution and does not require complete documentation.
Customer-specific features are required.
Moderate-to-complex customizations are required.
Independent software vendor (ISV) solutions are included.
Simple-to-moderate infrastructure is involved.
Customer-specific integrations or interfaces to third-party systems are required.
Simple-to-complex data migration is involved.
Small-to-medium number of users will use the solution.

38) Which skills are essential to key user profile? (2)

Soft Skills
Clear verbal communicator
Fast learner of new tools and software
Ability to think abstractly
Strong analytic skills
Functional/Technical Skills
Basic understanding of business systems
Basic understanding of project and methodology
Strong knowledge about the existing business processes and future requirements
Skilled in problem solving and analyzing business information
Ability to describe business processes

39) After kick off meeting with the customer the team members requested several changes to some activities.
Should you adjust the schedule?
Manage Change Requests
Change requests are required to document requirements, design, and development changes that occur during the course of the
project and alter the agreed upon scope which is the baseline for the project.
Typically, the Application Consultants will gather information indicating scope changes during their activities, including the detailed
business process analysis and fit gap analysis.
The Change Request form is a document to capture the change requested and provide an analysis of the change and the impacts
of that change. Additionally, the project manager can use the Change Control Request Log to manage the status and impact of all
change requests.

Review and Approve Change Requests

Upon completion of the change request documentation, the Project Manager will review the Change Request with the impacted
project team members to incorporate any feedback the team members provide.
Then a review session with the customer will be scheduled to describe the change requests and their impacts to the resources,
schedule, and costs. Upon review of the Change Request form, the customer will approve or reject the change. The Project
Manager will then finalize this information in the project plan and inform the team members of the new schedule and resources, if
applicable.

40) With a complex Enterprise project, you need to ensure strict QA control. What should you do? (2)
Quality Management
Purpose
Quality management ensures a certain level of quality for the project deliverables and for project management. Activities addressing
quality issues include defining processes, procedures, standards and policies as required to satisfy project stakeholder needs.

Description
An important element of project quality management is to turn stakeholder expectations for quality into requirements. The results
from high level business process analysis, risk analysis and analysis of the various project stakeholders provides the base to
MB5-858, SURE STEP 2010

develop a quality management plan that will be used during project execution to assure, control and improve the quality up to the
required and balanced quality level.
Quality assurance is the set of systematically planned activities to provide confidence the deliverables and services of the project
will fulfill the defined requirements for quality. Quality assurance events are scheduled early and across all project phases to detect
issues and improve the project performance early in the project lifecycle.
Quality control is an ongoing process during project execution that controls the acceptance of project indicators and project results.
The process leads to analyzing and reducing failures and improves quality as required.

The quality management discipline supports the project management team in following similar goals. Examples are below:
-Customer satisfaction
-Plan, design and build in quality instead of just focusing on inspecting the quality.
-Prevent mistakes instead of correct mistakes as an outcome of later inspections.
-Manage the project team for active participation and to provide the resources needed to be successful.
-Avoid overworking the project team and the resulting negative consequences like increased employee attrition, unfounded
errors or rework.
-Avoid meeting project schedule objectives by rushing project work and creating less qualified results.
-Using the plan-do-check-act cycle for continuous quality improvement during the project lifecycle.

41) Como copiar de un proyecto a otro? RESPUESTA: Clone

42) The development consultants are reviewing the design security and identifying additional security
requirements. What are they doing?
Create Technical Design Document
The purpose of the Technical Design Document is for the developers to document the methods and code that will be generated to
meet the corresponding business requirement. The Technical Design Document (TDD) details each system modification or
enhancement included in the proposed solution. A TDD is created for each corresponding FDD - Gap.
This activity consists of the following tasks:
• Create the TDD
-Document specific user interface, business and data layer components required to deliver each proposed system modification.
-Review the design security.
-Identify additional security requirements.

43) How should you describe a formal project status report to customer? (2)
Project Status Reporting
Project Status Reporting provides the customer with a weekly summary of the project consisting of the accomplishments, decisions,
planned work, risks, and issues.
A status report is a document prepared by the Project Manager on a weekly basis using the information provided through the
consultant status reports and the updated project plan.
The status report depicts the following information:
• Overall health status of the project
• Tasks accomplished this week
• Decisions made
• Tasks planned for next week
• Issues and risks
• Vacation schedules
• Forecast/actual hours by consultant
The status report is first reviewed with the project team through an internal weekly team status meeting and then presented to the
customer per the agreed upon timeline.
Project team members provide their level of status reports a day before the reports need to be consolidated at a project or program
level by the Program Manager.

44) While conducting design activities; in which document should you record this configuration setting?
Design Phase
Deliverables for new implementations
Core Team Training
Functional Design Documents (FDDs) for Fits (Configurations)
Functional Design Documents (FDDs) for Gaps (Customizations)
FDDs for Requirements indentified as Gaps in Standard Solution
FDDs for Integration and Interface Requirements
FDDs for Data Migration Requirements
Technical Design Documents (TDDs)
Solution Design Document (SDD)
MB5-858, SURE STEP 2010

45) You plan a meeting at the end of the analysis phase (health project, key deliverable completed, issues and
risk) this meeting will be the sign off of the analysis phase. Which sure step document do you prepare?
Project Status Reporting
Project Status Reporting provides the customer with a weekly summary of the project consisting of the accomplishments, decisions,
planned work, risks, and issues.
A status report is a document prepared by the Project Manager on a weekly basis using the information provided through the
consultant status reports and the updated project plan.
The status report depicts the following information:
• Overall health status of the project
• Tasks accomplished this week
• Decisions made
• Tasks planned for next week
• Issues and risks
• Vacation schedules
• Forecast/actual hours by consultant

The status report is first reviewed with the project team through an internal weekly team status meeting and then presented to the
customer per the agreed upon timeline.
Project team members provide their level of status reports a day before the reports need to be consolidated at a project or program
level by the Program Manager.

46) Detailed business process analysis is conducted. You need to document your findings in a key customer
facing deliverable. Which document do you use?

♦ Functional Requirements Document

Detailed Business Process Analysis
In Microsoft Dynamics Sure Step detailed business process analysis is conducted by means of organizing workshops with the
customer.
With the implementation of an ERP solution, organizational change management efforts are generally involved to varying extents
based on the size of the organization and complexity of the implementation. It is important that these anticipated changes are
incorporated in the business process analysis tasks through the identification of the 'as is' as well as the 'to be' processes.
The Detailed Business Process Analysis Workshops define these processes and identify where specific functionality of the new
system will be used. At the same time the workshops identify the gaps and overlaps between these to be and as is processes.
The following highlight the key steps in Detailed Business Process Analysis:
• Define Target Processes (To Be)
• Map Existing Processes (As Is)
• Conduct Business Process Gap Analysis

Gathering and documenting customer's business requirements is a critical path activity that is executed in the Analysis phase of the
Microsoft Dynamics implementation. The process involves a series of Business Requirements workshops conducted with the key
users, business process owners, and subject matter experts (SMEs) for the customer as well as a mapping of these processes to
the 'to-be' processes identified in the ERP solution. The purpose of these workshops is to collect the customer requirements that are
being documented in the Functional Requirements Document (FRD).
If high level functional requirements are captured during the Diagnostic phase, those requirements will be an input into this activity.
The end result of this activity is a clearly documented list of customer requirements in the FRD.
The FRD in turn becomes an input to the Fit Gap Analysis activity. While the FRD captures what needs to be accomplished, the Fit
Gap Spreadsheet captures how those requirements are met.

47) Standard approach. The technical designs are completed and wants to begin development early. What should
you do?
a. Start earlier
b. Don’t start earlier + verify status of test scripts and non production environment X?
c. Don’t start earlier + make technical designs for reqs that earlier were categorized as changes
d. Determine if go-live can be accelerated and update project schedule accordingly

48) You need to provide business decision makers with a document that defines the proposed solutions and
capabilities being enabled by the solution. What should you do?
Proof of Concept: this tool is designed to gain management support and confidence in the solution. A Microsoft Dynamics ERP
solution is configured in the client's test system around certain critical requirements and demonstrated to their decision makers in a
conference room setting to validate requirements.

Solution Design Document

MB5-858, SURE STEP 2010

The purpose of the Solution Design Document (SDD) is to allow the Business Decision Makers and other stakeholders to obtain a
clear view of the proposed solution flow. As such, the SDD provides the overall solution description in business language, and
includes the capabilities being enabled by the solution.

49) Which actions should you take if you are concerned that users might not be able to bridge the gap between
business processes and business systems? (2)

a. Identify this as a risk and document in the Project Risk Register X?

b. Discuss with customer and advise to select key users X?
c. Advise application consultants to start making change request for this potencial issues
d. Advise application consultants to identify this as an issue and update issue list accotdingly
If resources are assigned to the project and it seems they do not meet the requirements of the role, go back to the manager of the
resource to clarify the responsibilities the person will need to handle. Assigning too many responsibilities to an individual team
member might hinder the project and the person’s career.

50) You consider training the customer’s core implementation team before starts business processes analysis.
How is the goal of this training different from training in the upcoming phases?
Purpose
To ensure that the Customer’s Core Implementation team and other Stakeholders understand the Microsoft Dynamics solution’s
“out-of-the-box” standardized functionality and flow prior to executing Business Requirements workshops.
--------------------------------------------------------------------------------
Description
The goal of this exercise is to educate the Customer’s Core Implementation team, key users, and/or other Stakeholders who will act
as, or on behalf of, process owners and who are to be involved in the various requirements gathering activities.
From an Organizational Change Management perspective, a demonstration of standard functionality and standard solution flows is
especially important because this is the first step toward creating awareness and acceptance for the new solution among users. In
particular, it gives an opportunity to demonstrate that it is possible to execute existing processes in a slightly different sequence or
manner, yet still achieve the same or more optimum results. In order for this exercise to gain full effect and drive maximum
awareness, it is highly recommended that the Business Process owners (or similar people) from the Customer’s organization host
these workshops. They will need to help identify the target audience and preferably distribute the invitations.
The goal of the Solution Overview is different from the Design Phase “Core Team Training” and Deployment Phase User Training
because it focuses on the Dynamics Solutions standard flows without any consideration of customizations or configurations. Design
Phase Core Team Training is narrowed down and conducted after the Fit Gap analysis, and is thus based on the scoped solution.
Deployment Phase customer solution-specific user training is delivered in preparation for go-live. It is useful for the customer to
understand the differences between the training activities across the various phases when scheduling resources to participate in the
Solution Overview.

51) Implementation at single site, analysis phase complete and technical consultants are defining and
documenting how to implement business requirements. Which activities to execute at this stage? (2)

a. Create deployment plan

b. Create knowledge transfer plan X?
c. Develop communication strategy plan
d. Finalize and obtain sign-off of the technical architecture design X?

For new implementation projects, the Design phase builds on the previous Analysis phase by acting on the deliverables that result from the
requirements workshops conducted for each cross phase. The specific goals of the Design phase include, but are not limited to:

Core team training, including any independent software vendor (ISV) solutions, to begin the transfer of knowledge to the customer.
Configuration of the Microsoft Dynamics solution, including any ISV solution, to satisfy those requirements identified as a “Fit” in the Fit Gap
spreadsheet.
Documentation of the “Fits—Configurations” in the Functional Design Document (FDD).
Functional design specifications in the FDD for each system modification, custom processing, custom report, or integration noted as a “Gap”
in the Fit Gap spreadsheet.
Functional design specifications and mapping for Integration and Interfaces in the FDD, and development of Integration and Interfaces plan.
Functional design specifications and mapping for data migration in the FDD, and development of a Data Migration plan.
Technical Design Documents for the “Gaps” based on the Functional designs approved by the customer.
Creation of the Solution Design Document, which provides the overall solution description in business language, and includes the capabilities
being enabled by the solution, in order for the business decision makers and other stakeholders to obtain a clear view of the proposed
solution flow.
Presentation of estimates to the customer for the proposed modifications, integrations, and data migration programs.
Customer sign-off on the overall implementation design, specific modification designs, data migration design, and estimates for all the above-
mentioned activities.
MB5-858, SURE STEP 2010

Risk management continues to play an important role in the management of the project. Risks should be confirmed and new risks identified on a
weekly basis to properly create mitigation plans. The project schedule is updated accordingly. In addition, the design phase is when deployment
planning should be initiated.
The Design phase culminates with the completion of the Solution Design Document, Functional Design Document, and Technical Design
Documents. Based on the FDDs and TDDs, the project scope is finalized, with all requirements considered to be in-scope cross-referenced to one
of these documents. Customer sign-off is obtained on all the design elements and the final estimates, and the development team is readied for the
custom code development effort.

52) Analysis, design, development phases were closed accordingly, you are ready to transition to the Deployment
team. Which deployment activities plan next? (2)

a. Begin and finalize config. & parameters setting

b. Develop data migration scripts
c. Execute user acceptance test X
d. Migrate live data from the source to production in preparation for cut-over and go-live X

Purpose
The Deployment phase is where all the efforts of the project team come together for a successful transition to the new Microsoft Dynamics™
solution. Key activities in this phase include End User Training, User Acceptance Testing, and the actual cutover to the new or upgraded production
environment. For Enterprise projects, Performance Testing is also completed.
Deliverables/Milestones

Baseline Deliverables
End User Training
User Acceptance Test Results
Final Data Migration (excluding Upgrade Projects)
Final System Readiness & Go-Live Checklist
Production Environment
Cutover to Production

Additional Deliverables for Enterprise Projects

Deployment Plan
Train-the-Trainer (TTT) Training
Production Operations Guide

Milestones
End User Training complete
User Acceptance Testing complete
Production Environment ready
Final Data Migration complete (excluding Upgrade Projects)
System Go-Live

53) Which key tasks when planning go live cutover in a large scaled complex company? You are focused in
deployment activities (2)

Purpose
The purpose of this activity is to ensure that a planned, documented and tested cut over process is in place. This reduces the risk of mistakes
being made over the go live period which can have a significant impact on user acceptance and take up of the solution as a whole.
Description
In planning for the go live cut over consider the following key items:
1. Plan: Write a go-live cut-over plan than provides an overview of all those involved and key activities.
2. Document: Write a go-live cut-over process document that defines the details of the cut over plan on a step-by-step basis. This should include
any key decision points and a step-by-step back out plan if things go wrong.
3. Test: It is recommended that the full cut-over process is run as a dress rehearsal, against one of the other environments at least two weeks
before the final cut-over is due. In complex projects you may need several iterations of testing and enhancing the cut over process.

54) Which tools help meet QA requirements? (2)

a. Detailed requirements documents

b. Daily conference calls
c. Documeted conditions of satisfaction X
d. Phase tollgate review meeting X
MB5-858, SURE STEP 2010

55) What are the elements of a good User Acceptance Testing scripts?

a. Detailed requirements documents

56) As part of Scopement Assessment and Statements of Work you know: single location, 2 ISV solutions, and
medium complex customizations. To analyze current and future business status you:

a. Begin and finalize config. & parameters setting

57) You need to provide business decision makers with a document that defines the proposed solution and
capabilities being enabled by the solution. What should you do?

a. Functional design specifications (FDD) X?

b. Technical design documents
c. Solution desing document
d. Gap design document

58) Project manager is verifying that acceptance criteria is met and confirming final technology and management
reviews of deliverables are complete. He is also collecting intellectual property and confirming that services
plan was delivered to customer. What is he doing?

The Phase Tollgate review presentation is prepared by the Program Manager and presented to the customer at the end of the
phase. The toll gate review highlights the current health of the project, key milestones achieved, key deliverables completed, project
level issues and risks, and the conditions of satisfaction assessment.
--------------------------------------------------------------------------------
Description
The tollgate review presentation for an engagement should highlight the following
1. Project Summary
2. Business Objectives
3. Timeline
4. Milestones and Accomplishments
5. Scope and Change Requests
6. Issues
7. Risks
8. Conditions of Satisfaction
9. Lessons Learned
10. Next Steps

PODRA HABER ALGO ACÁ TAMBIEN??

Description
Contract closing is an activity that supports the closing process for project phases or the project itself, depending on whether the
contract was written for a single phase of a multi-phase project or for the entire project covering all phases.

Contract closing involves getting a final sign-off for the completed services and deliverables.
For a smooth contract closing it is necessary to plan just as carefully as during the initial contract signing. Worrying about contract
closing in the final weeks of the project is too late. Early planning of the closing and proper communication to the appropriate
individuals helps to identify issues sooner and increase the satisfaction for all involved parties. For long term contracting (> 3 Month)
it is helpful to plan for multiple sign-off events in accordance to the project phases and milestones.
The following activities belong to contract closing:
Work with the customer’s management, as needed, to conduct a procurement audit identifying and documenting the lessons
learned that warrant recognition for future use.
Request from the customer a formal written statement that the deliverables have been accepted or rejected.
Initiate the final invoice payment in accordance to the defined payment terms.
Ensure no unresolved claims or contested changes that require arbitration.
Inform any supplier about contract closing and initiate closing of related sub-contracting.
Harvest intellectual property in accordance to the contract terms.
Archive a complete set of the contract documents and the related sign-off and acceptance notifications.
Create a lessons learned documentation for future use.

59) Your project team is working on a large complex implementation with global sites. Complicated IT
infrastructure and large nbr. of users. What steps would you take to ensure performance issues are being
MB5-858, SURE STEP 2010

monitored and proactively address during implementation life cycle? (3)

a. Propose, plan and conduct performance tunning and optimization as post go-live activity X?
b. Execute performance testing before go-live X?
c. Engage third party performance specialist X?
d. Era algo after go-live…

60) You need to preparate to close a contract. What should you do? (2)

a. Request formal writing statement from customer with deliveries acceptance/rejection X

b. Complete final system readiness
c. Make document plans for go-live cutover
d. Archive a complete set of contract documents and related sign-off and acceptance notifications X
61) You and your team implemented MD, with the go-live cutover are both pleased. Post go-live support is
completed. What are the next milestones to plan for? (3)

a. Transition of solution to support complete and formal project closure X

b. Core team training complete and formal project closure X?
c. Obtain complete system acceptance and formal project closure X?
d. Finalize production specifications and formal project closure

62) Enterprise project. Which activities should be budgeted to take place after go-live? (2)

a. Determine final resolution for any items that are outstanding after go-live X?
b. Provide the customer with post go-live support X
c. Finalize training documents
d. Crate a production operations guide that covers std. operations and support activities related with
new solution

63) The contract is formally closed. Is there any remaining task to complete?

a. Yes. Release project team and close communication management X

b. No. After closing there is no remaining tasks
c. Yes. Provide post go-live support and verify project scope
d. Yes. Implement minority of changes agreed during contract closing

64) Performance optional tasks executed in the operation phase. Which optional tasks will you need to consider
address in the future? (2)

a. Apply hot fixes and service packs X

b. Additional user training
c. Archive old data from large tables X
d. Implement application configuration, customization and develop changes
MB5-858, SURE STEP 2010

Business Case: this decision accelerator aids in projecting return on investment (ROI) based on industry benchmarks, estimating total cost of
ownership (TCO), and understanding the benefits of implementing a Microsoft Dynamics ERP solution.

Determine the level of infrastructure analysis based on implementation type.

If you decide to conduct a rapid implementation project, define the infrastructure completely in the Diagnostic phase. Performing a more detailed
analysis of the infrastructure is possible because you will have sufficiently defined the scope and details of the business solution during the
Diagnostic phase.

In Microsoft Dynamics Sure Step there is a Project Status Report template.

This report will gather all notes from the consultants for the Project Manager to present to the customer a weekly summary of the project including
information concerning scope, schedule, cost, and quality including risks and issues. This document can be handed over to the customer during a
weekly project meeting or mailed for revision, depending on the communication agreements noted in the Communications Plan.

The Operation phase involves the final activities required to close out the project and transition the solution and knowledge to the
customer.

Enable Organization
Purpose
The purpose of Enable Organization is to ensure that the new solution is deployed, users are trained, and the help/support processes are made
operational.
Description
The Engage Organization processes are as follows:
· Conduct End User Training. Provide adequate and ongoing training to the end users on the new solution to ensure successful adoption.
· Transition Solution to Support. Engage the support organization and processes and hand over the solution to the Help desk to ensure that
user support requests are handled in a timely manner.
· Handover Master Data Management Process. Ensure that the data management processes are handed over to the data owners so that the
data integrity and accuracy can be maintained through the new solution.

Resource Assignment Matrix

Roles and responsibilities are often described using a Resource Assignment Matrix (RAM). A specific form of a RAM is the RACI Matrix or the
extend form of it, as shown below. The matrix shows which roles are responsible, accountable, consultative, informed, verifying, and signing off.

Extended RACI-Matrix:
R - Responsible, implying the main responsibility in doing or delivering effort and skill.
A - Accountable, implying management (overrides R when both are implied).
C - Consultative, implying assistance (both active and advisory).
I - Informed, implying a requirement of the one responsible to report on the task.
--------------------------------------------------------------------------------------------
V - Verifying, implying a check against the defined scope and conditions of quality standards.
S - Signing-off, implying the actions of review, validation, and acceptance.

Project Manager: en todo es Accountable

Customer Project Manager: Define project roles (R), Assign Resources to project (R)

Quality Management in the Operations phase

To ensure quality management in the Operations phase, the Microsoft Dynamics™ Sure Step Methodology plans for specific Quality Management
activities as follows:

• Preparing and conducting phase tollgate review.

• Clearing pending items.
• Finalizing knowledge transfer.
• Document lessons learned.
• Project closure.

In addition, hot fixes, service packs, or update releases may need to be applied as part of the ongoing maintenance of the Microsoft
Dynamics ERP solution.

The Engagement Closure Checklist

The Engagement Closure Checklist is a guide to ensure that the critical tasks needed to close a project have occurred, and that critical project
information (for example, contractual commitments, customer site logistics, project control processes) is defined and documented.
Project Managers must be accountable for making sure that their customer engagements have ended correctly, and that their team has had the
best opportunity for success. The Engagement Closure Checklist ensures that all the necessary tasks have occurred to successfully end a project.