title

Agile Doctor

Agile Doctor

0
Followers
3
Plays
Agile Doctor
Agile Doctor

Agile Doctor

Agile Doctor

0
Followers
3
Plays
OVERVIEWEPISODESYOU MAY ALSO LIKE

Details

About Us

Things Change. Be Agile.

Latest Episodes

Agile Principles: Team Reflection Provides Growth

Retrospectives are my favorite of all the scrum activities because they represent the opportunity to reflect on how we are implementing and to adjust our behavior to be more effective. I have said to my teams on many occasions that if I were forced to choose only one scrum ceremony that my choice, without hesitation or reservation, would be the retrospective. Without it, how could we ever expect to improve? What essential difference would an “Agile” project have over the many death march projects that teams have come to accept?

8 MIN2016 AUG 16
Comments
Agile Principles: Team Reflection Provides Growth

Agile Principles: Why You Need Self-Organizing Teams

I have often argued that the founders of Agile did not provide reasons why their approaches worked just that they did. Their was empirical evidence, proven by doing the work, or, as they state in the beginning of the manifesto - uncovering better ways of developing software by doing it and helping others do it. From their very pragmatic approach, they figured out that better software was created by following the values and principles. One of those discoveries was that better software was created by self-organizing teams.

3 MIN2016 AUG 16
Comments
Agile Principles: Why You Need Self-Organizing Teams

Agile Principles: Simplicity is Essential

In 2002, Jim Johnson of the Standish Group (made famous by their Chaos Report of software project “success”) presented findings of features and functions used in a typical system. The number of features that were never or rarely used totaled a whopping 64% while sometimes, often and always weighed in with 16%, 13% and 7% respectively. For those acquainted with the Pareto principle (80/20 rule), notice how the often and always used features - those things we should concentrate on building for our customers and those things things that bring us the most value – is exactly 80%. In other words, a great deal of our effort is generally spent creating things that customers do not use or want.

2 MIN2016 AUG 16
Comments
Agile Principles: Simplicity is Essential

Latest Episodes

Agile Principles: Team Reflection Provides Growth

Retrospectives are my favorite of all the scrum activities because they represent the opportunity to reflect on how we are implementing and to adjust our behavior to be more effective. I have said to my teams on many occasions that if I were forced to choose only one scrum ceremony that my choice, without hesitation or reservation, would be the retrospective. Without it, how could we ever expect to improve? What essential difference would an “Agile” project have over the many death march projects that teams have come to accept?

8 MIN2016 AUG 16
Comments
Agile Principles: Team Reflection Provides Growth

Agile Principles: Why You Need Self-Organizing Teams

I have often argued that the founders of Agile did not provide reasons why their approaches worked just that they did. Their was empirical evidence, proven by doing the work, or, as they state in the beginning of the manifesto - uncovering better ways of developing software by doing it and helping others do it. From their very pragmatic approach, they figured out that better software was created by following the values and principles. One of those discoveries was that better software was created by self-organizing teams.

3 MIN2016 AUG 16
Comments
Agile Principles: Why You Need Self-Organizing Teams

Agile Principles: Simplicity is Essential

In 2002, Jim Johnson of the Standish Group (made famous by their Chaos Report of software project “success”) presented findings of features and functions used in a typical system. The number of features that were never or rarely used totaled a whopping 64% while sometimes, often and always weighed in with 16%, 13% and 7% respectively. For those acquainted with the Pareto principle (80/20 rule), notice how the often and always used features - those things we should concentrate on building for our customers and those things things that bring us the most value – is exactly 80%. In other words, a great deal of our effort is generally spent creating things that customers do not use or want.

2 MIN2016 AUG 16
Comments
Agile Principles: Simplicity is Essential

Listen Now On Himalaya