Team Input vs. Collaboration

 

At times, as an FSR or Project is going through workflow process, Team Input or Collaboration may be required.  There is a subtle difference between the two.

 

Workflow is typically a linear chain progression of required actions within the software going from one step to another until the process is completed.  For example, if an approval process requires the review of three people, the process may be stopped by anyone in the progression by simply not approving it for whatever reason and that step cannot be bi-passed.   If approval is required to demonstrate due dilligence and approval is very likely, this is a desireable feature.  However for more complex interaction of parties to arrive at consensuse or concurrence, this is NOT a desireable feature.  PMweb offers two more interactive processes that provide concurrance and approvals but with less impact on workflow - Collaboration and Team Input.

 

Collaboration is a virtual "huddle" of invited people that come together within the software to view files, attachments, communicate with each other, offer opinions, cost information, etc.  Typically a project manager will invite selected individuals within an approval process to gain concessus.  This interaction is totally outside of the workflow process.  Collaboration is completely optional for the project manager but it would be wise to gain consensus prior to requesting approval from these parties.  There is no "approve" or "return" button for parties to click on.

 

Team Input is also a virtual huddle of invited people that can also view files and communicate, however a formal approval is required by all parties for the workflow to move forward.  The approval within Team Input is concurrent and not linear but the Team Input process itself is placed in the linear workflow chain.

 

 

Refer to a more detail description of Collaboration and Team Input.