Kwoosh’s take on project management is slightly different than most current systems. Our core thesis is that software project management shouldn’t much differ from project management used for building an airplane or a rocket. I don’t think Waterfall is making a comeback, but rather, using aWork Breakdown Structure(WBS) is the best way to get an accurate feel for the size of the project and the work required.
Using a WBS, you take a given project and divide it into smaller and smaller pieces of work until it no longer makes sense. When it no longer makes sense to divide a task, you should be able to confidently estimate how long it will take to complete. If you are estimating that a single task will take longer than an hour or two, it’s likely that you haven’t broken your task down into indiviual actions. It’s this lack of breaking down tasks sufficiently that leads to incorrect estimates, as you have not fully thought through the problem.
Since apps are naturally divided by screen and sub-screens, Kwoosh uses screens as the primary way to organize your project. To illustrate this concept we’ve built a number of pages that show how your team can use Kwoosh to manage different kinds of software projects.
So far we have three examples:How to Build a Brochure Website,Building a Desktop App, andBuilding a Mobile App. On each page we set the stage with a project brief, break down each project into its deliverable views, and show how it looks when managed by Kwoosh.
My aim is that by showing people what it looks like to use Kwoosh on these kinds of projects, they will imagine how it would apply to their own andgive Kwoosh a spin