|
From: <wol...@us...> - 2002-08-25 11:57:15
|
Update of /cvsroot/subtrick/TiTan/doc/design In directory usw-pr-cvs1:/tmp/cvs-serv23764/doc/design Added Files: Work Policy.htm Log Message: TiTan OS Group Policy --- NEW FILE: Work Policy.htm --- <html xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:st1="urn:schemas-microsoft-com:office:smarttags" xmlns="http://www.w3.org/TR/REC-html40"> <head> <meta http-equiv=Content-Type content="text/html; charset=windows-1252"> <meta name=ProgId content=Word.Document> <meta name=Generator content="Microsoft Word 10"> <meta name=Originator content="Microsoft Word 10"> <link rel=File-List href="Work%20Policy_files/filelist.xml"> <title>Dear group , </title> <o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="date"/> <!--[if gte mso 9]><xml> <o:DocumentProperties> <o:Author>Amgad Madkour</o:Author> <o:Template>Normal</o:Template> <o:LastAuthor>Amgad Madkour</o:LastAuthor> <o:Revision>2</o:Revision> <o:TotalTime>9</o:TotalTime> <o:Created>2002-08-25T11:40:00Z</o:Created> <o:LastSaved>2002-08-25T11:40:00Z</o:LastSaved> <o:Pages>1</o:Pages> <o:Words>1259</o:Words> <o:Characters>7178</o:Characters> <o:Company>Madkour</o:Company> <o:Lines>59</o:Lines> <o:Paragraphs>16</o:Paragraphs> <o:CharactersWithSpaces>8421</o:CharactersWithSpaces> <o:Version>10.2625</o:Version> </o:DocumentProperties> </xml><![endif]--><!--[if gte mso 9]><xml> <w:WordDocument> <w:SpellingState>Clean</w:SpellingState> <w:GrammarState>Clean</w:GrammarState> <w:Compatibility> <w:BreakWrappedTables/> <w:SnapToGridInCell/> <w:WrapTextWithPunct/> <w:UseAsianBreakRules/> </w:Compatibility> <w:BrowserLevel>MicrosoftInternetExplorer4</w:BrowserLevel> </w:WordDocument> </xml><![endif]--><!--[if !mso]><object classid="clsid:38481807-CA0E-42D2-BF39-B33AF135CC4D" id=ieooui></object> <style> st1\:*{behavior:url(#ieooui) } </style> <![endif]--> <style> <!-- /* Style Definitions */ p.MsoNormal, li.MsoNormal, div.MsoNormal {mso-style-parent:""; margin:0in; margin-bottom:.0001pt; mso-pagination:widow-orphan; font-size:12.0pt; font-family:"Times New Roman"; mso-fareast-font-family:"Times New Roman";} a:link, span.MsoHyperlink {color:blue; text-decoration:underline; text-underline:single;} a:visited, span.MsoHyperlinkFollowed {color:purple; text-decoration:underline; text-underline:single;} span.SpellE {mso-style-name:""; mso-spl-e:yes;} span.GramE {mso-style-name:""; mso-gram-e:yes;} @page Section1 {size:8.5in 11.0in; margin:1.0in 1.25in 1.0in 1.25in; mso-header-margin:.5in; mso-footer-margin:.5in; mso-paper-source:0;} div.Section1 {page:Section1;} --> </style> <!--[if gte mso 10]> <style> /* Style Definitions */ table.MsoNormalTable {mso-style-name:"Table Normal"; mso-tstyle-rowband-size:0; mso-tstyle-colband-size:0; mso-style-noshow:yes; mso-style-parent:""; mso-padding-alt:0in 5.4pt 0in 5.4pt; mso-para-margin:0in; mso-para-margin-bottom:.0001pt; mso-pagination:widow-orphan; font-size:10.0pt; font-family:"Times New Roman";} </style> <![endif]--> </head> <body lang=EN-US link=blue vlink=purple style='tab-interval:.5in'> <div class=Section1> <p class=MsoNormal>Dear <span class=GramE>group ,</span> </p> <p class=MsoNormal> </p> <p class=MsoNormal>* As we can all see we are having a serious problem in coordinating the work being <span class=GramE>done ,</span> and also we are facing a lack of team work in some parts , so here is a suggestion of a policy ..</p> <p class=MsoNormal> </p> <p class=MsoNormal>******************************************************</p> <p class=MsoNormal> </p> <p class=MsoNormal>Meetings:</p> <p class=MsoNormal>----------</p> <p class=MsoNormal> </p> <p class=MsoNormal>1. Group would meet 3 days a week , suggested (sat , mon , wed ) as if people wanna travel on Thursday its ok , one of the 3 specified days would be a day were we all meet together ALL DAY , most probably at the moment would be ( Univ , Adhams new place , my house ) . The other two days would be discussing what has been done and assigning tasks to the rest of the developers. FAILIUR TO COME WOULD BE RESPONSIBILITY OF THE PERSON.</p> <p class=MsoNormal> </p> <p class=MsoNormal>2. Meetings would discuss what progress has been <span class=GramE>done ,</span> each member would have a paper written on it a report of what he has done. The paper would be hand written or printed as wished .THIS IS EXTREAMLY IMPORTANT.</p> <p class=MsoNormal> </p> <p class=MsoNormal>3. Each member would be assigned the task of writing down in each meeting what has been said in general besides his personal notes and his <span class=GramE>tasks ,</span> that is beside a member who will log all our main points and put it on the web site as a reminder to all members.</p> <p class=MsoNormal> </p> <p class=MsoNormal>4. If a member fails to attend a meeting it is his responsibility to know what has been done either by entering the web site and reading the notes or contacting the team leader to know what to <span class=GramE>do .</span> FAILURE TO DO SO WOULD RESULT IN CUMMULATIVE WORK ON THAT MEMBER.</p> <p class=MsoNormal><span class=GramE>Leading team leader to take appropriate measures with that member.</span></p> <p class=MsoNormal> </p> <p class=MsoNormal>5. Meetings with Dr. <span class=SpellE>Ibrahim</span> would be made every Wednesday (if appropriate ) to discuss what has been done , and weekly report would be presented by the team leader , and parts done would be explained by members to the Dr. . Also meeting would be made even if small progress is <span class=GramE>done ,</span> just to keep updates as much as possible</p> <p class=MsoNormal> </p> <p class=MsoNormal>6. Concerning the topic that some members would like to meet and sit together more would be applied 1 day <span class=GramE>only ,</span> this is because each person can have better time with himself with his system , this will not prevent him from coordinating his work with the rest because he will be assigned a specific task which will NOT DEPEND ON THE REST . <span class=GramE>this</span> would be managed by the team leader , still we will meet once a week together ALL DAY LONG. <span class=GramE>if</span> a task would depend on the rest then this part would be done at that very day of meeting of all the group . If a member feels he will need more help then he can just lookup info on the net or post his <span class=GramE>questions .</span> </p> <p class=MsoNormal> </p> <p class=MsoNormal>7. It is the members responsibility to put himself on track of <span class=GramE>work .</span> He may ask for help from the team leader or any other member to DIRECT HIM ONLY to what he should be reading or do , this would REALY help the member on understanding everything more than a suffer to him . Members would give help but not <span class=GramE>teach .</span> Even after all of that a member feels he is still not happy he can gather his questions and ask us in the group <span class=GramE>meeting .</span></p> <p class=MsoNormal> </p> <p class=MsoNormal> </p> <p class=MsoNormal> </p> <p class=MsoNormal>Members Tasks <span class=GramE>And</span> Work Progress:</p> <p class=MsoNormal>----------------------------------------------</p> <p class=MsoNormal> </p> <p class=MsoNormal>1. Each developer is responsible to fully understand his work during the <span class=GramE>meeting ,</span> he must be assured that he understands his task very well , and if the tasks are shared among many members , he must know his part very well from the team leader of the task.</p> <p class=MsoNormal> </p> <p class=MsoNormal>2. Each task will be assigned a DEADLINE in which it has to be done <span class=GramE>in .</span> Each developer is responsible to deliver his work on <span class=GramE>time ,</span> excuses such as traveling and busy would be ONLY ACCEPTED AT EXTREM LEVELS in which the work would be cumulated on the developer . If the team leader feels that this developer is not working YET properly then he has the right to deal with <span class=GramE>him ,</span> and I mean by that suggest the removal of such member . <span class=GramE>with</span> all respects to all members , this project needs WORK and TIME.</p> <p class=MsoNormal> </p> <p class=MsoNormal>3. If a specified task would take more time than required then the developer can send an e-mail from the team leader requesting more time and specifying in points the <span class=GramE>reasons .</span> It would be only the team leader who would accept such an excuse.</p> <p class=MsoNormal> </p> <p class=MsoNormal>4. Any questions regarding code or syntax would be posted on the message board in order to share the answers among <span class=GramE>members ,</span> even if the question is silly , we are here to learn . </p> <p class=MsoNormal> </p> <p class=MsoNormal>5. Each developer is required to mail his progress EACH FRIDAY in order to discuss it on Saturday , The mail IS A MUST to send and is gathered by the team leader in order to give him a chance to make points about, and bought by each developer to be discussed next day .EVEN IF HE SENDS A BLANK MAIL . <span class=GramE>just</span> show you are doing something .</p> <p class=MsoNormal> </p> <p class=MsoNormal>6. As we know now we have a web <span class=GramE>site ,</span> <a href="http://www.titanos.net">www.titanos.net</a> thanks to <span class=SpellE>adham</span> who managed to get it for us , now there will be a member responsible of making sure to put all logs of the meetings with the date meeting and notes on the web site. <span class=GramE>also</span> it would be his responsibility to always update the documentation section of the web site with the documentation inside the CVS. THIS IS VERY IMPORTANT TO KEEP ALL ATTENDING AND NON ATTENDING MEMBERS UP TO DATE ABOUT MEETINGS AND <span class=GramE>WORK .</span></p> <p class=MsoNormal> </p> <p class=MsoNormal>7. Also a member would be having the time schedule of task each meeting saying what has to be done and what has been <span class=GramE>done .</span> it is advised that he would be the same member of the web site as he would also include the same schedule on the net , meaning a section in the web site would include the schedule we are doing and things to be done and by which members.</p> <p class=MsoNormal> </p> <p class=MsoNormal>8. Progress and tasks can be assigned by all members and the team leader is the one who should manage the timings and coordination of work among members.</p> <p class=MsoNormal> </p> <p class=MsoNormal>9. Any changing of the basic structure of the OS or design issue HAS TO BE DISCUSSED WITH THE REST before it is done in order to take agreements on that subject. </p> <p class=MsoNormal> </p> <p class=MsoNormal><span class=GramE>10 .</span> Concerning the Documentation of the <span class=GramE>work ,</span> <span class=SpellE>i</span> would like to suggest a policy of our work , that would help ALL of us to understand every little thing done in the project . The policy is <span class=GramE>simple ,</span> every developer would be responsible of documenting the topic he is writing about and the Code he is writing . This would really help all the members a lot to understand and learn and <span class=SpellE>i</span> think it is a CRITICAL thing to <span class=GramE>do .</span> <span class=GramE>iv</span> attached an example of what <span class=SpellE>i</span> mean .</p> <p class=MsoNormal> </p> <p class=MsoNormal> </p> <p class=MsoNormal>Team Leader <span class=GramE>Tasks :</span></p> <p class=MsoNormal>------------------------</p> <p class=MsoNormal> </p> <p class=MsoNormal>1. It is the team <span class=GramE>leader 's</span> task to assure that development is up to date , and to be up to date with the rest of the group either via e-mail or phone . </p> <p class=MsoNormal> </p> <p class=MsoNormal>2. Team leader is the one who confronts Dr. <span class=SpellE>Ibrahim</span> as the one responsible for the current progress and for the material presented to Dr. <span class=SpellE><span class=GramE>Ibrahim</span></span><span class=GramE> .</span> he is the one responsible for the members and the members work , and in case of lack of work of certain member , would inform the Dr. to clear his hand from that matter in the worst cases ( hopefully we dont want that to happen do we ! ) </p> <p class=MsoNormal> </p> <p class=MsoNormal>3. Team Leader has to write the Weekly report of the progress done by collecting all the work from the rest of the group and delivering it to Dr. <span class=SpellE><span class=GramE>Ibrahim</span></span><span class=GramE> .</span> <span class=GramE>and</span> it is the every developers responsibility to explain what he has done to the dr. on the day of the meeting . </p> <p class=MsoNormal> </p> <p class=MsoNormal> </p> <p class=MsoNormal>4. It is the team leader responsibility to manage the brain dumps done in the meeting of the <span class=GramE>members .</span> He should manage the meeting ideas and discuss them so that we may have many <span class=GramE>ideas .</span></p> <p class=MsoNormal> </p> <p class=MsoNormal> </p> <p class=MsoNormal> </p> <p class=MsoNormal>************************************************************</p> <p class=MsoNormal> </p> <p class=MsoNormal> </p> <p class=MsoNormal> </p> <p class=MsoNormal>In the end <span class=SpellE>i</span> tried to layout the important points that may be raised by <span class=GramE>members ,</span> and <span class=SpellE>i</span> hope <span class=SpellE>i</span> covered most .</p> <p class=MsoNormal> </p> <p class=MsoNormal>Now this policy is JUST A SUGGESTION that <span class=SpellE>i</span> <span class=GramE>proposed ,</span> please send from your account a REPY on this mail with your notes and points you would like to add . <span class=GramE>by</span> this <span class=SpellE>i</span> mean all members <span class=SpellE>Adham</span> , <span class=SpellE>Ayman</span> , Mohamed and <span class=SpellE>Emad</span> . This reply is not optional but it is a must from all <span class=GramE>members ,</span> saying you agree or not and what points you dont agree on and which points you want to add . <span class=SpellE><span class=GramE>im</span></span> expecting a reply soon ESA , <span class=SpellE>i</span> know that some points may be hard but its a must to boost development in summer so that we dont get stuck by the start of the year ... if the policy is agreed upon it would begin progress from <st1:date Month="11" Day="8" Year="2002">Monday 11/8/2002</st1:date> . </p> <p class=MsoNormal> </p> <p class=MsoNormal> Thank you for reading</p> <p class=MsoNormal> Awaiting Your Reply</p> <p class=MsoNormal> Amgad </p> <p class=MsoNormal> </p> <p class=MsoNormal> </p> <p class=MsoNormal><o:p> </o:p></p> </div> </body> </html> |