This template can be easily used for incremental approach in Agile style. In essence it helps to define the properties that will form the conditions of the functional tests. From my experience, this is essential for designing the “proof of concept”, it is especially true for the architecture (e.g. workload). [...]
|
||||||
|
Moreover, for who is working in a consultant position (i.e. Time & Material) the policy of dragging the problems through the continuous ignorance of the elephant under the carpet does not change the result. Some monies gained in this way are lost in terms of self respect and a sound professional [...] There is a very amusing (and amazing as well) post about the seven capital sins of using automation for testing. In my yesterday’s post, automation had a huge importance. Therefore, the indications suggested by Colin, are to be taken with the utmost care. In essence, the best solution against mistakes remains a good [...] The automatic data collection, based on a well designed unit-test (see this post ) needs the following steps: A sound architectural design where services are neatly conceived for managing values and entities. In these days, I am busy with the building of a system for supporting the PMO via web. In this phase, most of the job consists in the preparation of “standard” templates. They represent the iceberg’s tip; however, the templates are tangible things that will be delivered to the PM. Their acceptance will make a [...] Prince2 templates: Today I have added/updated three more documents: Communication plan Hopefully in the next days I will be able to update the main page for explaning the new strategy. Some interesting hindsights: It is interesting to confront these three posts: Building A Better Project Grapevine While the first gives a good overview of what [...] The projects are set up for delivering a product. Therefore, all the efforts are sustained for obtaining that specific result. The PM(O) must be able to supply, to the Snr Management, the information needed for evaluating whether the project is still feasible (i.e. within the scope, the delivery date, budget and quality) or not. From this viewpoint, all other information (upcoming results, risks and issues) can be better understood in order to take action whenever it would be [...] The most common tool for communicating with the stakeholders (outside the team) is the report. The quotation made by Von Clausewitz can be applied to many occasions. There are several reasons for this, they span from excessive expectancies about the ability to produce information within the quality standard, to the lack of agreement about what it is worth being read (or viewed, when presentations are included). This post is dedicated to frame reports within the stakeholders’ management (the “Communication Management Strategy Report” has been published just today under Prince2 [...] …in order to make “real” things (either functions or reports) information is needed. Some data are essential in order to grant the necessary quality others are necessary for presenting the result in the best possible way. “The secret of life is honesty and fair dealing. If you can fake that, you’ve got it made.” In almost every project I managed, every stakeholder had his/her “little” dirty secrets. And it was not related to the security needs; whether they were essential or just important. Managing is about dealing with information The accountability is the key [...] |
||||||
|
|
![[Valid RSS]](/wp-content/uploads/2009/05/valid-rss.png "Validate my RSS feed"){kind=small}
