IT Project Kwa Vitendo

mimi nawatakia kila lakheri wakuu, tunahitaji watu creative yaani waliosoma nakuelewa na sio kukariri. ninachofahamu IT ni ushindani na ubunifu mwingi, hinyo hata kama kuna project kama hiyo basi mnahitaji kuichallenge ili kupata ktu beta na kuweza kupiga hatua zaidi. mfano hao yellow page wamelala sana kwa sababu wamekosa mshindani wa kweli anayefanana na wao, so nyinyi mkiwachallenge kwa kubuni project inayofanana na yao pia na wao wataamka hinyo technologia itakuwa. mi niko nyuma yenu wakuu japo sina mchango mkubwa kwa hilo.
 
I hope Mtazamaji doesnt burst his head tryin come up wit a document plan.:tonguez:
Usijali, dont rush! :coffee:. Fanya kwa utulivu.
 
Ahsante kwa kazi yako. Good work. Kuna vitu umeweka nimevipenda, lakini sisemi vipi!:clap2:

Perhaps you could have add a methodology section in which you could have discussed about what methods we are going to implement in the development process (Waterfall, Spiral). May be, tools and technologies we are expecting to use, fore example PHP for scripting language.

Furthermore, we could have an activity plan. Do you have MS Project, so that you could draw proper Gantt Chart. The Schedule is very important, firstly because we need to spend less time as possible so that we do not lose focus and undermine our commitment. Secondly, it is a good lesson for time management. That is, writing an activity plan with each activity having its own deliverable and outcomes.

After having all that, we move to one of the important steps, requirement analysis.

In short, I think we have:

  • Planning
  • Requirement analysis
  • Design
  • Coding
  • Testing
  • Integrating
  • Implementing
  • Maintenance (Upgrades and Fixes)

​
 
1 PROJECT PLAN
This section describes the plan to implement an Online contact directory.

Preface
This is a simple plan for developing a simple Online contact directory .using technology and solution to be decided by Team members.

It provides the scope and context of the project to be undertaken. It details the intended user group and the value that the system will have to them. It also provides a schedule for the completion of the project, including a list of all the deliverables and resources required.

The intended audience of this document is the Team members participating in the project so that they can determine and review the best possible way to implement an online contact directory. It is an initial starting point and it will be change during the course of the project

Overview
Purpose Scope and Objective
The current Online Contact directory in Tanzania like Yellowpages are :-
• not usable , and lack even basic contact information of important organisation like Ministries, Regional Office , education , health services etc
• There is no interface to let people share their business contact and information.
• Nowadays there are many advances in Open source industry, and open source solution can provide cost effective and feasible solution

It assumed t cost of the project will be as minimal as possible and whenever possible open source solution and free hosting service should be priority.. Member will choose the best environment to implement the project

Assumptions and Constraints
It is assumed that the project will be complete within 4 months. Implementation strategy will be decided by members but Team leader have a veto and final say on any issue that member don't have agreement.
Team leader has a right to fire or hire any member for the benefit of the project.

