Friday, September 14, 2007

Rejoice Comrades!

I have just come from a meeting with the Revolutionary Council. Comrade Glorious Leader is doing well, the ailment that was bothering our supreme leader is now fixed.

That is to say, comrades, that I had ailed Comrade Glorious Leader by following the change request process a little too blindly without considering the greater context. Comrade Glorious Leader was quite vexed at the 'mysterious disappearance' of Comrade Revolutionary Systems Engineer.

As a result, the Change Request process, has itself accepted a Change Request (CR#3 for those tracking, and also ACR#1 (approved CR)), from now on, Change Requests will not automatically be 'declined'.

That is all for now Comrades!

I shall endeavour to work overtime this weekend to complete the revolutionary work breakdown structure for Phase 1 of the revolution. I hope to have it done by Monday. Only with the help of the Project Management Body of Knowledge would it be so easy to plan a revolution...

Wednesday, September 12, 2007

Rejoice Comrades!

It is time to iteratively progress through the creation of the revolutionary work breakdown structure.

To do this comrades, let us look at one of our revolution’s deliverables and determine how to use Decomposition to breakdown the deliverable into smaller packages to achieve the revolutionary communications plan.

Decomposing the parts is not just what is happening to Comrade Revolutionary Systems Engineer right now (his change request to eliminate ‘process’ after the revolution was not approved in the change request process).

We know many of the deliverables for phase 1 of the revolution. We shall break each of these into smaller pieces for phase 1, such as how the communications plan needs to have its own requirements defined. Then the lowest level items need to be coded with an ID code, much like all people will be after the revolution.

Tuesday, September 11, 2007

Comrades Rejoice!

We are ready to engage in decomposition to create the revolutionary work breakdown structure.

To do this, we must look at our inputs to the ‘Creating a revolutionary Work Breakdown Structure process’:
1. We have no ‘pending’ change requests,
2. No revolutionary assets but our intentions, excellent comrades, and revolutionary skill,
3. A preliminary revolutionary scope statement, and
4. A revolutionary scope management plan.

Err…
Number 4…

Comrades, I shall pay the ultimate penalty if we do not create this plan now.

Luckily, the inputs to the revolutionary scope management plan include 1, 2, and 3 from above, and also our revolutionary charter and revolutionary management plan, which we are creating as we go…

Since our scope is almost unlimited, then we shall use expert judgment from comrades such as Comrade Glorious Leader and Comrade Revolutionary Systems Engineer to create a revolutionary scope management plan.

Transcript of the meeting:

CPM (me): What do you think?
CRSE (Comrade Revolutionary Systems Engineer): Why limit ourselves. But since there is only so much time, then what we don’t define now will go into a revolutionary change management process, which I’ll devise.
CPM: Sounds good. When will you have it by?
CRSE: End of Day.
CPM: Excellent. I’ll look for a confirmation on that task and cross it off the preliminary task list, issues log, and communicate it out to the Revolutionary Team. I’ll also work on a format for the status mails so that everyone will be able to identify the relevant information easily, and work on setting up a location where we can store all the revolution’s documentation so that it will be easily accessible for future revolutions, which of course will not be necessary since ours will be the end all of all revolutions.
CRSE: Whatever. I’ll send you the confirmation via our secret encoded communication method.
CPM: We haven’t defined the revolutionary communications strategy yet. We’ll need to setup a meeting to discuss the initial requirements for that, do you know anyone else who should be involved? I’ll spin up a separate revolutionary work breakdown structure task to develop this, and open up an deliverables log to track this item until it is added to the revolution’s management plan.
CRSE: …
CRSE: …
CRSE: Can’t we just.
CPM: NO! We have a process for this and everything else. And if we don’t have a process, then the revolution is nothing. Even after the revolution, there will be process, unless of course, changing ‘process’ becomes one of the revolution’s goals. Would you care to initiate a revolutionary change request on that???

Monday, September 10, 2007

Comrades Rejoice!

The strike is over. Our fellow brethren in the allied revolutionary movement have finally acheived their demands. Much like Moses and Godzilla their leader had been condemned to live in the wilderness for his brazen ways in trying to acheive their revolutionary movements goals of more equitable hours, pay, and affordable property insurance.

Long live the revolution!

I would like to introduce to you, our new, systems engineer for the revolution, Comrade Revolutionary Systems Engineer.

Comrades, tomorrow we shall attack the next steps in the revolution.

Rejoice!