Skip to main content

Italian Agile Day (and Scrum Workshop) in Bologna

The Italian Agile Day 2009 is the sixth edition of the free conference dedicated to Agile methods for development and management of software projects like eXtreme Programming, Scrum, Feature Driven Development, DSDM, Crystal and Lean Software Development.

I am honored and pleased to support their efforts as a Key Note speaker. My talk will be about Fixed Price Projects and Agile - It can be done!
What: Italian Agile Day
Organizers: Italian Agile Movement
Where: Bologna
When: November 20, 2009

Registration (more in English than Italian): http://iad09.eventbrite.com/
I believe in supporting the community, so I try to speak at communityevents (like this or the Agile Tour in Luxembourg) when asked, andgenerally without charge. This is a free event, so they are asking for donations to offset the costs of the event. Please contribute!

Just before the Agile Day, Alberto Brandolini and I are organizing a one day Scrum Workshop to help people discover Scrum:
Scrum today is becoming the leading agile management practice, helpingcompanies to develop software more effectively, helping developers toimprove their technical skills, and helping everyone to have more funon the job. But what is Scrum? How does it work? How does it relate toother practices such as Lean or Extreme Programming? And mostimportantly, why does it work?

This one day workshop is particularly geared to:
  • Developers and Testers who want to apply Extreme Programming or other Agile Practices at work
  • Managers and Project Managers who want their software teams to be more effective (and are willing to change themselves to achieve this goal)
  • Business Analysts, Business Development Managers and other customer roles who need software that meets their objectives
Language: Mixture of English and Italian. I speak both.

Where: Bologna (probably at the conference hotel, but not yet 100% certain)
When: November 19, 2009, 9.00 to 17.30
Cost: €500 / Agile Day Participants €400
Information and Registration for this Scrum Workshop in Bologna
So bring your boss, and I look forward seeing you at the Agile Day and / or our Scrum Workshop!

Comments

Popular posts from this blog

Scaling Scrum: SAFe, DAD, or LeSS?

Participants in last week's Scrum MasterClass wanted to evaluate approaches to scaling Scrum and Agile for their large enterprise. So I set out to review the available frameworks. Which one is best for your situation?

Recently a number of approaches have started gaining attention, including the Scaled Agile Framework ("SAFe") by Dean Leffingwell, Disciplined Agile Development (DAD), by Scott Ambler, and Large Scale Scrum (LeSS), by Craig Larman and Bas Vodde. (Follow the links for white papers or overviews of each approach).

How to compare these approaches? My starting point is Scrum in the team. Scrum has proven very effective at helping teams perform, even though it does not directly address the issues surrounding larger organizations and teams. An approach to scaling Scrum should not be inconsistent with Scrum itself.

Scrum implements a small number of principles and constraints: Inspect and Adapt. An interdisciplinary Team solves the problem. Deliver something of va…

Sample Definition of Done

Why does Scrum have a Definition of Done? Simple, everyone involved in the project needs to know and understand what Done means. Furthermore, Done should be really done, as in, 'there is nothing stopping us from earning value with this function, except maybe the go-ahead from the Product Owner. Consider the alternative:
Project Manager: Is this function done?
Developer: Yes
Project Manager: So we can ship it?
Developer: Well, No. It needs to be tested, and I need to write some documentation, but the code works, really. I tested it... (pause) ...on my machine. What's wrong with this exchange? To the developer and to the project manager, "done" means something rather different. To the developer in this case, done means: "I don't have to work on this piece of code any more (unless the tester tells me something is wrong)." The project leader is looking for a statement that the code is ready to ship.

At its most basic level, a definition of Done creates a sh…

10 Warning Signs, that your team is not self-organizing

How do you know that self-organization is working? The Bern Chapter of Scrum Breakfast Club looked into this questions, and identified the following warning signs (which I have taken the liberty of translating).

The team reports to the Scrum Master at the Daily ScrumPeople wait for instructions from the Scrum MasterTeam members don't hold each other responsible [for their commitments]The same impediment comes up twice"That's the way it is" => resignation"I" instead of "We"Flip charts are lonelyCulture of conflict-avoidanceDecisions processes are unclear, nor are they discussedPersonal goals are more important than team goals
To this list I would add my a couple of my favorites:
you don't see a triangle on the task board (not working according prioritization of stories)after the daily Scrum, people return directly to their desks (no collaboration)there are a least as many stories in progress as team members (no pairing)
P.S. You can join the …