Home

Central Station's goal is to simply the workflow that developers and managers go through with Agile web development. At times Central Station provides rules and structure to optimize Developer Happiness.

Projects

Projects should be fluid. Requirements change, and this is a good thing. However, as requirements change tasks/stories should be interchanged and swapped. Central Station will enforce this concept by locking down sprints, and only allowing tasks/stories to be swapped of equal value.

Projects should be open and accessible to as many users as possible. Everyone who has a user account in Central Station can view open projects and their tasks. It is important for Clients and decision makers to be able to view the iteration/sprint and see what things are working and what things aren't.

Transparency

There is no such thing as a closed beta for clients. Clients should be able to see progress at any given moment and not be forced to wait through an iteration before seeing progress. However, this does not mean that a Client has direct access to a developer. Central Station ensures that their feed back is ported directly to the Iteration Manager/Business Analyst and not to the developer.

All projects have an accessible API.

Roles

Developer
Analyst/Iteration Manager/Scrum Manager
Department Supervisor
Client
Superuser/Administrator

Sprints

Sprints can be two weeks or two months. Any date range will work, and its important that what works for one team, wont' work for another. Some projects need longer sprints to accomplish complete working code.

Project Management

Central Station takes a hands off approach to project management in the sense that it does not direct you to handle clients in any specific way. Central Station will keep sprints and tasks with a heavy hand yet.