Effective Agile Blog
 
     

Effective Scrum and High Quality Code – It Is a Chicken and Egg Relationship

Effective Scrum and High Quality Code – It Is a Chicken and Egg Relationship
Scrum is simple, but Scrum is Hard.  Scrum is so simple that it can be explained in 20 minutes, but so hard that some teams are never effective.  Yet other teams produce 3-10 times more business value than they did before.  This article will go into one of the main differences between under-performing teams and very successful teams— Code Quality—and its impact on the effectiveness of every Scrum team.  You will learn how to present the business case for high quality code, how to facilitate the establishment of a business commitment to high quality code, and how to implement the process of transforming code quality to an enabler rather than a restrainer of the delivery of business value within your organization.

Agile's Impact on Product Development

Dec 10 2009
2
0

 Agile and it's various implementations, including Scrum, while most often discussed in software development circles,  can correctly be classified as Product Development methodologies. Most of the time the product being developed has software as a major component, but they are products developed to solve a problem or make a job easier or more efficient.  When we think about products in this broader context we can often identify some impacts on product management rooted in the Agile practices and thought process. We need to understand these impacts to be prepared to mitigate them and propel the organization to the next level.

 
 
 

Bugs, bugs, BUGS!

Jul 07 2009
8
0
 I'm sure that you all know the story of how the term "bug" got associated with a computer failure. It was a moth in a computer which caused a hardware failure. However, since then the term bug  has become synonymous with a software error. There is a bug in the program. Yes, there is a bug in the program, every program. Many software development organizations spend a large portion of their time and effort finding and fixing bugs. However the situation rarely improves. hbrfj8e3c4

Do you know your team's "room tone"?

Jul 06 2009
3
0
 As a ScrumMaster and Agile Coach, I develop the same feeling about the team's work environment. Depending on the team the "room tone" will be different and in iterative development the tone will be different depending on the stage of the iteration the team is in.

Scrum is a flexible process!

Jun 10 2009
11
0
 I’m a white board and sticky type of agilest. Give me a team room with white boards and a bunch of multicolored stickys and I’m a happy camper! Why? Because I know that the white board and stickys are NOT the project, the people and the conversations they have with each other are the project and the white boards and stickys are used to drive those conversations and track the work. However for most teams and most organizations, my agile dream project just does not exist and trying to force it to be is foolishness. Most organizations are going to need a tool to manage the project and provide visibility

Software Development Process Improvement for Enterprise Sustainability, Why Scrum, Agile and Lean?

May 15 2009
2
0
 There is a lot of information out there about why an organization would attempt to improve their software development process using any of the wide variety of methodologies, techniques, systems, coaches and mentors that market their message. In fact there is so much information it is overwhelming to anyone genuinely trying to improve their process. I've been out in the trenches for several years now and have seen many different approaches used with varying degrees of success. In fact no two organizations have ever done the same thing or had the same results.
Tag Cloud
Post History
Blog Archive
2015 Dec  75  1
2015 May  9  1
2013 May  116  1
2011 May  3  1
2009 Dec  4  2
2009 Nov  0  1
2009 Jul  11  2
2009 Jun  11  1
2009 May  2  1
2009 Apr  1  2
Rod's Articles on ezineaticles.com

Get Aggregated RSS

The Role of the Product Owner in Scrum

Friday, June 19, 2009

The goal of the Product Owner must be to deliver the right business value. To do this, they engage the team(s) to create solutions that deliver the business value. The Product Owner is listening to and evaluating the needs of the stakeholder community. They must have a great business sense and understand their market and customers. They must understand what is technically possible. From all this input they deliver a stream of input to the team about what the priorities are. They are constantly updating this information and evaluating the output of the team to check it for completeness and correctness.

Scrum is a Flexible Process!

Tuesday, June 16, 2009

Most organizations reacquire a tool to help manage complex distributed team projects. To be Agile the tool must be flexible.

From rod-claar.net
Scrum Alliance REP

REP

Scrum Alliance

Contact Us
Effective Agile Development LLC
4676 Commercial St. SE #193
Salem, Oregon 97302
Toll Free - (888) 294-1865
Info@effectiveagiledev.com
Connect
  • Twitter
  • Facebook
  • Google+
  • LinkedIn
  • rod-claar.net