Lost Password?
Register now!

(1) 2 »
Quotes : Lean: Results are not the Point
on 2010/3/8 1:37:31 (1148 reads)

I have just finished reading the great book “Leading Lean Software Development” by Mary and Tom Poppendieck and I wanted to share with you two quotes excerpted from it.

Read More... | 2297 bytes more
Quotes : How Do You Refactor Untested Code?
on 2010/2/9 9:51:51 (997 reads)

I am currently reading the excellent "Debug It!" book written by Paul Butcher and I wanted to share with you some of the little gems that I have found in it.

Read More... | 1227 bytes more
Quotes : Agile Project Management Insights
on 2009/12/16 0:48:59 (1013 reads)

I am currently reading the book “Agile Project Management” from Jim Highsmith. I will publish a review later on this blog, but in the meantime I would like to share some of the interesting quotes that I have found in the book. I am sure they will make sense to software project managers… and developers ;o)

Read More... | 3773 bytes more
Quotes : Finding a Good Agile Coach
on 2009/9/17 4:51:28 (987 reads)

“Agile is all about teams working together to produce great software. As an Agile coach, you can help your team go from first steps to running with Agile to unleashing their full Agile potential.”

Read More... | 1518 bytes more
Quotes : Why Tester Won’t Like Agile
on 2009/9/3 1:04:54 (869 reads)

Testers cling to the concept of an independent QA team for many reasons, but the main reason is fear, specifically:

* Fear that they will lose their QA identity

* Fear that if they report to a development manager, they will loose support and programmers will get priority

* Fear that they lack the skills to work in an agile team and will lose their jobs

* Fear that when they’re dispersed into development teams they won’t get the support they need

* Fear that they, and their managers, will get lost in the new organizations


We often hear of QA managers asking questions such as “My company is implementing agile development. How does my role fit in?”. This is directly related to the “loss of identity” fears.


Source: “Agile Testing”, Lisa Crispin and Janet Gregory, Addison-Wesley, 2009

Quotes : What is an Agile Tester?
on 2009/4/2 11:59:21 (845 reads)

"We define an agile tester this way: a professional tester who embraces change, collaborates well with both technical and business people, and understands the concept of using tests to document requirements and drive development. Agile testers tend to have good technical skills, know how to collaborate with others to automate tests, and are also experienced exploratory testers. They're willing to learn what customers do so that they can better understand the customers' software requirements."

Source: "Agile Testing", Lisa Crispin and Janet Gregory, Addison-Wesley, 2009

Quotes : Sizing Project Teams
on 2009/2/11 23:59:14 (906 reads)

“We regularly coach groups that ask, “How can we calculate how many people we will need?” Our suggestion is, “Start with a small group of great people, and only grow when it really starts to hurt.” That rarely happens.”


Source: “Scaling Lean & Agile Development - Thinking and Organizational Tools for Large-Scale Scrum”, Craig Larman & Bas Vodde, Addison -Wesley

Quotes : Wise Iteration
on 2008/3/20 4:21:55 (947 reads)

As you move ahead, keep in mind the following:
* Never confuse the map with the journey - The project plan is only an outline (and a guess at that), so you should believe the team’s results and not the plans. Remember, it is the achievement of the objectives that is important, not the production of artifacts or the completion of activities. Be careful not to confuse the ends (objectives) with the means (artifacts and activities).
* Adopt the attitude that continuous planning is a good thing - In every iteration, expect your plans to change (albeit in small ways if your planning is effective). Don’t fall into the trap of thinking that the plan is infallible.
* Mature your process alongside your team - Tune the working practices alongside the plans, adapt your team’s skills as necessary to improve over time.
* Be prepared to cut your losses - Canceling bad projects early is success because you save time, money and resources that can be applied to better opportunities.
* Be honest - Without objectivity and honesty, the project team is set up for failure, even if developing iteratively.


Source: “Managing Iterative Software Development Projects”, Kurt Bittner, Ian Spence, Addisson Wesley.


Transitioning from a traditional approach to iterative software development is more a change of mind than a schedule adjustment. So try to be honest… or at least as honest as you can be ;o)

Quotes : The Main Principles Behind Lean
on 2008/1/31 5:01:28 (1272 reads)

Question: What are the main principles behind Lean?

Mary Poppendieck: The main principles behind Lean were articulated by Taiichi Ohno, the person at Toyota who invented the Toyota Production System. The first principle would be the idea of Flow (or Low Inventory, or Just-in-Time).

Read More... | 1721 bytes more
Quotes : Sharing Trough Implementation Patterns
on 2008/1/31 4:37:36 (891 reads)

The thing I like about the pattern form is that it gives you a way to talk about the motivation for what you are doing. So there is a lot of Java style books, and good ones, out there people with lots of experience, people who've thought carefully about how to program, but when I read them what I hear is a set of commandments, "Name variables like this, arrange your code like that, etc" and all those are good things to do in certain circumstances, but what doesn't ever come true for me is why?

Read More... | 2094 bytes more
(1) 2 »