Author archives: andreat
25 December 2011
andreat
,
OlafLewitz
A game to let you experience four of the five domains of Dave Snowden’s Cynefin framework.
Context
The Cynefin Lego Game is part of agile42’s management training for the Agile Management Framework.
It is licensed under the Creative Commons Attribution-Share Alike 3.0 Germany License.
What It Is
A game to let you experience four of the five domains of Dave Snowden’s Cynefin framework.
Using Lego, you go through four exercises where the problem to solve and the context you work in is designed to create a simple, complicated, complex and chaotic system. While it does not introduce you to the full potential of the sense-making framework, it is well suited to get a ...
15 September 2010
andreat
At the peak of sprint planning the team pledges "We commit to achieve these stories, no matter what it takes". ...
At the peak of sprint planning the team pledges "We commit to achieve these stories, no matter what it takes". It's a deal with the Product Owner (PO) and the team.
So why do teams commit?
The commitment is only valuable if the team thinks it can actually achieve it. Since the team is invited to pull the right amount of stories from the backlog, the PO trusts that the team makes reliable commitments based on their current capabilities and expected flow. This way the self-organizing team is challenged to constantly improve estimates, deliver value, as well as contribute ...
6 July 2009
andreat
How to get a reasonable Sprint commitment without having to spend too much time in breaking down tasks at the Sprint Planning meeting, while being quite sure that you are going to make it
Never had the problem that the Sprint Planning Meeting often is at risk of going out of the time-box, and eventually the Development Teams didn't manage to fill up the Sprint Backlog with all the needed tasks?
I want to share with you a way - for sure no rocket science, but "Common Sense" as Ken would say - in which you can have a team committed to the deliverables, without having to struggle with the tasks breakdown, and at the same time having a "good enough" understanding about the commitment given to move forward... interesting? Than read forward :-)
The idea ...
7 May 2009
andreat
Introducing Scrum in large organization is often a big challenge, it may take a lot of time to have all the parties in-line and able to start the adoption of Scrum. Moreover having a v...
Abstract
Introducing Scrum in large organization is often a big challenge, it may take a lot of time to have all the parties in-line and able to start the adoption of Scrum. Moreover having a very dynamic and constantly growing organization, requires to adopt special attention to dependencies between products. You need to have a plan, build a transition backlog, and define your strategy to phase out Scrum into the organization. Agile42 is helping Nokia (Berlin) to make this transition.
Here you can download the Presentation:
Best & Thanks for attending!
ANdreaT
23 April 2009
andreat
As we always say, every new training is a new experience, and you never stop to learn something, which is the *exciting* part of the job... at a telecommunication company in Croatia...
As we always say, every new training is a new experience, and you never stop to learn something, which is the exciting part of the job... at a telecommunication company in Zagreb it has been another very interesting experience, and again we learned something together :-)
Negotiation is the key, talk to the Product Owner...
The Product Owner prepares the Requirements and Stories and put them into the Product Backlog, sorted by Business Value, so that the items more valuable are considered first. Some times the Product Backlog is misunderstood to be a Plan, given from the Product Owner to the ...
4 April 2009
andreat
Following some more pictures from the Nokia training experience - already more than 15 teams have been trained and coached by agile42 in the last 6 months - were I'll try to point out some more intere...
Following some more pictures from the Nokia training experience - already more than 15 teams have been trained and coached by agile42 in the last 6 months - were I'll try to point out some more interesting highlights...
Best Practices
Collaboration...
Even in only 5 min. of time, after 2 Sprints and 2 Team Retrospectives the teams greatly improved their ability to self-organize and collaborate. You can't imagine how many hands are building together on the same "story" and how well synchronize the team members are sorting out pieces, putting them on top of each other to achieve the common ...
31 March 2009
andreat
The Scrum LEGO City Game is about building a nice city with Lego bricks - not a new idea till here - and doing it using as much as possible what learned during the Scrum Training. To create the sense of urgency, agile42 presents the "Product Vision" as to prove to the world that it is possible to build a LEGO city in only 20min. of working time...
Hi all, as agreed with our classes we decided to initiate a series of posts communicating the highlights of our trainings. In particular we constantly evolve the way we teach Scrum, and we make a lot of effort to make people live the best possible experience in only two days of training.
Introduction
After some years doing training, we came to the point where we really needed to find something that was good enough to put all together in a reasonable time, the theory of Scrum. Well after some reading over the internet and some inspecting & adapting, we came out ...
29 August 2008
andreat
**Agilo for scrum** is a Trac plugin that uses the issue tracking system and extends it with features that enable you to follow a more agile development process.
It’s still in early beta, but look...
Agilo for scrum is a Trac plugin that uses the issue tracking system and extends it with features that enable you to follow a more agile development process.
It’s still in early beta, but looks very promising already. It’s got an Apache Software License 2.0 so you can always have a look under the open-source hood ;-) Installation is possible with a python egg, so you can easy_install the whole thing, provided you have the needed dependencies (matplotlib and the python imaging library, to name a few).
After setup, Trac is modified quite substantially so let’s have ...
26 July 2008
andreat
Thanks to the support of our users (see the discussion group thred http://groups.google.com/group/agilo/browse_thread/thread/c119eb374b731436) which helpd in nailing down a significant number of bugs,...
Thanks to the support of our users (see the discussion group thred http://groups.google.com/group/agilo/browse_thread/thread/c119eb374b731436) which helpd in nailing down a significant number of bugs, we just released another version of Agilo for Scrum 0.6.6.
The Bug fixed:
- Wrong calculation of Resources allocation time, while the total have been correct, in some situations the individual allocation where fractioned
- Support for unicode characters in resources names, there was a bog avoiding to update a task containing a unicode character in one of the resource names
- Improved stylesheet for agilo-theme.
Thanks once more for ...
7 July 2008
andreat
One of the "assumption" that is often made, when starting to adopt Scrum, is that there will be a Product Owner and there will also be a Product Backlog. Well, it happens that the Product Backlog quality is one of the major responsible for the outcome of what the team will produce in terms of software, and is absolutely one of the most difficult things to work out. There are many problems related to having a right Backlog in place, and as you may guess there is no "one recipe" for the right Backlog, only some important ingredients to mix up in the right way ;-)
Product Backlog: Requirements or User Stories?
Hi there, spending some extra time at the airport (thanks to lovely pilot strikes) gives me the chance to write a bit about Scrum and the Product Backlog. A Product Backlog is a stack of "features" prioritized by Business Value, which means that on top of the stack there is always the most valuable item for the customer/client.
The owner of the Product Backlog is the Product Owner and as such should be the one and only authorized to make changes to the Product Backlog, given also the fact that the main responsibility ...
Andrea Tomasini
Olaf Lewitz
