Wednesday, February 21, 2007
ASS (part 2)
Well I've truley enjoyed playing with my ASS (Agile Sprint System). In response to a question posted earlier, I can confirm that ASS is available widely as OPEN source under the TOSSER (Totally Open Source System Experience of Retros) licence agreement. Many people have asked to see inside the source of my ASS. To which I say - get your own ASS and look inside it for yourself.
Tuesday, February 20, 2007
As Agile as they cum?
Thursday, February 15, 2007
Agile Sprint System (A.S.S)
Great news for Agile lovers. The world's first Agile operating system, Agile Sprint System (ASS), has gone into BETA release. As in common with other operating systems, ASS is responsible for managing hardware and software resources of a computer. This of course includes the usual tasks of memory management, I/O, security, networking and provision of a file system. But ASS goes further - incorporating Agile at it's very heart. Here are a few features to look forward to when you get your hands on an ASS.
Agile/IP now fully supported. I first mentioned this very exciting addition to the IP protocol family, in a previous blog a year or two back. For those who are unaware I'll quickly re-cap Agile/IP.
1. An extension of the OSI network model.
2. Agile stories are entered at the Application Layer. This is typically done via an application capable of using the AgileNet protocol. This protocol is an extension of the Telnet protocol.
3. The Presentation Layer then converts these Agile stories to XP Tasks using extended MIME encoding.
4. The Session Layer provides checkpoints which can be used for carrying out retros by a lower layer in the OSI model.
5. The Transport Layer helps move the XP task data between Scrum members without the latter having to know anything about computers.
6. The Network, Data and Physical layers are the same as in the standard OSI model - with one major exception. And that is security is added to the Agile data packets. This is done by injecting them with the Wide Area Network Kerberos Authentication policy (WANKA). These enlightened WANKAs, as the Agile packets are now known, are capable of delivering their tasks in any order they wish. Unlike TCP, however,
guarantee of delivery is never given by these WANKAs. If a delivery fails, they may try again - then again they may go off into a Spike and get side tracked. But thats a price well worth paying to be truly Agile.
Security The WANKA policy has been added to all file access now. It is a cut down version of the one used in Agile/IP and known as Mini WANKA.
Memory Management Thanks to the use of Binary Obstack Library Overlap eXtension (BOLOX), memory is now fully managed in an Agile manner. This means no up front memory usage design is done by the Operating System. Instead memory is used in a haphazard manner.
GUI ASS has an advance user interface. Everything looks a nice shade of pink, giving it a rose spectacled look about it. Very Agile I thought.
More reviews in the near future. If anyone else gets some ASS, please leave your comments here too.
Agile/IP now fully supported. I first mentioned this very exciting addition to the IP protocol family, in a previous blog a year or two back. For those who are unaware I'll quickly re-cap Agile/IP.
1. An extension of the OSI network model.
2. Agile stories are entered at the Application Layer. This is typically done via an application capable of using the AgileNet protocol. This protocol is an extension of the Telnet protocol.
3. The Presentation Layer then converts these Agile stories to XP Tasks using extended MIME encoding.
4. The Session Layer provides checkpoints which can be used for carrying out retros by a lower layer in the OSI model.
5. The Transport Layer helps move the XP task data between Scrum members without the latter having to know anything about computers.
6. The Network, Data and Physical layers are the same as in the standard OSI model - with one major exception. And that is security is added to the Agile data packets. This is done by injecting them with the Wide Area Network Kerberos Authentication policy (WANKA). These enlightened WANKAs, as the Agile packets are now known, are capable of delivering their tasks in any order they wish. Unlike TCP, however,
guarantee of delivery is never given by these WANKAs. If a delivery fails, they may try again - then again they may go off into a Spike and get side tracked. But thats a price well worth paying to be truly Agile.
Security The WANKA policy has been added to all file access now. It is a cut down version of the one used in Agile/IP and known as Mini WANKA.
Memory Management Thanks to the use of Binary Obstack Library Overlap eXtension (BOLOX), memory is now fully managed in an Agile manner. This means no up front memory usage design is done by the Operating System. Instead memory is used in a haphazard manner.
GUI ASS has an advance user interface. Everything looks a nice shade of pink, giving it a rose spectacled look about it. Very Agile I thought.
More reviews in the near future. If anyone else gets some ASS, please leave your comments here too.
Wednesday, February 14, 2007
Agility on Valentines day
Thank you to that wonderful reader who brought twinky nrobinson into my life. A boy couldn't wish for a more agile valentines gift...
After musing upon twinkies writing, chance brought me to this website and the perfect description of the joys of the agile path: "with training and willpower, intense feelings can be felt as exhilarating ecstasy...". Care to join me nrobinson? Enjoy!
After musing upon twinkies writing, chance brought me to this website and the perfect description of the joys of the agile path: "with training and willpower, intense feelings can be felt as exhilarating ecstasy...". Care to join me nrobinson? Enjoy!
Saturday, February 10, 2007
Agile 2007 Conference
Friday, February 9, 2007
The A-Team
In 1972, a crack pot unit was sent to prison by a non-Agile court for a crime they didn't commit. These men promptly escaped a maximum security Scrum Iteration to the Los Angeles underground. Today, still wanted by Ken and Kent, they survive as soldiers of XP. If you have a problem, if no one else can help, and if you can find them, maybe you can hire...the Agile-Team.
Featuring:
Colonel Johnny "eXtreme" Smith
Lieutenant "Faceman" nRobinson Peck
Captain "Half Agile, Half Smegma" Marc
Sergeant "Bullshit Agile" Chappy
Amy "Nice Rachel" Allen
Featuring:
Colonel Johnny "eXtreme" Smith
Lieutenant "Faceman" nRobinson Peck
Captain "Half Agile, Half Smegma" Marc
Sergeant "Bullshit Agile" Chappy
Amy "Nice Rachel" Allen
Thursday, February 8, 2007
The Daily Scrum
In my previous posts I dealt with the concept of Test Driven Development (TDD) and a typical Agile day. I now propose to move onto the concept of the Daily Scam (err... sorry I mean Daily Scrum). This takes place every morning, on the dot, at the same place, with no exception or excuse whatsoever, at precisely the same time each day, 365 days per year. As an Agile Grandmaster at a client site I currently hold my Daily Scrum between 9am and 3pm every day (err... or two or sometimes three days - depending on the time of the month).
Each Daily Scrum begins with the Agile chant to the Agile Grandmasters of old . This involves me assuming the Bent Keck position and the minions going around me shouting:
Kent, Ken - Agile be thy name. Thou shall be sucked as Dyson did before us.
By way of illustrating what happens in a typical daily Scrum with me, I will hereby re-produce a typical set of dialogue that I have experienced.
-------------------------
Me: OK minion Number 1 (damn I must get out of calling my subordinates that). What have you done since the last Scam?
Minion Number 1: When was that? I can't remember?
Me: Stupid fucker, it was yesterday of course.
Minion Number 2: I think you will find that yesterday, Crispin, you didn't come in as you were recovering from your Bukkake session over the weekend. Therefore we did not have our Scrum.
Me: Who asked you?, you little shit. Besides it's not your turn to speak. Anyway, what are you planning to do next minion number 1?
Minion Number 1: I don't know. What should I be doing?
Me: How the fuck should I know. As Scam master I don't give a fuck what you do. I'm here to just find out what you've been doing and planning to do next.
Minion Number 1: In that case I propose for today that I screw that cute blond in reception.
Senior Client Director: You leave her alone, do you hear?
Me: Err, excuse me. Who the fuck asked you to talk? Remember you are only a ChickenHawke. In future remember the daily scam is for Twinks only to speak.
Minion Number 3: Twinks?!? I'm sure the term is Pig?
Me: Look you can fucking stop talking also. Anyway, back to minion number 1. The 3rd and final question to ask is of course 'Whats stopping you in progressing?'
Minion Numbers 1, 2, 3 & Senior Client Director: YOU ARE, you fucking idiot!
Me: Right that does it. I'm calling this Scam to a halt due to a complete lack of commitment from you bunch of fucking retards.
----------------------------
I would like to hear from anyone else who wishes to share their daily scam experiences. Please leave a comment for us to share.
Each Daily Scrum begins with the Agile chant to the Agile Grandmasters of old . This involves me assuming the Bent Keck position and the minions going around me shouting:
Kent, Ken - Agile be thy name. Thou shall be sucked as Dyson did before us.
By way of illustrating what happens in a typical daily Scrum with me, I will hereby re-produce a typical set of dialogue that I have experienced.
-------------------------
Me: OK minion Number 1 (damn I must get out of calling my subordinates that). What have you done since the last Scam?
Minion Number 1: When was that? I can't remember?
Me: Stupid fucker, it was yesterday of course.
Minion Number 2: I think you will find that yesterday, Crispin, you didn't come in as you were recovering from your Bukkake session over the weekend. Therefore we did not have our Scrum.
Me: Who asked you?, you little shit. Besides it's not your turn to speak. Anyway, what are you planning to do next minion number 1?
Minion Number 1: I don't know. What should I be doing?
Me: How the fuck should I know. As Scam master I don't give a fuck what you do. I'm here to just find out what you've been doing and planning to do next.
Minion Number 1: In that case I propose for today that I screw that cute blond in reception.
Senior Client Director: You leave her alone, do you hear?
Me: Err, excuse me. Who the fuck asked you to talk? Remember you are only a ChickenHawke. In future remember the daily scam is for Twinks only to speak.
Minion Number 3: Twinks?!? I'm sure the term is Pig?
Me: Look you can fucking stop talking also. Anyway, back to minion number 1. The 3rd and final question to ask is of course 'Whats stopping you in progressing?'
Minion Numbers 1, 2, 3 & Senior Client Director: YOU ARE, you fucking idiot!
Me: Right that does it. I'm calling this Scam to a halt due to a complete lack of commitment from you bunch of fucking retards.
----------------------------
I would like to hear from anyone else who wishes to share their daily scam experiences. Please leave a comment for us to share.
Subscribe to:
Posts (Atom)