[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [kDev] kendraTools test 1...
Hi Kirit and All,
Thanks for your email but... did you guess? I went away to Gomera
(small island next to Tenerife) for a 3 week winter break and ended up
staying for 2 months. Couldn't get into Kendra in an Internet cafe
while the sun and sea were calling me. Anyway, back now and getting
back into the groove.
On Friday, February 7, 2003, at 02:31 pm, Kirit Saelensminde wrote:
1) Work out your deliverables
2) Build a project plan around those using any two of cost,
functionality & quality (you can't specify all three) as a basis.
This is very basic project management which I'm sure you can find a
lot of stuff on the web for.
From what you say I can at least conclude that I am not the guy to be
project managing coding development in Kendra Project. We need a
project manager or a group of people that take on that role. My skills
are in knowing where I want Kendra to go and having an overview of how
to get there. Doing coding and understanding formal coding practices
are just not what I do nor what I want to spend time learning.
It's really good that you detailed what needs to happen regarding
software development as it confirms that we're going in the right
direction: getting a project manager / developer in. They will then
grill me (ask questions rather than gas mark 4) on what I want for
kendraTools. I'm slowly getting ideas together but I respond much
better under questioning.
I still think that you are looking at two different projects:
1) Some web site tools to make your administrative tasks easier
2) Kendra Initiative
Although (2) will help you to deliver (1) the cost of doing it that
way around is a massive increase in complexity of delivering these
very simple tools. This is going to lead to delay, increased cost and
increased risk based on delivering (1) with whatever tools you have to
hand (preferably off the shelf) before spending too much time on (2).
I totally see where your coming from on that point. But by building
kendraTools with our own technology we can start to test out the wider
concepts of the project. It has to happen at some point and it may as
well be at the start. If we put a budget/time limit on it we can always
say: right, just build the tools using off the shelf stuff. But I have
a gut felling we can get functioning tools out the window without it
being too massive a time/budget thing.
Cheers Daniel