Well before contract, we’re often faced with project inputs that are astonishingly vague. Even RFP’s that can go on for dozens of pages, often miss critical big picture details related to legacy systems, and outline comparably nebulous descriptions of new deliverables. As account, bizdev, and pm leads, if we’re crafty, and a bit lucky, we might successfully parse and interpret these documents to the point of defining a reasonably satisfactory scope of work.

Do these statements create stress in your day and projects? This project is way over budget. We are never going to make the deadline. Client expectations are not being met. That is out of scope. Estimates are being blown. It is in the project plan. It’s not in the SOW.

Every developer has at least one or two ideas in their head about something they want to offer to the world.

Good software development has a codified process with specific steps. Skip a step at your own peril.

Software Business Creation is exactly the same. It has a codified process with specific steps. Skip a step at your own peril.

There are tens of thousands of blogs and websites with generic information on how to start a business. The problem is not a lack of information. The problem is too much information geared at a generic crowd without context.

This training session will look at key considerations faced by project managers as they go through the web development process. We'll cover the initiation, planning, execution, monitoring and ongoing maintenance of projects. We'll talk about how different aspects of a CMS affect scope, risks, resources and budgets, and about some unexpected measures of quality. We'll focus primarily on agile project management, however waterfall and hybrid approaches will be discussed.