Project Deliverables and Milestone
Deliverables include
• Web site
• Database to store contact information
• Documentation (Every member will be expected to provide a brief documentation of how they carried their task.

Schedule/Stages and Budget Summary
Schedule
Item:
1. Web & database Requirement specification and design
2. Solution selection( webhoster, DBMS)
3. Tasks and responsibilities distribution to group or individual by leader
4. Implementation of designed solution and Testing (Application Development)
5. Review and evaluate project progress
6. Final Project Documentation
7. Close down

Completion date
1. Selected Team members
2. All Team Members
3. Team Leader
4. Team members and group
5. Team member and team leader

Budget
So far it is estimated the project will involve no cost
 
Ahsante kwa kazi yako. Good work. Kuna vitu umeweka nimevipenda, lakini sisemi vipi!
clip_image001.gif


Perhaps you could have add a methodology section in which you could have discussed about what methods we are going to implement in the development process (Waterfall, Spiral). May be, tools and technologies we are expecting to use, fore example PHP for scripting language.

 Yah nilikuwa nimeandikia kitu kuhusu implimentaion strategy na approach sema sikuwa nimekamilisha nikaona nikitoe kipande hicho kwanza. But I have that.

Furthermore, we could have an activity plan. Do you have MS Project, so that you could draw proper Gantt Chart. The Schedule is very important, firstly because we need to spend less time as possible so that we do not lose focus and undermine our commitment. Secondly, it is a good lesson for time management. That is, writing an activity plan with each activity having its own deliverable and outcomes.

Boss Ms Prokect naweza kuipata but why not let us make it simple . Unaonaje tukitaja activities na task, start and expected end date yake na group au mtu atakeyehusika. In just a simple format. It a good lesson kama unavyosema lengo si tu sio tu kuwa na online directory bali ni kupata practical experience ya Project processes

Je miezi minne ni sawa.????

After having all that, we move to one of the important steps, requirement analysis.

In short, I think we have:

  • Planning
  • Requirement analysis
  • Design
  • Coding
  • Testing
  • Integrating
  • Implementing
  • Maintenance (Upgrades and Fixes)
The problem is mbona team members wengine wako kimya. At what stage do member do expected to be involved or not to be involved. Je hakuna wa kujitolea kuja na hata Requirement specification? Mimi naendelea kuiboresha hii kitu najua mwanzo mgumu.
Click to expand...
Boss Mpaka hapa nimeshajifunza kuwa wana IT wengi tunapenda kijihusiaha na Tecnical input zaidi kuliko documentation . But before technical solution and impplimentation, ideas lazima ziwekwe kwenye document. So tushirikiane.


You can see hizi stage za mwanzo wengi hawazipendi mpaka itapofika kwenye coding, Testing na kuendelea.


 
Nakubaliana na wewe iwe simple, ila iwe na info zote. Mimi najitolea kuandika Risk analysis document before Requirements. Inatakiwa iwemo kwenye Plan document, ila sisi tufanya separately (Our way!).

Tusirush kwenye code, ile itakuwa rahisi kabisa. Tukipatia huku juu, kila kitu kinafall into his place after good design and requirements analysis.

Nadhani labda kutokana na time difference na baadhi ya watu, ndio maana watu wapo kimya. Labda hawajaiona document. Jamani, hamna anaebisha? At least japo mmoja abishe.:rockon:
 
tabutupu said:
mheshimiwa kuna watu umewaacha, lakini usiwe na hofu bado tupo pamoja.
Click to expand...

Dah mkuuuuu nisamehe sana ndugu yangu wewe umo hii kitu ilikuwa inakwenda kwa FIFO .kwa hiyo kuongeza jina lako sio ufisadi sababu mni kati ya watu watano wa mwanzo kabisa . Nadhani hata team leader na mebers wote watakubali

Kumradhi tena tabutupu . Join in na tunasubiri kupata input na ushirki wako
 
Napendekeza kuwa, since the project is aimed at delivering an opensource application, basi, tools zote zitakazotumika ziwe in that licensing format.
Project management tools: Microsoft Project equivalent:-Use alternate/open source solution kama hizi zifuatazo
1). OpenProject
2). GANTT project

Kwa wale waliosomea project management and software development life-cycle pia wajumuishwe kwani already naona the plans zilizoandikwa hapo juu zinalenga kwenye "waterfall" models wakati kuna this new model referred to as AGILE SCRUM dev model (please see WIKI). That is more favourable for a system/application that is set to undergo multiple changes over its life time as needs/requirements/enhancements change .

A nice video explains Agile



Agile as compared to waterfall



One more vid.
 
Last edited by a moderator:
team and interested public members

Attached find a project plan for your comments an addition


Your input will help to have a good final plan.
 

Attachments

  • Online directory1.2.doc
    138 KB · Views: 42
Comments: 4.2
The scope of the application hasn't been decided as yet hence should not exclude any feature of the application. Pia, inabidi muangalie the solution and its future/usage viability ukizingatia the main driver of the project ni kuwa source of crucial information to the masses, ambao wanatumia two different technologie Traditional Internet (PC based)and Mobile Internet hence we can't eliminate either in the planning decisions. Solution has to support these two form factors.

