Skip to main content

Examples of Visualizations

Perhaps someone has already thought about the human brain's propensity to match patterns... if this has happened - would we see a patten in this behavior?  If there was a patten, you think someone would have written a book on the subject.



Five of the most influential data visualization of all time  by Andy Cotgreave, Tableau Software.

The Periodic Table of Visualization Methods (aside: why people abuse the notion of the Periodic table of elements is puzzling to me - it's not just a table with iconic status - it's a predictive model in action; ... meanwhile, back to the visualization methods...) awesome chart with wonderful pop-ups to explain all the visualization methods.



So let's just go right ahead and include the predictive model of Mendeleev's table.


Example of the Periodic Table style applied to Scrum by my friend and colleague KaTe.
by Kate Terlecka
Agile Fluency model by Larsen and Shore - a intro video by James Shore: Your Path through Agile Fluency.








When you're into visual info, books on work processes, wonder and humor... you need a crateful of grateful - bet ya can get it at www.getlit.me here's a sample of Todd's book review info graphics.
Succeeding with Agile Governance

The author Niels Pflaeging has quite a few illustrations in his writings about organizational structures.




Want to visualize what that conference call really looks like - watch this video.


from Tripp and Tyler


Visualize the 5 SOLID class design principles.


Visualize what an org. chart should look like (if it was to be a useful tool; rather than an ego booster):

The secret to Walt Disney's Creativity - an Organigraph.


Visual.ly presents an interactive graphic depicting various sorting algorithms.


Big O notation cheat sheet. "This webpage covers the space and time Big-O complexities of common algorithms used in Computer Science."


The Cockburn project classification scale is a wonderful visualization for viewing projects as a group of activities and then deciding what process might fit around that project well.  I was very impressed the first time a saw Alistair's work on this, and it has stood the test of time.

Brian Marick's testing quadrants -- from a presentation by Lisa Crispin & Janet Gregory (see their book Agile Testing).



Linux (unix) performance management tools and the OS architecture stack.

Read Also:

Why Humans are Obsessed with Circles
Post a Comment

Most Popular on Agile Complexification Inverter

David's notes on "Drive"

- "The Surprising Truth about what Motivates Us" by Dan Pink.

Amazon book order
What I notice first and really like is the subtle implication in the shadow of the "i" in Drive is a person taking one step in a running motion.  This brings to mind the old saying - "there is no I in TEAM".  There is however a ME in TEAM, and there is an I in DRIVE.  And when one talks about motivating a team or an individual - it all starts with - what's in it for me.

Introduction

Pink starts with an early experiment with monkeys on problem solving.  Seems the monkeys were much better problem solver's than the scientist thought they should be.  This 1949 experiment is explained as the early understanding of motivation.  At the time there were two main drivers of motivation:  biological & external influences.  Harry F. Harlow defines the third drive in a novel theory:  "The performance of the task provided intrinsic reward" (p 3).  This is Dan Pink's M…

Elements of an Effective Scrum Task Board

What are the individual elements that make a Scrum task board effective for the team and the leadership of the team?  There are a few basic elements that are quite obvious when you have seen a few good Scrum boards... but there are some other elements that appear to elude even the most servant of leaders of Scrum teams.









In general I'm referring to a physical Scrum board.  Although software applications will replicated may of the elements of a good Scrum board there will be affordances that are not easily replicated.  And software applications offer features not easily implemented in the physical domain also.





Scrum Info Radiator Checklist (PDF) Basic Elements
Board Framework - columns and rows laid out in bold colors (blue tape works well)
Attributes:  space for the total number of stickies that will need to belong in each cell of the matrix;  lines that are not easy eroded, but are also easy to replace;  see Orientation.

Columns (or Rows) - labeled
    Stories
    To Do
    Work In P…

Exercise:: Definition of Ready & Done

Assuming you are on a Scrum/Agile software development team, then one of the first 'working agreements' you have created with your team is a 'Definition of Done' - right?



Oh - you don't have a definition of what aspects a user story that is done will exhibit. Well then, you need to create a list of attributes of a done story. One way to do this would be to Google 'definition of done' ... here let me do that for you: http://tinyurl.com/3br9o6n. Then you could just use someone else's definition - there DONE!

But that would be cheating -- right? It is not the artifact - the list of done criteria, that is important for your team - it is the act of doing it for themselves, it is that shared understanding of having a debate over some of the gray areas that create a true working agreement. If some of the team believes that a story being done means that there can be no bugs found in the code - but some believe that there can be some minor issues - well, …

What belongs on the Task Board?

I wonder about these questions a lot - what types of task belong on the task board?  Does every task have to belong to a Story?  Are some tasks just too small?  Are some tasks too obvious?  Obviously some task are too larger, but when should it be decomposed?  How will we know a task is too large?

I answer these questions with a question.  What about a task board motivates us to get work done?  The answer is: T.A.S.K.S. to DONE!



Inherent in the acronym TASKS is the point of all tasks, to get to done.  That is the measure of if the task is the right size.  Does it motivate us to get the work done?  (see notes on Dan Pink's book: Drive - The surprising Truth about what motivates us) If we are forgetting to do some class of task then putting it on the board will help us remember.  If we think some small task is being done by someone else, then putting it on the board will validate that someone else is actually doing it.  If a task is obvious, then putting it on the board will take vi…

Refactoring - examples from the book

Martin Fowler's book Refactoring:  Improving the Design of Existing Code has a simple example of a movie rental domain model, which he refactors from a less than ideal object-oriented design to a more robust OO design. Included in this Refactoring_FirstExample.zip Zip file are the Java source code files of the Movie, Rental, and Customer classes. Along with a JUnit CustomerTest class. Using these example source files you too can follow along with the refactoring that Fowler presents in the first few chapters of his book.