DISCOVER - This stage guides the development team through designing a prototype and setting goals. At the end of this stage, everyone involved in the project should have a clear picture of which applications are being developed and why.Of the thirteen jm+co rules for Private Web development, five are put to use in the Discover stage.
Rule 1 -
BEGIN WITH THE END IN MIND
It is extremely important to ensure that the driving force behind your prototype application is part of a process that directly produces value for the customer of the organization. These are typically applications that impact the corporate mission or an identified value stream. During the "Build Client Wish List" task, you will review the available opportunities. These drivers and other pertinent issues are quickly identified, so that a prototype can be built that will generate broad-based support and aid team members in setting goals for the project as a whole.
It is extremely important to ensure that the driving force behind your prototype application is part of a process that directly produces value for the customer of the organization. These are typically applications that impact the corporate mission or an identified value stream. During the "Build Client Wish List" task, you will review the available opportunities. These drivers and other pertinent issues are quickly identified, so that a prototype can be built that will generate broad-based support and aid team members in setting goals for the project as a whole.
Rule 3 -
THINK ORGANIZATIONALLY, NOT COMPUTATIONALLY
It is very important to select technologies based on goals and needed functionality, not popularity with other organizations. During the "Identify Client Requirements" task, you will identify the specific functions you will require in order to have a successful system. This rule warns us to avoid selecting technologies just because, "everyone else has it". This leads to making decisions based on goals we set considering the specific costs and needs of the organization.
It is very important to select technologies based on goals and needed functionality, not popularity with other organizations. During the "Identify Client Requirements" task, you will identify the specific functions you will require in order to have a successful system. This rule warns us to avoid selecting technologies just because, "everyone else has it". This leads to making decisions based on goals we set considering the specific costs and needs of the organization.
Rule 4 -
UNDERSTAND THE POSSIBILITIES
The members of your development team must understand the technologies involved in your private web project, as well as understanding what is possible today using Internet technologies. The "Identify Project Team" task provides a matrix and guidelines for selecting team members as well as a way of documenting your justifications for selecting each developer. Throughout the methodology, you will find pointers guiding you to where to search on the web for "up to the minute" information on specific cutting-edge topics.
The members of your development team must understand the technologies involved in your private web project, as well as understanding what is possible today using Internet technologies. The "Identify Project Team" task provides a matrix and guidelines for selecting team members as well as a way of documenting your justifications for selecting each developer. Throughout the methodology, you will find pointers guiding you to where to search on the web for "up to the minute" information on specific cutting-edge topics.
Rule 5 -
KNOW WHERE YOU ARE AND WHERE YOU ARE GOING
During the "Build Client Wish List" you gather some baseline information, which is later refined in the Design stage. Assessing not only technical impacts, but staffing impacts is crucial to the success of the new system.
During the "Build Client Wish List" you gather some baseline information, which is later refined in the Design stage. Assessing not only technical impacts, but staffing impacts is crucial to the success of the new system.
Rule 9 -
MIX UP YOUR STAFFNo,
this does not mean intentionally confuse people. Rather it means that it is important to get different perspectives from people at different levels and parts of the organization. This rule comes into play in both the "Identify Project Team" and "Identify Client Requirements" tasks. Select your project team from a diverse group and demonstrate your prototype to broad audiences in order to get feedback from as many people as possible. In this way, you will get everyone's needs out in the open where they may be assessed and addressed.
this does not mean intentionally confuse people. Rather it means that it is important to get different perspectives from people at different levels and parts of the organization. This rule comes into play in both the "Identify Project Team" and "Identify Client Requirements" tasks. Select your project team from a diverse group and demonstrate your prototype to broad audiences in order to get feedback from as many people as possible. In this way, you will get everyone's needs out in the open where they may be assessed and addressed.
Build Client Wish List
Building the Client Wish List involves the following tasks:- Complete Client Profile Questionnaire - Analyze Industry Information- Perform an Enterprise-wide Analysis What am I doing?During the Complete Client Profile Questionnaire step you will identify the clients' (these can be external or internal clients) principals and collect baseline requirements data. Then you will Analyze Industry Information by gathering information from the principals and other resources. As you Perform an Enterprise-Wide Analysis you will gain an understanding of past organizational issues and project future Internet-related needs in order to ensure integration with other efforts. Why? The first task in the web building process is to get a feel for the immediate needs of the organization. During this task, you will identify an important value stream for the organization and determine how you can improve the process to make the organization more effective. Working through the fact-finding steps in this task will help you to develop an effective prototype and get the project off on the right foot. This task also helps the project manager gain an understanding of what the principals' expectations are going to be with respect to this project. Internal client issues will be uncovered early to allow you time to deal with them effectively. Documentation of this information gathering process will be used later for further discussions and to validate decisions made during the project.What are the risks of not properly performing this step?- Critical client goal or background information may be missing. The Client Profile Questionnaire allows individual principals to give thoughtful and complete input to client goals without the political and timing pressures of a group situation . It draws out information which may have been missed in the initial goal discussion.- You may end up with an ineffective prototype. Since gaining universal support early and showing immediate results are the key to building your Intranet, this could be a mistake that dooms your project to failure.- Your efforts may conflict with other past, present, or future efforts. Has someone developed a site at the departmental level? What other plans are in the works? The Enterprise-wide Analysis helps you ask the right questions and coordinate your efforts with others.
Identify Project Team
Identifying the project team involves the following tasks:- Identify Creative Team - Identify Technical Team - Identify the Content Management TeamIn order to properly Identify the Creative, Technical, and Content Management Teams; you will need to review the client requirements and convert them to skill requirements using the role/skills document template. Each role/skills template has suggested skills for each team. Modify these to suit your specific requirements.Why am I doing it? Finding the right person to fill each role is many times a difficult task. You must, however, begin with the end in mind by knowing which specific skills are needed for each role before making team assignments.What are the risks of not properly performing this step?- The wrong person may be selected for a role. Web site development teams are typically small groups of talented people. Each person typically has specialties within their area of expertise. If a Microsoft NT administrator is tasked with setting up a UNIX environment the project may be seriously impacted. A graphics designer may be skilled at selecting production graphics, but may not understand the art of site concept, layout, or size reduction. The Role/Skills Document Template will aid you in identifying needed skills.- You may assign someone whose time is already over allocated. If your team members are not dedicated to this project, you need to understand the amount of time they can spare and manage the project accordingly. - The wrong mix of people may be assigned to the project. Getting feedback from each potential team member on including the others may help to avoid future conflicts.
Establish Development Environment
Establishing the Development Environment involves the following tasks:- Select a Hosting Option- Set Up InfrastructureWhat am I doing?As quickly as possible, you are setting up the infrastructure for the prototype. This is a quick version of the process you will go through in setting up the production environment, but in the interests of time not all component selection factors are considered.Why am I doing it?The Private Web prototype tends to be very high impact for three basic reasons:1. It solves a specific business problem or improves a value stream process.2. It is produced in a time period that would not be possible using client/server tools.3. It demonstrates the high return on investment that Internet technologies can provide.The information gathering performed at the beginning of the Private Web Development Process helped to ensure that you are building the correct prototype application. The key during this part of the process is speed. While ensuring that the prototype you build is reliable and stable, keep a fast development cycle in mind as a primary objective. Given the competitive market for Internet technologies, investments in software components should be minimal.What are the risks of not properly performing this step?- The prototype may be brought on line too slowly and therefore have less impact.- The prototype may be built using unfamiliar tools. This can slow the development process and increase the likelyhood that an unstable prototype will be produced.
Build Prototype
Building the Prototype involves the following tasks:- Gather Pilot Content - Identify Package Solutions- Select and Create Graphics- Build Prototype InfrastructureWhat am I doing?As quickly as possible, you are building at least one of the candidate prototypes identified in the Enterprise-wide Analysis.Why am I doing it? The Private Web prototype tends to be very high impact for three basic reasons:
1. It solves a specific business problem or improves a value stream process.
2. It is produced in a time period that would not be possible using client/server tools.
3. It demonstrates the high return on investment that Internet technologies can provide. The information gathering performed at the beginning of the Private Web Development Process helped to ensure that you are building the correct prototype application. The key during this part of the process is speed. While ensuring that the prototype you build is reliable and stable, keep a fast development cycle in mind as a primary objective. Given the competitive market for Internet techologies, investments in software components should be minimal.
What are the risks of not properly performing this step?-
The prototype may be brought on line too slowly and therefore have less impact.- Too much of the prototype will be unnecessarily coded by hand, which will slow delivery.- Too much emphasis will be placed on graphical appeal, which could slow delivery. Later in the Design stage, the visual architecture will be designed and implemented. Excessive attention to graphics at this point is a mistake.
Identify Client Requirements
Identifying Client Requirements involves the following tasks:-
Demonstrate Prototype-
Discuss Goals with Principals
At this point the DESIGN stage has begun and a prototype has been created. During this task, you will demonstrate the prototype and solicit as much feedback as possible. Following the demonstrations, you will discuss the goals of the site as a whole using the information gained up to this point in the project. Once goals are determined, they must be mapped to general functions on the site.
Posts
No comments:
Post a Comment