Italian Agile Day 2014


14 e 15 Novembre 2014
Insieme a Jacopo Franzoi ho presentato lo speak "Team non si nasce ma si diventa". La nostra sessione ha toccato i seguenti punti:
  • Cosa vuol dire “Team non si nasce ma si diventa”
    • come si capisce che un team va bene?
    • come si capisce che bisogna cambiare qualcosa?
  • La composizione del team
    • dimensione (come siamo arrivati a 4 e perchè)
    • sviluppatori
    • il “bidello” (a cosa serve? perchè fa parte del team?)
  • La base di partenza
    • valori (partendo da quelli di XP, poi nuovi)
    • pratiche
    • motivazioni
  • Come si evolve
    • retrospettive
    • nuove pratiche (laser game di fine rilascio, test di produzione, …)
    • valori emergenti
  • L’auto-organizzazione
    • processo di sviluppo
    • code conventions
    • lo studio, le presentazioni a tutta l’azienda
    • recruiting
Guarda il video
Location: Ancona, Italia

Comments

Post a Comment

Popular posts from this blog

"Back to values" agile retrospective format

Image
A week ago i proposed to my team a new format for the weekly retrospective. I called it "Back to values" because the starting focus is on values and then on practices and actions to improve that practices. Step 1: the values I put on the wall seven big post-its with the values, on the pink post-its the eXtreme Programming values plus the team's values on the orange post-its. simplicity (XP) communication (XP) feedback (XP) courage (XP) respect (XP) trust (team) sharing (team) Each teammate has an up arrow and a down arrow and I asked them to vote the best performing value of the week and the worst performing one. At the end of the vote we chose the two most rated values (no matter if with down or up arrow). In our case the chose values was communication and sharing. Step 2: the practices For each of the two chose values (one at a time), I asked the team to write on post-its all practices that support this value, both if they had used them and if...
Read more

Contracts: diagonal saber vs. agile

Image
I have moved from a product company to a consulting firm and therefore I am dealing with issues that up to now I have not considered particularly interesting, but now they are. In particular, to make offers to customers I need to better understand what type of contract I can offer to support an agile development process . So what did I do? I studied! I picked up the book " Lean Software Development: An Agile Toolkit " and I tried to summarize what I studied and how much I shared with my colleagues in these slides. It's about how to move from diagonal saber contracts to agile contracts . How to go from arguing over contractual clauses to find a form of win-win cooperation. Do you know what a diagonal saber contract is? Do you know what are the main types of contract for software development? What can we learn from Toyota 's manufacturing experience? Is it all applicable to the world of software development? Find it out!! Contracts: diagonal ...
Read more

Holacracy joy and pain

Image
I want to share my 3-year experience with Holacracy . The implementation seen in my previous job with a detached point of view, an example of auto-organization at company level whit some joys and pains. It's not a judgment about Holacracy but only the story of my experience . Holacracy joy and pain from Marco Fracassi
Read more