Skip to main content

8 reasons to buy an iPad for your team room.

Will you buy an iPad?  That was the question in March 2010.  Here is the answer - iPad sales over 14 months.
8 reasons to buy an iPad for your team room.

  1. Easy to carry to meeting (compared to laptop and power supply).
  2. Makes a person look smart compared to the person with the laptop, power supply, wired mouse, wired web cam that needs to get up and walk around the conference table to get a close-up shot of the white board.
  3. Apps that are designed to work instantly and quickly give the information you need without minutes of drill-down menu clicking and searching.
  4. Instant on (compared to opening a laptop that has its lid shut - because shutting the lid is a sign that you are present and paying attention to the meeting).
  5. Early adopters have acted - now you can hop on the bandwagon.
  6. Smiles on team members face's is a sign of a performing team.
  7. Have a need - there is an App for that, 65000 of them.
  8. Facetime - video calls that just work.  And with iOS5 sync to the big screen in a team room with a few touches (AirPlay -> Apple TV).

Here's a developer preview iOS 5 running on the iPad and Apple TV to do just that - share what ever is on the iPad with the TV big screen.  This could include the FaceTime call with the remote team.


by CNETTV on Aug 4, 2011


Want to connect remote Agile teams?  I suggest you buy an iPad 2 for each team location.  Use it as the video conference system - cost $1000 (2 wifi iPads).  Benefit - instant easy access to the members of the other team via a shared video conference system that is portable, easy to setup, easy to use, gives high quality images.  And does more than just video - it becomes a communication tool. 

I mentioned this to a colleague and he suggested that if one could link the FaceTime video on the iPad 2 with Apple TV via the AirPlay protocol then one would have an awesome video conference tool.  Imagine the easy of use with two remote locations using iPads with FaceTime chatting and the ability to put the remote video on the big screen (Apple TV large screen TV or projector).

Last year Apple had not enabled this video sharing over AirPlay... yet.  But I've asked for it.  And now with iOS 5, Apple is delivering.  That is innovation.


Related Links:

Bashing the iPad - but will you purchase? Jan 2010

The Macalope Weekly: Say, this iPad thing may really take off

What competes with an iPad? 

What replaces co-location in Agile?

Agile tools for your iPhone/iPad

Long Distance Communication Timeline  it ends at FaceTime

Post a Comment

Most Popular on Agile Complexification Inverter

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, …

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…

Webinar: Collaboration at Scale: Defining Done, Ready, and NO.

I was invited to participate in a Scrum Alliance Webinar.  Maybe you would like to listen to us in a discussion of techniques to collaborate at scale (remotely and with many people).  The topic is one that I've got some experience in discussions - yet I never seem to get to done...
Collaboration at Scale: Defining Done and Ready and NO for Distributed Teams
With Joel Bancroft-Connors, Agile Organizational Coach; David A. Koontz, Agile Transition Guide; and Luke Hohmann, CEO and Founder of Conteneo, Inc.


14 February 2018 11 a.m. ET (USA).




The Scrum Guide is pretty clear on the criticality of the definition of Done: "When a Product Backlog item or an Increment is described as "Done," everyone must understand what "Done" means. However, the Scrum Guide ALSO says that the definition of Done can "vary significantly per Scrum Team." This leads us to examine when and how the definition of Done should vary, how distributed teams should cr…

A T-Shaped 21st Century Knowledge Worker

Knowledge workers in the 21st Century must have many areas of deep knowledge, while also be capable of collaboration across multiple other domains with dissimilar T-shaped individuals.  This description of a person is a metaphor.  Compare it to the shape of the "I" in the classic saying there is no "I" in Team.


I first read about Scott Ambler's term "Generalizing Specialist" - but it's so hard to remember the proper order of the words... get it backwards and it has an inverted meaning... T-Shaped is easier to remember. 
A generalizing specialist is someone who:
Has one or more technical specialties (e.g. Java programming, Project Management, Database Administration, ...). Has at least a general knowledge of software development. Has at least a general knowledge of the business domain in which they work. Actively seeks to gain new skills in both their existing specialties as well as in other areas, including both technical and domain areas.  General…

A FAILURE to Communicate

I was working with a failing team some time ago.  I use "failing" to describe the outcome of the team - not the people on the team.  Are you OK with that description?



An issue arrose in the stand up - a team member that was to verify the quality of a procedure did so and reported that there were a few records that didn't match expectation in the data set.  Upon inquire the number of records not matching was over 2000.  Most people acknowledged immediately the exaggeration - I could tell by the laughter.  After about 10 minutes of discussing the details of the problem - it appeared the team had a handle on the specific situation.

I stopped the discussion and inquired if they could name the impediment.  One team member did a great job of describing the impediment as a _communication gap_.  Wonderful - I could work with that - the problem had a name and it didn't include anyones Proper Name.

"If the problem has a first name; we are going to have a problem."

I&#…