A Backlog Item is a defined as “Deliverables, Stories, Functionality Requirements”. A Backlog Item can be anything as long as the team understands that it has to have business value and is meaningful for the Product Owner.
While I was working on my backlog Yesterday, I tried to understand, what kind of project I am? A maintenance or ongoing project? A fix price, fix date? A time and material? A project with non-defined end-date and a continuous flow of requirements? Or maybe I am a product? A product that is already released … weiterlesen →
I found again some very interesting wrong interpretations about how Scrum works. Kenji Hiranabe and I discussed this point over a year ago before his second Kanban article for InfoQ. I argued and I believe Kenji concurred that Agile methods like Scrum are really small batch transfer push processes. There is no explicit pull system within … weiterlesen →
You do continous integration – but every release is still a big THING. You fear it, you sit there and you hope it will work. In case you are in this situation, you are obviously behind the next development in our industry. A friend reommended a posting to me that I liked so much, I … weiterlesen →
“I did not hire the 26 year old game designer, who was fresh from university, I hired the 16 year old boy who was still in school as our new game designer. He still has new fresh and completely different ideas.”A well know person in the German video game industry told me this a couple … weiterlesen →
In the last week, we helped 8 companies in Maringá in Parana, Brazil to improve their Scrum implementation. [googlemaps http://maps.google.com.br/maps?f=q&source=s_q&hl=pt-BR&geocode=&q=maringa+parana&sll=-8.209598,-35.56955&sspn=0.420678,0.541763&gl=br&ie=UTF8&z=11&ll=-23.356125,-51.903534&output=embed&w=425&h=350] Maringá is a city full of wonderful trees, really good restaurants and with a lot of very interesting small companies: DB1: A very interesting company that provides ERP software and a messenger program. SG Sistema: … weiterlesen →
Karl Scottland, asked me to give you more precice information about Scrum and Kanban. He http://availagility.wordpress.com/2008/10/28/kanban-flow-and-cadence/ A Kanban system is a mechanism for controlling the work in the software development system. Kanban can be defined as “visual card”, as shown below – kindly written for me by Kenji Hiranabe [?] at Agile 2008. read more … weiterlesen →