First Certified Scrum Developer (CSD) in Buenos Aires
0During July and August I’ll be facilitating the required courses for the CSD certification (Certified Scrum Developer) from the Scrum Alliance.

These courses will put speccial focus on the agile engeneering practices for software development like continuous integration, concurrent version managing, test automation, User Stories aceptance criteria automation (ATDD), TDD and refactoring, database evolutive development, database refactoring, taskboards usage, agile metrics, planning poker, release planning, retrospectives, etc.
There will be three different tracks for you to become a Certified Scrum Developer:
Track 1: Planning Orientation for non Certified Scrum Masters:
1. Introduction to Scrum (1 day course)
2. Estimatin and Planning with Scrum (1 day course)
3. Agile Software Developmenr (3 days course)
Track2: Software and DB Development Orientation for non Certified Scrum Masters:
1. Introduction to Scrum (1 day course)
2. Agile Software Developmenr (3 days course)
3. Agile Database Development (1 day course)
Track 3: Software Development Orientation for Certified Scrum Masters:
1. Agile Software Developmenr (3 days course)
After following any of these tracks you’re qualified to take the Scrum Alliance CSD exam.
You can see the course calendar in Kleer’s Scrum Alliance profile or in the Agile en Acción! calendar, grouped by track.
For more information you can download Kleer’s CSD brochure from:
A new era on motivation & engagement
0The problem is that Andrew doesn’t have his shirt on.
Incredibly this is the most common reasoning I’ve encountered over the last few years addressing the lack of commitment and / or motivation of resources within an organization. Let’s start calling them “people” instead of “resources” and we’ll begin to understand a little better the issue.
Another argument that is also used is:
Well, thats the way “Y Generation” is.
I have dozens of real examples which I won’t disclose die to respect purposes, but most occur / occurred in those organizations that are used to reward the “Performance” of the people.
This is a topic to chat for a long time, but it would be better to do with a coffee in between, much better in a lunch. Unfortunately we are not in any of these situations.
At this time there’s a very interesting discussion on the list of Agile Argentina that reminded me this issue, in which Juan sent a video that clearly illustrates the issue.
I leave it here for anyone who wants to see it. I hope you find Daniel Pink’s approach about the issue as interesting as i actually do.
For now, it would be good for the new start-ups to begin promoting autonomy, mastery and purpose of each of its employees.
PS: here’s another talk Daniel pink gave in TED:
Adding auto increment columns
0I’m currently working on a demo/tutorial on Evolutionary Database Development techniques and tools.
Since yesterday we installed a mysql in a client for some software configuration management operations, I decided to use mysql for the tutorial / demo at hand.
I found something strange when trying to add an auto-incremental column to an existing table.
Given this table:
create table program ( required_solo_hs int not null, required_inst_hs int not null, int not null required_hs )
I tried to add a column id:
alter table add column program id int not null auto_increment
Getting the following error;
Script line: 1 Incorrect table definition;
There Can be only one auto column and it must be defined as a key
The solution is simply to indicate that the auto increment column is also primary key:
alter table add column program id int not null auto_increment key,
Again .. someone might find it useful.
Kleer & Run IT
0Run IT and Kleer have made a business alliance through which all teh Run IT user will be able to participate in any of the “Agile en Acción!” courses. If you want to participate in these sweepstakes, you must meet the following conditions in Run IT:
- Enter in your profile that you are interested in participating in the Kleer sweepstakes
- Have a score of more than 250 points within the network
- Able to attend the courses taking into account the location of the site
Each winner can participate again in these drawings, should take into account that the points are reset at the time of winning.
The valid points are those obtained by generating content of interest within the community or for inviting friends and then they have registered on the site.
More on Run IT: http://www.runit.com.ar
Windows Vista 64bits & MySQL: ERROR 1045 (28000): Access denied for user ‘root’@'localhost’
6Today -at Kleer- we went through the experience of installing MySQL 5.1 for the first time in Vista 64bits. Far from being a pleasant installation, as we’re used to, this made us sweat bullets sweat.
After downloading the 64bit installer, install and configure, the setup wizard wouldn’t stop giving the error:
ERROR 1045 (28000): Access denied for user 'root' @ 'localhost'
We tried many solutions but none worked. Except for the following:
1. Stop the service “MySQL” from “Control Panel-> Administrative Tools-> Services”
2. Go to “C:\Windows\System32″
3. Find the file cmd.exe, right click with SHIFT down and select “Run as administrator”
4. Run the following command:
mysqld - skip-grant-tables
5. Leave that window running
6. Open another terminal window, this time NOT as administrator: “Start-> Run-> cmd” ENTER
7. Run the following command:
mysql-u root mysql
8. Wala! We are inside. Run the following statement, changing a password mypass real you want setear:
UPDATE user SET Password = PASSWORD ('mypass') WHERE USER = 'root';
FLUSH PRIVILEGES;
9. Exit:
exit
10. Close the window
11. Close the window that was running as administrator
12. Open task manager and kill all processes named “mysqld” (there should be one, of another user “Administrator”)
13. Start the service from “Control Panel-> Administrative Tools-> Services”
14. Log in again, this time as we are used to:
mysql-u root-p
With this last step, you should be connected without problems. I hope this solution can serve someone and save some time.
Procrastination
0By prioritizing the stories in the backlog we’re supposed to do it by business value or ROI (value / cost). I like to also add the risk inherent in the user story and use it as a factor to decide on prioritization.
Said in a different way, the group of stories with greater ROI can be divided into more risky stories and less risky stories. In particular I prefer to first address those at high risk because I see agile methodologies a great tool for risk mitigation. If the risky stories are left or postponed for a later time, we wouldn’t be mitigated any risks.
Just thinking out loud because of a procrastination video I saw on YouTube.
Procrastination
Procrastination refers to the counterproductive deferment of actions or tasks to a later time. Psychologists often cite such behavior as a mechanism for coping with the anxiety associated with starting or completing any task or decision.[1] There are three criteria for a behavior to be classified as procrastination: it must be counterproductive, needless, and delaying.[2]
Procrastination may result in stress, a sense of guilt and crisis, severe loss of personal productivity, as well as societal disapproval for not meeting responsibilities or commitments. These feelings combined may promote further procrastination. While it is regarded as normal for people to procrastinate to some degree, it becomes a problem when it impedes normal functioning. Chronic procrastination may be a sign of an underlying psychological disorder.
Source: Wikipedia: http://en.wikipedia.org/wiki/Procrastination
Bigger procrastination examples are those deep analysis and design phases of traditional project management, also known as Analysis-Paralysis, but this is a topic for another post. (procrastinating)…
Agile in Action! – March 2010 – Review
0From March-16th trough March-26th the workshop named Agile en Acción! took place in Buenos Aires City.
This edition was delivered to 15 participants, who through a serie of workshops based on real requierements created EPICs and User Stories, estimated and prioritized them, created the Product Backlog, defined Velocity, put together the Release Plan, and ended with a series of retrospective execices.
There was a great dynamic between the participants and between the teams that were built. We all have fun during those 4 days. I took some photos that you can access here: http://bit.ly/alQC2j
Greetings!
There will be a new Agile in Action! in April-2010: http://bit.ly/agile-en-accion–abril-2010



