If I had a dollar for every time a potential client told me how easy web development is, or asked me to estimate the re-development of a Facebook-like website after a ten minute phone call I could travel around the world for a couple months. It it was easy to estimate and develop web applications (or any IT project for that matter) over 60% of projects wouldn't fail.
Time and time again, we get the horror stories from companies who have started a web project with the best of intentions only to see it end in disaster. A successful project is not something that can just be lucked into; it takes various components that all must be managed properly for execution. No matter what the size of the organization, everyone struggles with the same problems; using our internal team or hiring a partner, how much budget is there for the project, when can we expect to see the end product, and array of other questions that all have to be answered.
Hopefully, if you’re making a decision on re-designing or building a new website for your company at least one of the criteria for selecting an agency is; 1. “Doe's the agency’s own web site reflect the same kind of results that are being proposed for your new website?" In other words, doe's the website design company or agency practice what they preach?
As Drupal becomes more popular and grows its open-source development community, more websites are turning to it as a solution for creating extremely powerful online communities, allowing users to submit their own content to a community hub. The power of these hubs is obviously their users and creating an organized, easy to use interface can be the difference between failure and success.
I have been working on a new whitepaper about how to become an online leader. One of the cornerstones is to use a strategic, agile process. While agile is not for every project, often it is by far the optimal process for web development. While many large development organization such as Microsoft, IBM, Google and Yahoo! use agile, very few companies that don’t do software development for a living are using it – particularly small and midsized businesses.
I've recently been researching the differences between content management systems and blogging engines and thought I would discuss some key differences I've found in Drupal and WordPress. LevelTen has experience installing, configuring and theming both and each has its strengths and weaknesses. I feel the deciding factors come down to your long-term goals for the application.
For those of you familiar with a traditional project management process, you’re probably familiar with a typical project life cycle- plan, budget, design, develop, test and release, AKA waterfall. This style of management can typically be found in fixed-bid projects. You may be less familiar with the percentage of projects that utilize this management process, yet fail to stay within the project’s intended time line, budget and scope.
According to the “Chaos Report”, a project management study on software development companies:
…35 percent of software projects started in 2006 can be categorized as successful, meaning they were completed on time, on budget and met user requirements. This is a marked improvement from the first, groundbreaking report in 1994 that labeled only 16.2 percent of projects as successful…
35 percent! Almost two out of every three software development or integration projects are failures. If you are not planning on selling services or merchandise on your site, collecting customer data or statistics, or updating site content via a content management system, you can probably rest assured your project will not be a total failure. However, if you are planning on utilizing any or all of these features into your website, I highly recommend you continue reading.
While there are 4 project life cycles adopted for software and web development, LevelTen primarily works within the Waterfall (also known as Serial) and Iterative cycles. While all project life cycles provide advantages and disadvantages, these two have been widely accepted and adopted by software, IT, and web companies alike.
For those of you familiar with a traditional project management process, you’re probably familiar with a typical project lifecycle- plan, budget, design, develop, test and release. You may be less familiar with the percentage of projects that utilize this management process, yet fail to stay within the project’s intended timeline, budget and scope.
According to the “Chaos Report”, a project management study on software development companies:
