Screen Shot



Project Screen                    
Following is a project screen of ChainOfAsker. Left portion is request and task parent-child tree and right portion is Gantt chart. 

  


Open ChainOfAsker ver3 (<= This is free service. So If you are interested in this approach, please try! )
To use ChainOfAsker, Please install Microsoft-Silverlight

Screen layout is similar to existing project management system but this project is planned through chained asking process. Numbered requests and tasks represent following three member's chained asking planning activity.
  1. Sales_John issued “Top Request” to himself with due date Oct-18. This is the start of project planning.
  2. Sales_John added his “Menu Consultation Task” by 3 days duration.
  3. Sales_John issued(asked) “Cooking Request” to ChefMac. 
  4. Sales_John set time relation(brown wave arrow in the Gantt Chart) from “Consultation Task” to “Cooking Request”.
  5. Chef_Mac accepted “Cooking Request” and created his “Cooking Task” by 3 days duration.
  6. Chef_Mac issued(asked) “Food Stuff Shopping Request” to ShopperJane.
  7. Chef_Mac set time relation from “Shopping Request” to “Cooking Task”.
  8. Shopper_Jane accepted “Food Stuff Shopping Request” and created her “Shopping Task” by 3 days duration.
Scenario of this project
John is a salesman of catering service company and he got 100 lunch delivery order. To conduct this order, he must determine lunch menu with customer, prepare food stuff, and cook. This Lunch project can be developed under the three user's cooperative planning activities listed above #1 to #8.
  • You can watch these 1 to 8 step by step project planning screen shot at How it works page.
  • You can watch ChainOfAsker screen operation to develop this lunch project by  "2/3 How to Plan" demo video.
  • You can develop this project structure by acting(or playing) Sales_John's role, Chef_Mac's role and Shopper_Jane's role under the  Tutorial mode of ChainOfAsker. For detail please refer to "section 3 Let's try 100 Lunch project" step by step operation learning course in the user's manual .
 

Request creation Screen
To create a new "Request", Please select a parent request which you want to add child request and select "Create Child request or Task" then we get new detail request tab to input what we want.

   
   Note: Request creation screen is after data is filled in.

It looks a lot of data to fill in but user input data is following 5 items (blue headers on above screen).
  1. Request title
  2. Request body (description of what you want)
  3. Status
  4. Due date (usually and default is "Auto" so no need to change)
  5. Helper to whom you ask
Like this way, we can create new request almost same manner when we ask something by e-mail.


Additional Information Screen
We can see "Post Additional Info" button on the previous detail request screen(#6 above screen) and additionally posted information at 10/07 titled  "Menu is selected"(#7 above screen).  This is the additionally posted menu information from Sales_John to Chef_Mac and Shopper_Jane.

Like this way, we can add information to original request.  Because it is common that request related information is not fully gathered or fixed when we ask something. Usually detail information has been fixed or created with a progresses of the project.  So this is the function to store these additionally created information with a original request. We can get content of the additional information(next screen shot) by clicking information title(#7 above screen).

  

We can designate a person who must read this information(#1 above screen) then "InfoToRead" notification is automatically listed on the designated user's Notification screen(see next screen right pane). So we can use this additional information both push style information sharing(Notification) and pull style (like electronic board) information sharing.


MyReq&Task Screen
This Screen consisted by following 2 pane
  • My Request and Task
    This pane lists up all login user's requests and  tasks. We can check or update user related request and task from here. Pasted screen shot is some data field but this screen provide same information which you can see on the project screen.

  • Notification from System
    This pane show system generated important notification to each user. We can get various notification like following.
  • When we get new request
  • When all pre-task are completed and login user's  task status changed to "CanDo"
  • When issued request is completed
  • due date -1 day, on due date, and over due date warning
  • When other person post a additional information which login user must read



How ChainOfAsker  Works on the MS-Silverlight platform
Following is a image diagram to show how ChainOfAsker works


  1. At start up, ChainOfAsker loads request and task data from your PC’s hard drive.
  2. Request and task data is stored in your PC’s memory and presented on the screen
  3. When user create new request or task or change data, changed request and task data is stored to user's PC memory.
  4. Periodically ChainOfAsker upload changed request and task and download other project related member changed request and task. So  even user's internet is slow, it does not slow down PC screen response. Because all your change is written to your PC memory and later it will be uploaded by background process.
  5. ChainOfAsker stores latest request and task data to your PC’s hard drive.
Isolated storage
This is Microsoft word for Silverlight application(=ChainOfAsker). This is special hard drive storage area which is provided under the approval of user. Silverlight application can use this area to store application data but Silverlight application can not access other HD area in user's PC.(this is a reason of “Isolated” naming ) By this restriction Silverlight application can not read(or steal) user's  data file. This is Silverlight system restriction to protect user's  data from bad Silverlight application. So when you get request from ChainOfAsker to allow to create isolated storage area, please respond OK.


What we can get by using ChainOfAsker
ChainOfAsker have following merit compare to the current e-mail(groupware) or project manager centric traditional project management system.
  • Compare to e-mail
    • No risk to be mistakenly erased
    • No need to search (like where is original request or where is update?)
    • No need to sorting(e-mail sorting by inbox folders )
    • We can enjoy various function which e-mail hasn't like scheduling, notification,progress monitoring

  • Compare to File server or Electronic board
    • We can store request related all information with the original request. So the project member can get all request related information at one place.
    • We can use this function for both push style information sharing like e-mail and passive information sharing like Electronic-Board or File-Server.
    • Chained asking is a process to organize the project team. So ChainOfAsker has built-in mechanism to create a secure information sharing group.
  • Compare to traditional project management system

































FREE PROJECT MANAGEMENT  FREE TASK MANAGEMENT Project management 2.0 Cooperative management Collaborative management Collaborative project management Participative  management scheduling Gantt chart groupware collaboration cooperation distributed project planning distributed project management

FREE PROJECT MANAGEMENT  FREE TASK MANAGEMENT Project management 2.0 Cooperative management Collaborative management Collaborative project management Participative  management scheduling Gantt chart groupware collaboration cooperation distributed project planning distributed project management

FREE PROJECT MANAGEMENT  FREE TASK MANAGEMENT Project management 2.0 Cooperative management Collaborative management Collaborative project management Participative  management scheduling Gantt chart groupware collaboration cooperation distributed project planning distributed project management







ą
doc usui,
Mar 22, 2010, 6:58 AM
Comments