User Nian Yee has agreed to write this How-to note.
Wikibon How-to Note (aka Level 1 Article)
A Wikibon How-to Note is a document that is useful to a reader as a standalone entity. While it may link to other articles (within or outside of Wikibon) and may contain graphics, these are not necessary conditions for Level 1 compliance. A Level 1 Article is between 1,500 and 2,000 words in length and has the following attributes:
- Follows the Wikibon content outline and format specified in this document and looks substantially similar to the following example Level 1 Articles:
- Includes metrics and rules-of-thumb that are of value, related to the topic, non-obvious, and help the reader get started on a project related to the topic. Metrics should include appropriate attribution.
- Is sufficiently action-oriented and strikes a “how to get it done” tone that is useful to business professionals trying to accomplish work related to the topic.
- Links to external sources for related content where appropriate.
- Is edited, spellchecked, formatted and available on the Wikibon Web site (www.wikibon.org).
- Ends with the following categorization syntax: Category:Level 1 surrounded by opening and closing double brackets [[ ]]
First Paragraph (150 words)
A one paragraph statement on the nature of the business problem to be solved. To ensure that this paragraph is placed prior to the article’s “contents” box, this paragraph should not be preceded by a header.
<Storage resource management> capability (150 words)
A one paragraph statement on how the technology/product/service set solves the problem. The header should include the capability name. Specific operational goals of <capability> (300 words) Using the Wikibon model business ($1B revenue), list the FIVE-to-EIGHT seminal operational goals associated with generating the capability. These goals should include:
- Expense to create the capability.
- Time to create the capability.
- Operating attributes of the capability (resources to deliver at what scale)
- Expected range of “Variable 1” business returns.
- Expected range of “Variable N” business returns.
- General impacts on “average” infrastructure.
- Key exit considerations.
Specific operational goals of storage resource management <capability>
Using the Wikibon model business ($1B revenue), list the FIVE-to-EIGHT seminal operational goals associated with generating the capability. These goals should include:
- Expense to create the capability.
- Time to create the capability.
- Operating attributes of the capability (resources to deliver at what scale)
- Expected range of “Variable 1” business returns.
- Expected range of “Variable N” business returns.
- General impacts on “average” infrastructure.
- Key exit considerations.
Risks of implementing storage resource management (150 words)
A ONE paragraph statement on the types of risks that must be mitigated for a capability to be successfully realized.
The <capability> initiative
This is the main body of the document. The basic objective is to provide high-level guidance regarding how a team will move an organization from a generalized “as-is” state to a generalized “to-be” state. This section of the article highlights three phases of a project including: 1) Analyze; 2) Design and 3) Deploy. Each phase includes an “acceptance test considerations” paragraph, which answers the “How do you know when you’re finished” question, as well as a simple articulation of any key metrics or rules of thumb to consider. Also included in each phase is a Key Milestones section which identifies the most important milestones (events) and activities (tasks) that need attention in order to reach the milestone.
Expectations (Out-of-scope) (200 WORDS)
Every initiative has a scope. However, every initiative requires that certain out-of-scope expectations be met if the initiative is to succeed. For example, an initiative intended to deploy a “customer profitability reporting” capability presupposes the existence (or commitment to deploy) of function for aggregating customer data in some form. This section highlights, in list form, the three-to-five, out-of-scope conditions or expectations that must be satisfied for the initiative to succeed.
- List of expectation #1 through N
Analyze Phase (250 WORDS)
Acceptance Test Considerations
ONE paragraph on “How do you know when you’ve successfully completed the Analysis phase?”
Key analysis milestones
List of three-to-five milestones (including anticipated elapsed time and effort) that are most likely to influence the success or failure of an initiative. Under each milestone, the activities or outcomes most critical to the milestone effort should be listed. This list is not comprehensive. Only the most critical milestones should be listed. In the analyze phase, this is likely to include activities like:
- Key data to gather
- Key trends to factor
- Required stakeholder participation (e.g., Champion, Project lead, critical technology talent)
Design phase (250 WORDS)
Acceptance Test Considerations
ONE paragraph on “How do you know when you’ve successfully completed the Design phase?”
Key design milestones
List of three-to-five milestones (including anticipated elapsed time and effort) that are most likely to influence the success or failure of an initiative. Under each milestone, the activities or outcomes most critical to the milestone effort should be listed. This list is not comprehensive. Only the most critical milestones should be listed. In the design phase, this is likely to include activities like:
- Two-to-three key business impacts to factor
- Two-to-three key technology impacts to factor
- Three-to-five key trade-offs to consider
Deploy phase (250 WORDS)
Acceptance Test Considerations
One paragraph on “How do you know when you’ve successfully completed the Deploy phase?”
Key deployment milestones
List of three-to-five milestones (including anticipated elapsed time and effort) that are most likely to influence the success of failure of an initiative. Under each milestone, the activities or outcomes most critical to the milestone effort should be listed. This list is not comprehensive. Only the most critical milestones should be listed. . In the deploy phase, this is likely to include activities like:
- The ONE key skills consideration.
- The TWO key sourcing considerations.
- Two-to-five compatibility considerations.
- Two-to-five training/education considerations.
Initiative summary (150 words)
One paragraph summarizing the time and resources required to realize the capability.