<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom">
    <title>Penguin Storm</title>
    <link rel="alternate" type="text/html" href="http://www.penguinstorm.com/" />
    <link rel="self" type="application/atom+xml" href="http://www.penguinstorm.com/atom.xml" />
    <id>tag:www.penguinstorm.com,2007-09-30://6</id>
    <updated>2007-09-30T00:59:22Z</updated>
    
    <generator uri="http://www.sixapart.com/movabletype/">Movable Type Open Source 4.1</generator>

<entry>
    <title>Planning</title>
    <link rel="alternate" type="text/html" href="http://www.penguinstorm.com/development_process/planning/" />
    <id>tag:www.penguinstorm.com,2005://6.1701</id>

    <published>2005-11-04T04:57:06Z</published>
    <updated>2007-09-30T00:59:22Z</updated>

    <summary>What&apos;s the most important park of any project? Design? Programming? Testing?

Think again. It&apos;s planning, and it&apos;s where we start.</summary>
    <author>
        <name>Skot Nelson</name>
        
    </author>
    
        <category term="Development Process" scheme="http://www.sixapart.com/ns/types#category" />
    
    
    <content type="html" xml:lang="en-us" xml:base="http://www.penguinstorm.com/">
        <![CDATA[<p>Planning is the first phase of any project, no matter how small. You wouldn't start a house without doing it, and you shouldn't start a software project.</p>

<p>Planning happens in a few stages: if this seems like a lot, don't worry - for small projects, many of these stages involve just a few minutes of your time. Just think of this as a checklist - remembering what you're supposed to do is important, even if some of the steps get skipped on purpose.</p>

<h2>Project Brief</h2>

<p>The first step involves a review of the project brief. Are there any questions left over? Have all the important roles been defined? Are critical dates listed? Is a budget defined, even if it's only approximate?</p>

<p>Don't forget the most important question: <em>Is the project's purpose clear.</em> Without a clear definition, you're doomed for failure.</p>

<p>Once everyone's happy with the project brief, everybody signs off on it and the project starts.</p>

<h2>Project Schedule and Budget</h2>

<p>A project schedule means committing to delivery dates. Getting these dates on the table and committing to a budget up front is importat to make sure that everybody is on the same page.</p>

<h2>Project Plan</h2>

<p>Think of the Project Plan as a response to the Project Brief. It summarizes everything in it, and outlines how the projects goals are going to be achieved. It's a road map for the project.</p>

<h1>After the Plan</h1>

<p>Once everybody's agreed to a plan, we move on to the Execution phase.</p>]]>
        <![CDATA[<p>Planning is more important than ever in software development, and it's happening less than it ever has. A project without a plan is a recipe for unhappiness.</p>]]>
    </content>
</entry>

<entry>
    <title>Custom Content Management</title>
    <link rel="alternate" type="text/html" href="http://www.penguinstorm.com/content_development/custom_content_management/" />
    <id>tag:www.penguinstorm.com,2005://6.1700</id>

    <published>2005-10-18T16:45:15Z</published>
    <updated>2007-10-06T02:07:55Z</updated>

    <summary>There are times when existing content management systems just won&apos;t do - your needs are different and unique in some way.
Custom content management systems can offer the solution you&apos;re looking for. Properly designed, such systems offer significant advantages, but come with a cost associated.
We can help you define your needs and determine whether a custom solution or an off the shelf one is what you&apos;re looking for. Learn about some of the issues you need to think about, and learn how we can help you resolve them.</summary>
    <author>
        <name>Skot Nelson</name>
        
    </author>
    
        <category term="Content Development" scheme="http://www.sixapart.com/ns/types#category" />
    
    
    <content type="html" xml:lang="en-us" xml:base="http://www.penguinstorm.com/">
        <![CDATA[<p>To a hammer, everything looks like a nail. To a content management vendor, their content management system always works for your content.</p>

<p>Common sense tells you this simply isn’t true.</p>

<p>Custom content management systems typically offer a tremendous advantage in cases where the structure of the information you need to display contains more than a few simple fields, when you need to design a custom workflow for your environment, or when you need to share responsibility for different areas of content. Many of these things can be done with commercially available content management systems, but you it may be more efficient to build your own system from scratch.</p>

<p>We’ll analyze your content plan and determine the most effective way for you to turn it into a reality. Understanding your options means you can make the right decision for your business in the long term.</p>

<p><em>Deliverables.</em> Content Management Recommendation document, with background information.<br />
Development deliverables vary from project to project, but generally include all code installed in the functional environment, necessary documentation (both system and user documentation) as well as a backup CD of all code.</p>

<p><em>Rates.</em> A content management recommendation can be prepared for a fixed price of $200. This involves a review of your existing documentation and data structures, any existing infrastructure, as well as your content plan.</p>

<p>Content Management System Development rates start at US$100 per hour.</p>]]>
        <![CDATA[<p>Building your own content management system <em>may</em> be the right solution, but it requires careful thought. Why reinvent the wheel if you don't need to?</p>]]>
    </content>
</entry>

<entry>
    <title>Database Planning</title>
    <link rel="alternate" type="text/html" href="http://www.penguinstorm.com/content_development/database_planning/" />
    <id>tag:www.penguinstorm.com,2005://6.1699</id>

    <published>2005-10-18T16:44:27Z</published>
    <updated>2007-09-30T00:59:22Z</updated>

    <summary>Your database is like that overstuffed storage closet in your house - you know you&apos;ve put something really important in it, but it doesn&apos;t do you any good if you can&apos;t find it.
A properly planned database helps you in every aspect of your business: it stores data efficiently; it makes data mining easier to do and faster to accomplish; it creates new possibilites for your business.
We can help you with planning your database as well as planning for your data mining and analysis needs.</summary>
    <author>
        <name>Skot Nelson</name>
        
    </author>
    
        <category term="Content Development" scheme="http://www.sixapart.com/ns/types#category" />
    
    
    <content type="html" xml:lang="en-us" xml:base="http://www.penguinstorm.com/">
        <![CDATA[<h3>Benefits of Database Planning</h3>

<p>Database planning can seem quite simple at first glance – write down the information you need, separate it into tables and you’ve got your database.</p>

<p>Too often, this ignores the fundamental reason you use a database in the first place: <strong>Data Mining.</strong></p>

<p>Using a database to store your company’s information is a great idea, as long as you can use it. Data mining provides the most powerful marketing tool you have if it’s done well.</p>

<h3>Database Choices</h3>

<p>Choosing a database doesn’t have to be difficult – in fact, your choice of platform often dictates the best database to use. Trust your technology expert’s recommendation-  whatever database you’re using, our database planning will help you get the maximum value from your data. </p>

<h3>Database Hosting</h3>

<p>Some databases are hosted in house, others are hosted on dedicated servers at hosting facilities. Both of these solutions work, as long as you remember one fundamental rule:</p>

<h3>Back Up Your Data!</h3>

<p>There’s no sense in building up years of expertise and knowledge only to have it all disappear because of data loss. You may never recover from a loss like this.</p>

<p>Data loss is a bigger risk to most businesses than data theft, and yet many worry more about theft. </p>

<p>Create a backup plan, make sure it’s being executed and don’t be afraid to test its integrity on a regular basis. A backup won’t do you any good if it’s corrupt, or you don’t know how to restore your data.</p>

<div ID="deliverables">
<em>Deliverables.</em> Database table description document. Enterprise relationship document.

<em>Rates.</em> Database design work starts at US$100 per hour.</div>]]>
        <![CDATA[<p>In the information age databases are your most powerful asset. Entire companies have been built around good databases for years - American Express, Amazon.com, Air Miles...none of these companies would have succeeded without good databases.</p>]]>
    </content>
</entry>

<entry>
    <title>Our Development Process</title>
    <link rel="alternate" type="text/html" href="http://www.penguinstorm.com/development_process/our_development_process/" />
    <id>tag:www.penguinstorm.com,2005://6.1698</id>

    <published>2005-10-17T18:10:03Z</published>
    <updated>2007-09-30T00:59:22Z</updated>

    <summary>Our development process is intended to eliminate those things that are the enemies of projects everywhere: surprises, needless changes, scope creep. All of these things conspire to prevent you from getting things done on time.

Learn a little bit about it here, and please feel free to ask us any questions you have.</summary>
    <author>
        <name>Skot Nelson</name>
        
    </author>
    
        <category term="Development Process" scheme="http://www.sixapart.com/ns/types#category" />
    
    
    <content type="html" xml:lang="en-us" xml:base="http://www.penguinstorm.com/">
        <![CDATA[<p>Our development process is based on years of experience working on both sides of the fence: as a purchaser of web services, and a vendor.</p>

<h3>We Work With You</h3>

<p>The heart of our philosophy means that we work with you to maximize your investment. It's our view that the best way to create long term, enduring relationships with our clients is to be open, honest and to promote clear communications.</p>

<p>Long term relationships with clients are our goal - by working together, we can grow and make sure that your technology investment grows with you.</p>

<h3>We Don't Just Say Quality - We Mean It</h3>

<p>A lot of people say they focus on quality; we take a wholistic view of this and use it as more than just a buzzword.</p>

<p>It's our goal to make sure that you understand everything that we do, and are satisfied that we have acted in your best interests. Because we focus on quality, we're confident that you'll be happier with the final result.</p>

<p>Writing your invoice is the last thing we do, not the first.</p>]]>
        
    </content>
</entry>

<entry>
    <title>Content Management Systems</title>
    <link rel="alternate" type="text/html" href="http://www.penguinstorm.com/content_development/content_management_systems/" />
    <id>tag:www.penguinstorm.com,2005://6.1696</id>

    <published>2005-10-17T18:06:27Z</published>
    <updated>2007-09-30T00:59:22Z</updated>

    <summary>Buying a content management system is road full of potential potholes. We can help you choose one, and understand the critical factors that you need to consider.</summary>
    <author>
        <name>Skot Nelson</name>
        
    </author>
    
        <category term="Content Development" scheme="http://www.sixapart.com/ns/types#category" />
    
    
    <content type="html" xml:lang="en-us" xml:base="http://www.penguinstorm.com/">
        <![CDATA[<p>Content Management Systems give you the flexibility to manage your site’s content without needing to know <span class="caps">HTML.</span></p>

<h3>What to Look For in a Content Management System.</h3>

<p><strong>Documentation.</strong> Any software package you buy should be well documented – this  is especially true of your content management system. Without documentation, future upgrades and updates are going to virtually impossible to implement.</p>

<p><strong>Support.</strong> Many companies have developed proprietary content management systems that offer little or no support. This locks you into a single source for information, support and future upgrades. Buying a content management system with a broad support network ensures that no matter what happens, your investment is secure.</p>

<p><strong>Cost.</strong> The software components of content management systems can range from Free to thousands of dollars. More important than this is keeping an eye on the full cost of your project. A free solution that comes with thousands of dollars of consulting costs to implement doesn’t do you any good. Any solution that’s handed off to you without detailed documentation of the type of customization work that’s been done could cost you thousands of dollars down the road if you need to find a new devloper. Don’t lose site of the whole board when you’re looking at cost.</p>

<p><strong>Extensibility.</strong> Your content management system should include a plug-in architecture that makes it possible to add features that aren’t part of the core functionality. Even if you don’t need this architecture immediately, it may be necessary in the future in order to implement some new functionality.</p>]]>
        <![CDATA[<p>Content management systems give <em>you</em> -- not your designer -- control over your site. Using one as the basis of your site is the first step in <em>taking control of your online communications.</em></p>]]>
    </content>
</entry>

<entry>
    <title>Information Architecture</title>
    <link rel="alternate" type="text/html" href="http://www.penguinstorm.com/content_development/information_architecture/" />
    <id>tag:www.penguinstorm.com,2005://6.1694</id>

    <published>2005-10-17T18:05:29Z</published>
    <updated>2007-09-30T00:59:22Z</updated>

    <summary>Information Architecture is an integral part of the planning process for any web site. It&apos;s when you organize your content, create the labels and structure that are critical to helping people find what they&apos;re looking for.
Information Architecture combines a knowledge of how pople search and find things with an awareness of what works and doesn&apos;t work online. It provides the foundation on which your visual design will be based, and the platform for a usable web site.</summary>
    <author>
        <name>Skot Nelson</name>
        
    </author>
    
        <category term="Content Development" scheme="http://www.sixapart.com/ns/types#category" />
    
    
    <content type="html" xml:lang="en-us" xml:base="http://www.penguinstorm.com/">
        <![CDATA[<p>Information architecture is the core of many software projects: you wouldn’t build a house without a plan, why build software without one?</p>

<p>Information Architecture provides that plan, with a focus on helping your users satisfy their information needs. The proper site structure, headings, search tools and other factors can dramatically improve your site’s information scent.</p>

<p>Good architecture not only improves customer satisfaction, usability, and information scent, it also helps your site in the quest for customers at search engines. <em>Search Engine Optimization</em> can be a highly effective marketing tool – if your site’s content delivers on the promise. Well organized sites are the building block of a good search engine placement.</p>

<p><em>Rates.</em> Information Architecture work starts at US$100 per hour.</p>

<p><em>Deliverables.</em> Information architecture deliverables vary from project to project. At a minimum, a site map and content overview are usually requested. In some cases, selected low fidelity prototypes can be desirable. Design briefs can also be provided if visual design work has not yet been completed.</p>]]>
        
    </content>
</entry>

<entry>
    <title>Usability</title>
    <link rel="alternate" type="text/html" href="http://www.penguinstorm.com/project_management/usability/" />
    <id>tag:www.penguinstorm.com,2005://6.1693</id>

    <published>2005-10-17T18:04:55Z</published>
    <updated>2007-09-30T00:59:22Z</updated>

    <summary>Have you ever been frustrated with a store and just walked out? Think about what makes this happen:

Problems finding what you&apos;re looking forLong lines at the checkoutPoor customer service
All of the same principles apply to your online presence - we can them usability, and we can help you make sure your web site is as usable as possible.</summary>
    <author>
        <name>Skot Nelson</name>
        
    </author>
    
        <category term="Project Management" scheme="http://www.sixapart.com/ns/types#category" />
    
    
    <content type="html" xml:lang="en-us" xml:base="http://www.penguinstorm.com/">
        <![CDATA[<p>Why you need usability is no secret: if people get frustrated with your web site, they’re not going to keep using it. The tricky part is making sure they don’t get frustrated in the first place.</p>

<p>Getting there means using a combination of skills to create a site with the <a href="http://www.penguinstorm.com/content_development/">right content,</a> <a href="http://www.penguinstorm.com/content-development/information_architecture.php">architecture</a> and visual design in order to achieve your goals.</p>

<p>Usability testing can and should be done prior to launch for any project. Like <a href="http://www.penguinstorm.com/project-management/quality_assurance_testing.php">Quality Assurance,</a> Usability Testing shouldn’t be thought of as the last step before your project is launched: it’s an iterative process that’s integral to the success of your project.</p>

<h3>First Launch: Building a Usable Site</h3>

<p>Our philosophy of improving usability reflects this: starting with low fidelity prototypes made with pencil and paper, the entire project is storyboarded. These storyboards are shared, reviewed and discussed. Changes are made where necessary. We use paper for lots of reasons - mostly because it's cheap, and easy to make changes.</p>

<p>All of this is the foundation for the visual design. Multiple concepts are built, reviewed, and tested. </p>

<p>One visual design is chosen and then revised until it’s ready for production.</p>

<p>If the development timeline and budget permit, an initial skeleton shell is prepared that allows users to interact with a text only version of the site. Essential graphical elements may be included in this test, but the point is to ensure that the site’s structure and content meet the needs of the target audience.</p>

<p>As the final product is assembled, users are tested using a task driven model to ensure that the site meets the defined standards.</p>

<h3>Usability Reviews &amp; Redesign</h3>

<p>Usability reviews can be done in a number of different ways ranging from simple  written reports based on analysis, online testing and surveying to sessions with web site users and participants. A detailed usability review will comment on all aspects of the site - <a href="http://www.penguinstorm.com/content_development/">content</a>, <a href="http://www.penguinstorm.com/content-development/information_architecture.php">architecture</a> and visual design. <a href="http://www.penguinstorm.com/contact/" title="Contact Us">Contact us</a> for details.</p>

<p><em>Deliverables.</em> Deliverables vary by project, but always include a usability analysis and report.</p>

<p><em>Rates.</em> Usability work starts at US$75 per hour. Fixed rates can be negotiated when sufficient project details are available.</p>]]>
        <![CDATA[<p>Usabilty is a simple concept with powerful possibilities: the success of the <a href="http://www.apple.com/ipod/">iPod</a> is probably the best example. Understanding how to make <em>usable software</em> can be a critical factor in the success of your project.</p>]]>
    </content>
</entry>

<entry>
    <title>Quality Assurance &amp; Testing</title>
    <link rel="alternate" type="text/html" href="http://www.penguinstorm.com/project_management/quality_assurance_testing/" />
    <id>tag:www.penguinstorm.com,2005://6.1692</id>

    <published>2005-10-17T16:18:12Z</published>
    <updated>2007-09-30T00:59:22Z</updated>

    <summary>Everyone remembers an old Ford slogan that said &quot;Quality is Job 1&quot; The problem is, Honda and Toyota made better cars.
Quality software doesn&apos;t just happen - it takes hard work. An iterative Quality Assurance plan is a important part of getting this done. Waiting until your project is done to look for bugs means risking your entire launch date. Don&apos;t take that risk.</summary>
    <author>
        <name>Skot Nelson</name>
        
    </author>
    
        <category term="Project Management" scheme="http://www.sixapart.com/ns/types#category" />
    
    
    <content type="html" xml:lang="en-us" xml:base="http://www.penguinstorm.com/">
        <![CDATA[<p>Quality Assurance &amp; Testing are often viewed as the final steps in the software development process – catching bugs. Positioning these functions in this way ignores the critical role they play in getting your project completed on time and budget.</p>

<p>Quality Assurance is a continual process that plays an important role in ensuring your project is completed on time. By working with the development team in an iterative process, Quality Assurance helps to eliminate the last minute bug hunt that so many projects suffer from.</p>

<p><em>Deliverables</em> Exact deliverables depend on the nature of the project, but a minimum of one QA report per week should be expected. This report will detail all issues addressed during the previous week.</p>

<p><em>Rates</em> Quality Assurance &amp; Testing work can starts at US$50 per hour.</p>]]>
        <![CDATA[<p>Quality assurance isn't about catching bugs just before release - it's about preventing them from happening in the first place.</p>]]>
    </content>
</entry>

<entry>
    <title>Project Specification Development</title>
    <link rel="alternate" type="text/html" href="http://www.penguinstorm.com/project_management/project_specification_developm/" />
    <id>tag:www.penguinstorm.com,2005://6.1691</id>

    <published>2005-10-17T16:17:23Z</published>
    <updated>2007-09-30T00:59:22Z</updated>

    <summary>A good project specification can be the key to success. Your specification needs to define the project scope, the development environment, the content needs and manage risk - all at the same time.
We can help you build a bullet proof specification that will make sure your final product is exactly what you wanted it to be.</summary>
    <author>
        <name>Skot Nelson</name>
        
    </author>
    
        <category term="Project Management" scheme="http://www.sixapart.com/ns/types#category" />
    
    
    <content type="html" xml:lang="en-us" xml:base="http://www.penguinstorm.com/">
        <![CDATA[<p>A detailed project specification is your best defense against the software death spiral – the one that means your project either finishes late and over budget, or on time without all the features you needed.</p>

<p>An accurate project plan starts with an accurate project specification. </p>

<h3>What Makes a Good Specification</h3>

<p>A good specification includes both the necessary technical details and the necessary business details. Technical specifications and restrictions define the parameters within which the project will operate – this can include your existing hardware and software environment and any necessary interfaces it provides, or the parameters within which you would like to operate in a future environment (i.e. "use only freely available Open Source" software or "must be compatible with Microsoft Internet Explorer 5 and higher and Apple's Safari 1.3 or higher.)</p>

<p>Sniffing out the necessary business requirements means working with your staff to determine what elements of your business are, and are not, relevant to the project at hand. Missing details will inevitably lead to unexpected project costs when these features have to be added in at a later date – at great cost.</p>

<p>Preparing a good specification document means working with your staff and understanding what developers need to know – we can handle both of these.</p>

<p><em>Deliverables.</em> Detailed project technical specification. Detailed project outline and corresponding supporting documents as necessary (i.e. <span class="caps">ERD,</span> Software Flow Chart.) Risk document, outlining the perceived potential risks of the project that will need to be tracked.</p>

<p><em>Rates.</em> Complete project specification documentation can be prepared at rates from US$75 per hour. Fixed rates are available by negotiation.</p>]]>
        <![CDATA[<p>The rule in design has always been "What you see is what you get". In software, the trick is making sure that <em>"What You Get Is What You Expected."</em></p>]]>
    </content>
</entry>

<entry>
    <title>Proposal Writing &amp; Editing</title>
    <link rel="alternate" type="text/html" href="http://www.penguinstorm.com/project_management/proposal_writing_editing/" />
    <id>tag:www.penguinstorm.com,2005://6.1690</id>

    <published>2005-10-17T02:23:14Z</published>
    <updated>2007-09-30T00:59:22Z</updated>

    <summary>Writing solid proposals can make or break your business. We can help you win new business while you stay focused on your current work.</summary>
    <author>
        <name>Skot Nelson</name>
        
    </author>
    
        <category term="Project Management" scheme="http://www.sixapart.com/ns/types#category" />
    
    
    <content type="html" xml:lang="en-us" xml:base="http://www.penguinstorm.com/">
        <![CDATA[<p>Proposals are one of the most important documents any business can produce. A well written proposal can win unexpected new business and garner referrals; a poorly written one can not only impact your future business, it can also impact your current business. by causing you to lose focus.</p>

<p>Stay focused on what matters today and let us help you with your future.</p>

<h3>Proposal Writing</h3>

<p>Responding to <span class="caps">RFP</span>s can be a lot of work and shift your focus from current work. Contracting out the response process can keep your available resources focused on current projects, in addition to offering other advantages.</p>

<p><strong>An Outside Perspective.</strong> It’s easy to lose sight of how the agency receiving your <span class="caps">RFP </span>perceives you. By bringing an outside perspective to the <span class="caps">RFP </span>process, gain a valuable perspective on issues that may have a dramatic effect on your proposal.</p>

<p><strong>Client Side Insight.</strong> Our past experience as a purchaser of software development services means we understand what your clients are looking for. Put this experience to work for your business today.</p>

<p><em>Deliverables.</em> Final <span class="caps">RFP </span>document, proofed and edited. Delivered in <span class="caps">PDF </span>and MS Word format.</p>

<p><em>Rates.</em>  Proposal writing starts at US$50 per hour. Fixed rates are available. <a href="http://www.penguinstorm.com/contact/">Contact us</a> with details.</p>

<h3>Editing</h3>

<p>A final edit and review can be invaluable by itself. Our editing services give your proposal that final level of polish it needs to be perfect.</p>

<p>Preparing your proposal means an almost endless number of times reading and rewriting. Bringing a fresh set of eyes in for a final review can catch errors that have been missed by tired eyes.</p>

<p>Have you ever submitted a proposal based on a template &amp; forgotten to replace a company name? Avoid embarrassing mistakes like this with an editing review.</p>

<p><em>Deliverables.</em> Edited, marked up copy of your proposal (either in MS Word format, or edited on paper.) Recommendations document providing realistic ways to improve the proposal document.</p>

<p><em>Rates.</em> Editing alone begins at US$40/hour. Requests can be accommodated with as little as 24 hours notice, and a 24 hour turnaround is possible on proposal documents less than 100 pages in length. </p>]]>
        <![CDATA[<p>A good proposal means new, profitable business. Mistakes can be costly - including the wrong company name, typos, and poor langage use all make your company look unprofessional and disorganized.</p>]]>
    </content>
</entry>

<entry>
    <title>Project Planning</title>
    <link rel="alternate" type="text/html" href="http://www.penguinstorm.com/project_management/project_planning/" />
    <id>tag:www.penguinstorm.com,2005://6.1689</id>

    <published>2005-10-11T22:55:55Z</published>
    <updated>2007-09-30T00:59:22Z</updated>

    <summary>You wouldn&apos;t start framing a house without a plan - why are you starting your software project without one? A good plan is a multi-faceted document that helps you keep your project on track, while recognizing the need to remain responsive to key project stakeholders.
We can help get you from start to finish.</summary>
    <author>
        <name>Skot Nelson</name>
        
    </author>
    
        <category term="Project Management" scheme="http://www.sixapart.com/ns/types#category" />
    
    
    <content type="html" xml:lang="en-us" xml:base="http://www.penguinstorm.com/">
        <![CDATA[<p>Good planning is the only sure way to avoid the software death spiral – the one that means you either complete your project late, strip features, or go way over budget. The one that means no one’s happy with the end result.</p>

<p>Properly planned software means a few things.</p>

<h3>Setting Appropriate Expectations</h3>

<p>Defining the scope of the project sets expectations from the outset – don’t make promises you can’t keep, and make sure that people aren’t expecting features can’t get built.</p>

<h3>Setting Realistic Timeframes</h3>

<p>Missed timelines are a common problem that doesn’t have to happen. A good plan breaks the project into manageable, meaningful steps so that accurate timelines can be planned from day one.</p>

<h3>Defining The Project Team</h3>

<p>All projects – big or small – have important roles that need to be filled. The size and scope of these roles can vary from project to project, but they need to be identified in order to succeed.</p>

<p>It’s far too easy, and far too common, for good planning to be left too late – it’s too easy to get excited and just start coding. Avoid disappointment by getting organized first.</p>

<p>Our project planning process means working with you to develop a plan that works for everybody.</p>

<p><em>Deliverables.</em> Project plan document. Project timeline document. Project cost estimate.</p>

<p><em>Rates.</em> Project planning is ordinarily done on an hourly basis, at a rate of US$75/hour. Fixed rates are available.</p>]]>
        <![CDATA[<p><strong>All</strong> projects require planning, not just big ones. Small ones just need less of it.</p>]]>
    </content>
</entry>

<entry>
    <title>Documentation</title>
    <link rel="alternate" type="text/html" href="http://www.penguinstorm.com/project_management/documentation/" />
    <id>tag:www.penguinstorm.com,2005://6.1688</id>

    <published>2005-10-11T22:55:18Z</published>
    <updated>2007-09-30T00:59:22Z</updated>

    <summary>This documentation isn&apos;t important? Think again - it&apos;s an insurance policy for your software investment.
Without documentation, changes and future additions to your site are going to cost more than they need too. Documentation is the foundation on which your software is built.</summary>
    <author>
        <name>Skot Nelson</name>
        
    </author>
    
        <category term="Project Management" scheme="http://www.sixapart.com/ns/types#category" />
    
    
    <content type="html" xml:lang="en-us" xml:base="http://www.penguinstorm.com/">
        <![CDATA[<p>A project without documentation paints you into a corner –- losing a developer can set your timelines back by weeks or months while others struggle to catch up on work already done but not documented. Documentation takes many forms, but it should always exist. Documentation can take a number of forms.</p>

<h3>Inline Code Documentation</h3>

<p>All code should be documented, and standards exist to define this. You should make sure developers are doing this documentation as the work is done, but better late than never.</p>

<h3>User Documentation (Online Help, Manuals)</h3>

<p>Developing custom software solutions can be costly – good user documentation is a critical component of software success.</p>

<p>User documentation can mean online help, printed manuals, and detailed training materials or a combination of all of these.</p>

<h3>Technical Documentation</h3>

<p>By the time a project is complete, the original project specification has often flexed and changed. The technical documentation process updates the project specification and creates a valuable detailed record of all technical aspects of the project.</p>

<p><em>Deliverables.</em> Completed, edited documentation in digital format. (Format to be specified in project plan.) Printing can be arranged at additional cost.</p>

<p><em>Rates.</em> Documentation can be prepared on an hourly basis, or can be included in a larger project at a fixed rate.</p>]]>
        <![CDATA[<p>Documentation isn't an afterthough. Good documentation is as important as good code, if not more so.</p>]]>
    </content>
</entry>

<entry>
    <title>Contact Us</title>
    <link rel="alternate" type="text/html" href="http://www.penguinstorm.com/contact/contact_us/" />
    <id>tag:www.penguinstorm.com,2005://6.1687</id>

    <published>2005-10-11T21:03:21Z</published>
    <updated>2007-09-30T03:50:00Z</updated>

    <summary>Email skot@penguinstorm.com for information about how we can help. Call 206.629.8735 You can also reach us on Skype at skot.nelson...</summary>
    <author>
        <name>Skot Nelson</name>
        
    </author>
    
        <category term="contact" scheme="http://www.sixapart.com/ns/types#category" />
    
    
    <content type="html" xml:lang="en-us" xml:base="http://www.penguinstorm.com/">
        <![CDATA[<p><a href="mailto:%73%6B%6F%74%40%70%65%6E%67%75%69%6E%73%74%6F%72%6D%2E%63%6F%6D">Email skot@penguinstorm.com</a> for information about how we can help. </p>

<p>Call 206.629.8735</p>

<p>You can also reach us on <a href="http://www.skype.com/">Skype</a> at skot.nelson</p>]]>
        
    </content>
</entry>

<entry>
    <title>We Make Technology Beautiful</title>
    <link rel="alternate" type="text/html" href="http://www.penguinstorm.com/introduction/we_make_technology_beautiful/" />
    <id>tag:www.penguinstorm.com,2005://6.1686</id>

    <published>2005-10-11T19:49:56Z</published>
    <updated>2007-09-30T00:59:22Z</updated>

    <summary>Business has changed. Business used to be done by people, not computers. Services that used to move are now just bits and bytes being transmitted through wires. Clear communication has become more important than ever. Technology Doesn&apos;t Have to be...</summary>
    <author>
        <name>Skot Nelson</name>
        
    </author>
    
        <category term="Introduction" scheme="http://www.sixapart.com/ns/types#category" />
    
    
    <content type="html" xml:lang="en-us" xml:base="http://www.penguinstorm.com/">
        <![CDATA[<p><strong>Business has changed.</strong> Business used to be done by people, not computers. Services that used to move are now just bits and bytes being transmitted through wires.</p>

<p>Clear communication has become more important than ever.</p>

<h2>Technology Doesn't Have to be Impersonal</h2>

<p>"Technology is Impersonal" is a common refrain. Not so.</p>

<p>People have very intimate relationships with their personal technology. Well designed online tools can build these same kind of strong realtionships with your customers.</p>

<h2>How We Can Help</h2>

<p>We get things built. We help you understand. We help your customers get things done.</p>

<p>We make technology that works. <em>We make your technology beautiful.</em></p>]]>
        
    </content>
</entry>

<entry>
    <title>content development</title>
    <link rel="alternate" type="text/html" href="http://www.penguinstorm.com/content_development/" />
    <id>tag:www.penguinstorm.com,2005://6.1685</id>

    <published>2005-10-10T20:39:08Z</published>
    <updated>2007-09-30T00:59:21Z</updated>

    <summary>People used to say content was king: in 10 years of building online work, a lot has changed and a lot of lessons have been learned. At the end of the day, though, good content is still one of the...</summary>
    <author>
        <name>Skot Nelson</name>
        
    </author>
    
    
    <content type="html" xml:lang="en-us" xml:base="http://www.penguinstorm.com/">
        <![CDATA[<p>People used to say content was king: in 10 years of building online work, a lot has changed and a lot of lessons have been learned. At the end of the day, though, good content is still one of the most important aspects of your web site.<br />
Good content, means well written, well edited, well structured content. Keeping things short is good, but only if you get your core message across.<br />
Good content is the most important step in making sure that your site is Search Engine Optimized. Google search algorithms change without warning, but well written</p>]]>
        
    </content>
</entry>

</feed>
