Concerto collects some ideas for a better and more effective board to be used in Agile projects.
For an unfortunate coincidence, I chose the same name of the famous Parasoft’s development management software, which I didn’t know before.
Concerto board has nothing to do with Parasoft.
Concerto – A Board For Agile Teams from Arialdo Martini on Vimeo.
This post is going to be pretty long.
Feel free to scroll down, or roll the paragraphs, if you think.
I’m pretty sure you will entirely read it later, since it is really interesting.
In case of panic, click here to jump to conclusions.
I am going to describe my personal views about managing large software developments. I have had various assignments during the past nine: years, mostly concerned with the development of software packages for spacecraft mission planning, commanding and post-flight analysis.
Continue reading
No it cannot.
I mean: actually, it does, but adopting new and modern methodologies, you can dramatically improve your team productivity.
Yet, I believe most teams are using a mix of Agile and Waterfall. The reason is Waterfall is the sole methodology able to give the only information your manager needs to know: how much the project will cost and what’s the delivery date. About this, read the excellent post by Christopher Goldsbury Why Agile Adoption Fails in Some Organizations
Continue reading
Tags: agile, estimation, waterfall
I once worked as a team leader in a startup. I was in love with XP, studying Scrum and looking forward to be able to put into practice what I was reading.
Unfortunately, my boss explicitly told me to use Waterfall. I never blamed him: before him, the company had no process at all, and was governed by anarchy; no documentation, no requirements, no clear roles. Actually, introducing a Waterfall process, he made a great revolution, and let the company succeed.
Continue reading
var it = new MP3(); sam.play(it); sam.play(it); @chrisoldwood $Apocalypse = now(); @johnnypixel 10 IF ALL WORK NO PLAY 20 THEN JACK = DULL BOY 30 GOTO 10 @andrewfconex c.beginPath(); c.fillStyle="#0f0"; c.lineTo(63360*72,0); c.stroke(); @adomas_s echo $bible['Eze'][25][17]; kill(); @arialdomartini
Tags: #MovieLinesInCode, twitter
Nevertheless, unfortunately, no matter how much I dig into the topic, I’m not able to convince myself that Martin Fowler’s arguments about Feature Branching, Continuous Integration and Feature Toggling are right.
Please, help me to understand what I’m missing.
Continue reading
Tags: agile, continuous integration, git, scrum, tdd
When a unit test for a method implementing some feature is green, it does not mean the feature is working. The corresponding end-to-end or integration tests reveal if it’s working or if it’s broken. To Product Owner’s point of view, end-to-end tests are all that matters. Unit tests are useless.
Unit tests are meant to lie. They rely on the often wrong assumption that the rest of the world is correctly working, but only because they are explicitly mocking it: using a fake world is a deliberate lie.
To me, that’s exactly why they are so useful.
Tags: agile, criticism, ddd, development, mike gualtieri
The Pomodoro Technique® is a very popular methodology in the agile movement, and it’s claimed to be used for the managementent of timeboxing.
Inexplicably, it seems that few have the courage to say:
The Pomodoro Technique® is one of the most ridiculous silliness you may find on management articles
Ok, I wrote it. Maybe it is worth an explanation. Get prepared: it will be long.
Tags: criticism, pomodoro, pomodoro technique
Tags: agile, job, management
I won’t be able to deliver on time. My estimation was too optimistic. What can I do now?
If you can’t deliver on time, don’t. Simple, isn’t it?
I believe the best strategy is cutting features and start both constantly refining your estimation and doing Deliberate Discovery. In other words, I believe the question was somehow misplaced.
Tags: agile, estimation, management
More than 700 years ago. Yet I think it has something to teach us about Agile.
Continue reading
Tags: agile
Tags: feature branch, git, italian
I’m in love with git, and I’ve been devoting a lot of time and efforts in promoting it in the companies where I used to work.
I always found hard to effectively communicate to TFS, svn and cvs users the paradigm shift that git requires. Depicting information and ideas turned out to be the most successful approach.
Yet, visualizing information is an art.
Continue reading
Tags: git
Giacomo Tesio wrote an interesting post after a question arose during the DDD Day in Bologna on October, 8th.
He proposes an appealing point of view about what programming is and what’s the Domain Expert’s role in respect to “the problem” and “the matter“.
I still have to think it through. I’ll write about this topic in the next days.
Thanks, Giacomo for giving me food for thought.
Tags: event sourcing, git
Tags: italian, management
Traduzione dell’articolo Introducing Deliberate Discovery di Dan North
Tags: bdd, dan north, deliberate discovery
