Our project management structure is composed 

of several core items. These items work to 

enumerate and establish top-level components 

guiding all levels of development. 

We start by first capturing all vision & goals, opportunities & challenges, then prioritizing them.     A practice that ensures visibility to the entire team.

Each documented item is displayed hierarchically in a production calendar, allowing to quickly observe all Initiatives, view a particular Initiative and its Tasks through a Kanban Board.

Kanban is a new technique for managing software development in a highly efficient way, with roots in Toyota's "just-in-time" production system.               Activated via a pipeline whereby an informal ad hoc process is blended with a highly formal phased process, it allows for the agents of change to be included without the creation of bottlenecks.

HOW KANBAN WORKS

The classic Kanban is characterized with cards on large visible board, placed in columns displayed vertically and horizontally. A Project can be updated and it's Cards can reflect all changes, as they flow through a development cycle.  

HOW KANBAN WORKS

Each Board can be architected to reflect the existing protocol and procedures, highlight potential bottlenecks and the amount of work-in-progress at each step. For instance columns in a vertical board could be titled as PENDING, DOING, DONE.                                                                       SAMPLE HERE

AGENTS OF CHANGE                                                                              

Each Card can be architected to reflect the changing needs of each task and it's influence on other Card's completion. The visual nature of each card will display it's progress as the card moves from each column; which again manages bottlenecks and activates attention that inform leaders dynamically.  

AGENTS OF CHANGE

Everyone's bandwidth can be observed, helping support the availability of a team member's work protocol. This allows for collaboration between leadership, a key need that helps transact progress effectively.  

AGENTS OF CHANGE

Each initiative is defined and organized by the following set of properties, which inform it's goals from a top-level perspective  first by our client.   

WE LISTEN & DOCUMENT   

• Title 
  
• Description 
  
• Goals 
  
• Checklist 
  
• Category 
  
• Associated Initiatives 
  
• Status - Implemented by Swimming Lanes 
  
• Proposed Start Date 
  
• Due Dates 
  
• Priority 
  
• Assessment 
  
• Archive / History 
  
• List of Tasks 
  
• Membership 
  
• Email Alerts & Rss Feeds 
  

Each task will be organized with a similar set of properties from the same Kanban board. A creative brief will be furnished noting each task's objectives, whom it will be tasked to, deadlines, etc. The properties of each task are often the same as initiatives, yet are more specific to heighten focus.                           

MORE LISTENING & DOCUMENTING : )   

• Title 
  
• Description 
  
• Status - Implemented by Swimming Lanes  
  
• Proposed Start Date 
  
• Creative Brief - this will be furnished for review.
• Owner of a Task

Let's begin with an iterative whiteboard spec.
The classic experience of documenting it on a whiteboard, sticky notes and pencil sketches         and all...

• what's the status of the application?
• what needs to be built out?
• what have been the problems to date?

• The work will be documented as a static document to ensure we are indeed correct with all assumptions

Phase 2:  Provide Sample of Documenation

• Based on client review, iterate forward and gain full acceptance. ( TBD ) 

Phase 3:  Client Feedback