The project is also missing one very important element: The client. My advice here would be that, for those who did not make it into the development team form the CLIENT/CUSTOMER group for the project, their main task being to set the agenda and review whatever design decisions are made by the development team.
 
kotinkarwak said:
Comments: 4.2
The scope of the application hasn't been decided as yet hence should not exclude any feature of the application. Pia, inabidi muangalie the solution and its future/usage viability ukizingatia the main driver of the project ni kuwa source of crucial information to the masses, ambao wanatumia two different technologie Traditional Internet (PC based)and Mobile Internet hence we can't eliminate either in the planning decisions. Solution has to support these two form factors.

The project is also missing one very important element: The client. My advice here would be that, for those who did not make it into the development team form the CLIENT/CUSTOMER group for the project, their main task being to set the agenda and review whatever design decisions are made by the development team.
Click to expand...

Mkuu michango yako mizuri sana we here also to learn knew thing na nimeshajifunza new things kama hi kitu uliyosema Agile methododology.

Sijui Team leader anasemaje but kulingana na consntarints tulizonazo nadhani itakuwa ni sahihi na kuanza na product yenye mapungufu fulani fulani . Project ikiwa success then kwenye maintanace tunaweza kuangalia uwezekanao wa kuangalia mambo kama ya Mobility na mengine mengi .

Yah project inakosa client but tukiweka all realistic client requiremnt then tunaweza tusikamilishe kitu. Tunakuomba uzidi kutoa input kama client but consdiering unaweza kubalansi requimennt zako na kuajribu kuona challenge ya upande wetu supplier. Nadnani siku si nyingi u will be a team member too.
Kaa la moto said:
I will remain among those who learns from your skills. Much love to JF and members!
Click to expand...
Am sure you have some skill we can also learn from you . Usiwe mchoyo tehteh teh
 
Sina experience ya web development kwa hiyo nadhani I will be of best service watching from the sideline, scrutinize what is going on in the project na kutoa suggestions of where as a client I would expect the project to be heading na kama kuna tools/applications zinazoweza kusaidia hii project nitaziweka humu.
Kama ulivyosema, to start off, maybe the project can follow the traditional approach na hapo baadae, wakati wa kufanya post mortem tutaona wapi new tools could have assisted in certain situations. I hope contributors walioomba seat watawajibika, since this can be a real learning activity for everyone.
 
redSilverDog said:
Here I attach A risk analysis document.
Click to expand...

Nakubali analysisi yako .
In simple sentense ni kuwa big risk ni sisi team members.

Sasa kuna member wako nje ndio wana communicate na kuna member tuko wote kwenye team hawaja communicate kitu chochote kile toka wamejiregister.

To try to minimise these riks member wote itabidi tu confirm na kukubali kuteuliwa kwenye timu. Inawezekana wengine walieregister kama kutest zali wakati kuna watu wamefungiwa milango

Sasa ukijumlisha poor communication na remoteness of team members risk inakuwa kubwa zaidi.

Ili kujaribu kufanya risks ziwe managable may be we might need to we might need to set a rules were a team member atakuwa amejideject automaticaly.

Napendekeza 5 consecutive days without a member providing or communicating any any input kwenye hii thread regarding project basi anakuwa out.

Vile Vile ndio maana nilipendekeza Team leader awe na power ya kufire na kuhire

Kwahiyo napendakeza uongeze haya mameno kwenye risk management

Poor Communication:5 consecutive days without a member providing or communicating any any input he/ she will autotaicaly out



Members leaving the Team: 5 consecutive days without a member providing or communicating any any input he/ she will consired left the team. So any suitable member may fill the postion or his task being delegated o another member.


Befere being accepted as a team member propsective team member member must accept and cofirm their participation the project.


So we shoud assume we are prospective team member except for you team lader.
Click to expand...
But so far soo good
 
You must log in or register to reply here.
Back
Top Bottom
Forums
New posts
Post thread
Back