Tài liệu Module 7: Presenting Information pptx

Module 7: Presenting Information THIS PAGE LEFT INTENTIONALLY BLANK Module 1: Course Overview Module 4: Gathering Information Module 5: Analyzing Information: Use Cases and Usage Scenarios Module 6: Analyzing Information: Rationalizing Information Module 7: Presenting Information Gathering and Analyzing Business Requirements Module 2: Identifying Business Processes, Challenges, and Vision Module 3: Characteristics of Information Summarizing and Presenting the Results Review Module 7: Presenting Information Module 7: Presenting Information 157 ! !! ! Overview In this module . In this module . " Summarizing and Presenting the Results " Review After you have gathered and analyzed information on the business challenge, you will need to present it in a format that communicates the results to users, stakeholders, and the development team. A vision document represents one way to present the results of the project team’s work. In this module, you will use the vision document to summarize the information that you have developed for the Ferguson and Bardell, Inc. case study. You will also use the vision document as a way to review the concepts and skills that you have learned in this course. After completing this module, you will be able to: " Identify the contents and purpose of a vision document. " Develop a preliminary vision document. " Summarize the major concepts of the course. Slide Objective To provide an overview of the module topics and objectives. 158 Module 7: Presenting Information ! !! ! Summarizing and Presenting the Results " Envisioning Phase " Vision Document " Solution Concept " User Profiles " Business Goals " Design Goals " Activity 7.1: Developing a Preliminary Vision Document In this section . In this section . Throughout this course, you have been learning and performing tasks that are part of the Envisioning Phase of the Microsoft ® Solutions Framework (MSF) Process Model. The activities that you have completed provide information for the vision document, which is one of the main deliverables of the Envisioning Phase. In this section, you will review the main purpose of the Envisioning Phase. Then you will review the items that make up the vision document. Finally, you will learn about the items of the vision document that you have not discussed in previous modules. In Activity 7.1, you will develop a preliminary vision document for the Ferguson and Bardell, Inc. case study. Slide Objective To provide an overview of the section topics and activity. Module 7: Presenting Information 159 Envisioning Phase " Creates a high-level view of the project’s goals and constraints " Serves as an early form of planning " Helps the team pull different perspectives into a common understanding " Provides the basis for future planning " Captures what the customer and key stakeholders deem essential for success The purpose of envisioning, which is the first of four phases in the MSF Process Model, is to obtain an early understanding of the project’s goals and constraints. The project team uses envisioning to answer feasibility questions, gain approval from key stakeholders, and acquire a common set of expectations from everyone involved. Envisioning is fundamental to the success of a project because it sets the base upon which team members will build a shared vision. Envisioning culminates in the Vision Approved Milestone. The outcome of envisioning sets the stage for the more detailed planning effort that will come later. Approval of the project vision signals that members of the project team, the customer, and key project stakeholders agree at a high level on why the project is being done, what should be done, the risks of doing it, and who should do it. The deliverables for the Vision Approved Milestone are the vision document, the risk assessment document, and the project structure document. In this course, you develop most of the information needed for the vision document. Slide Objective To summarize the Envisioning Phase and how it relates to the course. Lead-in The purpose of the Envisioning Phase is to obtain an early understanding of the project’s goals and constraints. Delivery Tip Emphasize to students that they do not complete the Envisioning Phase in this course. They develop most of the information needed for the vision document. However, they do not take the final step of optimizing the information that they have gathered, which is necessary to complete the vision document. 160 Module 7: Presenting Information Vision Document Content Purpose Problem statement Vision statement Solution concept User profiles Business goals Design goals Why you want to do it What you want the product to be What you will do Who will use the product What you want to accomplish How you plan to accomplish it The vision document explicitly states the output of the envisioning process and forms the basis of the first agreement among everyone involved in the project. The vision document is the primary deliverable for the Vision Approved Milestone. The project team uses it as the basis for deciding whether to go ahead with the project. The vision document also provides a framework for planning throughout the rest of the project. The vision document should clearly explain why the team wants to do the project, what the product will be and do, what the product will not be and do, how the team will successfully complete the project, and what risks the team will incur by taking on the project. The items presented in this section represent those items that should be in the document at a minimum. Additional items may be necessary, such as an issues section that lists risks that the team cannot mitigate without outside intervention. The nature of the business and project will ultimately determine what the project team will include in the vision document. In this module, you will focus on developing a preliminary vision document to communicate project information to stakeholders. You can communicate a shared vision through other ways, such as presentations to stakeholder groups, Web sites, or company newsletters. You have already developed the problem statement, or business challenge, and the vision statement earlier in this course. The remainder of this section covers the new items that you need to develop. The information that you have gathered and analyzed throughout the course will help you to develop the additional items. Slide Objective To summarize the purpose and parts of a vision document. Lead-in The vision document explicitly states the output of the envisioning process. Module 7: Presenting Information 161 Solution Concept " Outlines an approach for solving the business problem " Expresses the product solution in nontechnical terms " Guides product research, analysis, and design " Describes features at a high level " Helps set an early scope for the project The solution concept describes the functionality provided by the new product. Because the solution concept serves as a business case, its audience tends to be more business oriented and less technical. The project team should write the proposed solution in terms that the target audience can understand. The solution concept is a first attempt at design, so that all design that occurs is a version or an evolution of this first attempt. However, the project team should avoid becoming locked into a specific technology at this stage. You will not be able to specify features at this stage because you have not completed the final step of optimizing the requirements and wants. You can state an initial solution concept based on the analysis that you completed in Modules 5 and 6. The solution concept and design goals work in conjunction to provide an initial scope to the vision statement. Slide Objective To explain the purpose of the solution concept. Lead-in The solution concept describes the functionality provided by the new product. Delivery Tip Tell students that they complete the process of optimizing requirements in Course 1608: Designing Business Solutions. 162 Module 7: Presenting Information User Profiles " Identify and classify the potential users of the product " Drive understanding of the intended users " Describe user goals and constraints " Identify early project risks " Help facilitate design decisions " Help define user performance support requirements User profiles are the team’s first attempt to understand the breadth of the product’s audience. When creating the user profiles, look at all of the potential users, direct and indirect, such as the person actually using the product or the manager who might be receiving hard-copy printouts of a report. User profiles try to capture what the users expect and what they need, as well as their goals. Document the issues that constrain the users, such as hardware, software, or anything else that might impact their ability to use the product. Generally, user profiles provide a detailed description of the users’ level of ability in relation to the proposed product. The user profiles lay the groundwork for understanding what the user needs for training and support. Slide Objective To explain the purpose of user profiles. Lead-in User profiles are the team’s first attempt to understand the nature of the product’s audience. Module 7: Presenting Information 163 Business Goals " Describe the expected business benefit of creating the product " Create a set of postproject metrics for the product " Help in making trade-off decisions " Clarify the relative priorities of the goals " Can describe specific “nongoals” for the product Business goals form the basis for determining the product’s success criteria versus the project’s success criteria. Ultimately, the business goals represent what the customer believes the product will do for the customer. Business goals offer insight into what the customer believes will make the product a success. Throughout the life of the project, the team makes trade-offs among resources, schedules, and features. Understanding the customer’s business needs is necessary to help the team determine what trade-offs to make. List the business goals in a prioritized way so that, if some goals cannot be achieved, the team has a clear understanding about which ones the customer believes are most important. Slide Objective To describe the purpose of business goals. Lead-in Business goals form the basis for determining the product’s success criteria versus the project’s success criteria. 164 Module 7: Presenting Information Design Goals " Restate product requirements and constraints as goals for design " Provide the basis for the design activity " Set product expectations " Help set an early scope for the project " Clarify product priorities " Can describe specific nongoals for the product Design goals are similar to business goals in many ways. The differences between the two are evident in their focus: design goals focus more on the attributes of the product, while the business goals focus on what the product will do for the business. Design goals should be prioritized so that if the project cannot achieve certain goals, the project team knows which goals should receive the primary focus. Design goals and the solution concept provide an initial scope that will become the basis for future design work. Establishing design goals and the solution concept is an iterative process. Sometimes, design goals are clearer and will help feed the solution concept. Other times, the solution concept will be clearer and will help feed the design goals. Design goals not only address what the project team wants to accomplish with the product, but also what the project team does not want to accomplish. An example of a design goal is the predetermined level of quality necessary for the product to be ready for users. Slide Objective To explain the purpose of design goals. Lead-in Design goals focus on the attributes of the product. [...]... business challenge provide the project team with the initial information to create the application’s design, particularly the conceptual design 168 Module 7: Presenting Information Review Questions Slide Objective To reinforce module objectives by reviewing key points Lead-in The review questions cover some of the key concepts taught in the module " Identify the contents and purpose of a vision document... review Finally, you will learn how the concepts and activities in this course relate to the entire process of developing business solutions Module 7: Presenting Information 167 Guidelines Slide Objective To present general guidelines related to the information in this module " Communicate the shared vision to involved parties " Write the vision document to sell it to key stakeholders " Follow SMART principles... this activity, you will create a preliminary vision document by using information that you have developed from previous activities, as well as developing new information from the Ferguson and Bardell, Inc case study After completing this activity, you will be able to: " Develop a preliminary vision document 166 Module 7: Presenting Information ! Review Slide Objective To introduce the topics in the.. .Module 7: Presenting Information 165 Activity 7.1: Developing a Preliminary Vision Document Slide Objective To explain the activity In this course, you do not complete all of the work in the Envisioning Phase However, by developing a preliminary vision document, you can organize the information that you have gathered and analyzed to summarize... ahead with the project The vision document also provides a framework for planning throughout the rest of the project Module 7: Presenting Information 169 3 What are some of the key items in the vision document? Problem statement: Describes the business challenge and the relevant background information Vision statement: Describes the fundamental goals of the product and sets the early scope of a project... product 170 Module 7: Presenting Information Looking Forward Slide Objective To relate the course concepts to the entire process of developing business solutions " Application Design Process $ $ Logical $ " Conceptual Physical Course 1608: Designing Business Solutions The project team must now complete the application’s design process The application design will provide the project team with the information. .. shape the final business solution, and to provide the project team with the information they need to develop a solution that addresses the business challenge The vision document and the process required to create the document also provide the project team with a base of information from which to create the solution’s design The information identified by the project team about the user community, application... introduce the topics in the section " Guidelines " Review Questions " Looking Forward This section presents an opportunity to review the material in this module First, you will look at guidelines that you can use to adapt the information and skills in this module for use in the workplace Next, you will answer questions about the material in this section As you answer the questions, note which topics you... application will do to solve the business challenge The logical and physical design will further describe how the new application will function Designing Business Solutions (Course 1608) provides more information on the conceptual, logical, and physical design process This workshop teaches students how to use conceptual, logical, and physical models and the appropriate MSF models and processes to design . Vision Module 3: Characteristics of Information Summarizing and Presenting the Results Review Module 7: Presenting Information Module 7: Presenting Information. Module 7: Presenting Information THIS PAGE LEFT INTENTIONALLY BLANK Module 1: Course Overview Module 4: Gathering Information Module 5: Analyzing Information: