This is my site for fun and work. I am Sander, a software architect.
Centrical is my playground. Blogs, news and resources are updated regularly.
My articles are published on Infoworld, AutomatiseringsGids and Emerce, too.
I gather worldwide news, whether it is about e-commerce or service oriented architectures.
My resume, the Web Unified Process and the general conditions are offered in several formats.
Some more information about me is shown here, like a resume, professional history and more.
Things I do are audits, architecture design and strategic advice.
Read the cases of customers like Akzo Nobel, Sanoma Publishers and VNU.
To contact Centrical, you could either use the contact information or fill out the contact form.
Past publications, sorted by date of publication, are shown in my archive.
A short overview on what this website has to offer is shown here.
For a legal disclaimer and privacy issues according to international laws, check out this chapter.
For access to the systems of Centrical, you could use this entry.
This is an rss feed for news only. After clicking, copy the URL into your feedreader.
Stuff that happens to me sometimes inspires me to write. It may be nonsense, though.
WUP (Web Unified Process) is a lightweight and agile development method for web projects.
This where I keep technical posts that might come in handy.
Reporting project progress
The project manager has to keep track of the project’s progress. Every one or two weeks he should send out a status report to all members of the team, the customer and maybe some sponsors too. The schedule has to be fine-tuned using these reports.
A status report would at least contain the following topics: the team itself, evaluation of the past period, a prognosis for the upcoming period, the use cases that have been built versus the ones that haven’t and of course the PPD estimates versus the spent time (in PPD’s and true days).
You could use the template report to do this.
At the end of an increment or after a mayor release a separate evaluation has to be sent out to everyone involved. This evaluation should dig deeper into the requirements that have been realized versus the ones that haven’t.
A status report would at least contain the following topics: the team itself, evaluation of the past period, a prognosis for the upcoming period, the use cases that have been built versus the ones that haven’t and of course the PPD estimates versus the spent time (in PPD’s and true days).
You could use the template report to do this.
At the end of an increment or after a mayor release a separate evaluation has to be sent out to everyone involved. This evaluation should dig deeper into the requirements that have been realized versus the ones that haven’t.
Transform to PDF
Print this item-
Send to a friend
You are trying to view the newsticker in a browser that doesn't support it. I am sorry.
