ChiefSimplicityOfficer.com

Search
Skip to content
  • About Me
  • Calendar
  • Simplifications
    • Simplifying Business
    • Simplifying Software
    • Simplifying Life
  • Downloads

Monthly Archives: February 2011

Extreme Programming, Scrum, Simplifying Software

Top 5 Agile Practices

February 1, 2011 Craig Jones 1 Comment

I took an informal survey at Code Camp this weekend.  I asked my fellow presenters what they considered to be the most important practices to start with when ramping up a new agile team.  Here are the top 5 answers, in no particular order… Continue reading Top 5 Agile Practices →

backlogcontinuous integrationdemosfeedbackstandups

a blog by Craig L. Jones, Software Agilist

Craig L. Jones

(714) 955-4025
craig@chiefsimplicityofficer.com
http://www.linkedin.com/in/craigjones

Let’s All Be More “Simple-Minded”

Photo of Craig L. Jones Complexity comes easily. Simplicity is hard work.

For example, we are quick to say, "There ought to be a law..." You hear that all the time, but when was the last time you heard someone say, "Oh, we don't need that law anymore."?

 

Simplicity means constantly asking, "is there a better way?" — Achieving simplicity takes awareness, practice, vigilance, and even a pinch of humility. As a Software Craftsmanship coach, I always begin an engagement by discussing the nature of simplicity. I get the teams to hang a vocabulary on the nuances of simplicity and then make those ideas prominent in our planning and retrospective discussions.

 

This site is dedicated to the nature of simplicity. To learn more, I invite you to: attend my free lectures (see the Calendar page), read and comment on my blog posts (explore the categories and tags, below), or contact me directly, for any reason, or just to say Hi. In the mean time, pull down the "Simplifications" menu, above, and choose a starting point: Simplifying Business, Simplifying Software, or Simplifying Life.

Topics

  • Blog Notes (6)
  • Book Reviews (3)
  • Events (12)
  • Extreme Programming (12)
  • Getting Things Done (GTD) (3)
  • Lean/Kanban (5)
  • Pragmatic Marketing (3)
  • Product Reviews (1)
  • Scrum (18)
  • Simplifying Business (26)
  • Simplifying Life (3)
  • Simplifying Software (34)
  • Tangents and Asides (4)

Archives

  • July 2015 (3)
  • June 2015 (1)
  • August 2014 (1)
  • December 2011 (1)
  • October 2011 (2)
  • September 2011 (4)
  • August 2011 (3)
  • July 2011 (5)
  • June 2011 (1)
  • May 2011 (3)
  • April 2011 (1)
  • March 2011 (1)
  • February 2011 (1)
  • January 2011 (3)
  • December 2010 (2)
  • November 2010 (1)
  • October 2010 (3)
  • September 2010 (1)
  • August 2010 (2)
  • June 2010 (1)
  • April 2010 (4)
  • March 2010 (2)
  • February 2010 (12)

Recent Posts

  • My Recent Guest Blogging for ThotSpots
  • Only One Retrospective Action-Item at a Time
  • Rookie Mistake: Jumping to Conclusions with Presumed Solutions
  • Counter-Intuition: The Confounding Implications of Ticket-Count Stats
  • Converting Between Go Unit Test Styles

Tags

analysis best practices Book Reviews brainstorming clean code code camp complexity continuous deployment continuous integration conventions design principles GaWaTa groovy hiding complexity INVEST Java Kanban laws of simplicity lean software development links naming conventions pair programming Pragmatic Marketing problem solving product management programming requirements analysis retrospectives Robert Martin role-based security Sarbanes-Oxley Scrum security segregation of duties separation of concerns simplicity simplicity examples speaking engagements standards storyboard TDD technical debt UC Irvine unit testing user stories

Blogroll

  • codejacked.com
  • ThotSpots

Scrum/Agile Resources

  • Agile Project Leadership Network
  • Agile Project Leadership Network, Orange County
  • The Agile Alliance
  • The Scrum Alliance
Proudly powered by WordPress