<?xml version='1.0' encoding='UTF-8'?><?xml-stylesheet href="http://www.blogger.com/styles/atom.css" type="text/css"?><feed xmlns='http://www.w3.org/2005/Atom' xmlns:openSearch='http://a9.com/-/spec/opensearchrss/1.0/' xmlns:georss='http://www.georss.org/georss' xmlns:gd='http://schemas.google.com/g/2005' xmlns:thr='http://purl.org/syndication/thread/1.0'><id>tag:blogger.com,1999:blog-10332387</id><updated>2012-01-24T07:16:48.560-05:00</updated><category term='pair progrmming'/><category term='mobile'/><category term='facebook'/><category term='startup cto'/><category term='business plans'/><category term='java'/><category term='cloud computing'/><category term='it management'/><category term='enterprise 2.0'/><category term='sandisk'/><category term='apple'/><category term='security'/><category term='offshore development'/><category term='customer service'/><category term='web development'/><category term='agile software development'/><category term='business exchange'/><category term='links'/><category term='organizational change'/><category term='site performance'/><category term='software development'/><category term='media and publishing'/><category term='dell'/><category term='content agility'/><category term='SaaS'/><category term='in the news'/><category term='product management'/><category term='amazon'/><category term='web 2.0'/><category term='twitter'/><category term='crisis management'/><category term='innovation'/><category term='about me'/><category term='agile planning'/><category term='microsoft'/><category term='standards'/><category term='cio'/><category term='rhapsody'/><category term='project management'/><category term='software qa'/><category term='social media'/><category term='jetblue'/><category term='google'/><title type='text'>Social, Agile, and Transformation</title><subtitle type='html'>I cover several topics including agile software development,   software startups, web 2.0, social networking, SaaS, content management, media, enterprise 2.0 and business transformation.</subtitle><link rel='http://schemas.google.com/g/2005#feed' type='application/atom+xml' href='http://ctotodevelopers.blogspot.com/feeds/posts/default'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/10332387/posts/default?max-results=100'/><link rel='alternate' type='text/html' href='http://ctotodevelopers.blogspot.com/'/><link rel='hub' href='http://pubsubhubbub.appspot.com/'/><link rel='next' type='application/atom+xml' href='http://www.blogger.com/feeds/10332387/posts/default?start-index=101&amp;max-results=100'/><author><name>Isaac Sacolick</name><uri>https://profiles.google.com/109747073147504760416</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='32' src='//lh4.googleusercontent.com/-pgtwy5F24tA/AAAAAAAAAAI/AAAAAAAAAAA/ZfSNeF9Egr8/s512-c/photo.jpg'/></author><generator version='7.00' uri='http://www.blogger.com'>Blogger</generator><openSearch:totalResults>140</openSearch:totalResults><openSearch:startIndex>1</openSearch:startIndex><openSearch:itemsPerPage>100</openSearch:itemsPerPage><entry><id>tag:blogger.com,1999:blog-10332387.post-2075261375847880640</id><published>2012-01-24T07:16:00.000-05:00</published><updated>2012-01-24T07:16:48.571-05:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='about me'/><category scheme='http://www.blogger.com/atom/ns#' term='cio'/><title type='text'>CIO Advice: Listen, Answer The Question, Provide Insights</title><summary type='text'>
I was relatively young when I attended my first board meeting. At the time, the board for my startup consisted of executives from some of the major media and newspaper companies including Hearst, Advance, Scripps, and Media News Group. This was back is 1998 or 1999, and like all Boards, they wanted to know how we were growing our business. They had few technology questions, though I do remember </summary><link rel='replies' type='application/atom+xml' href='http://ctotodevelopers.blogspot.com/feeds/2075261375847880640/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://ctotodevelopers.blogspot.com/2012/01/cio-advice-listen-answer-question.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/10332387/posts/default/2075261375847880640'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/10332387/posts/default/2075261375847880640'/><link rel='alternate' type='text/html' href='http://ctotodevelopers.blogspot.com/2012/01/cio-advice-listen-answer-question.html' title='CIO Advice: Listen, Answer The Question, Provide Insights'/><author><name>Isaac Sacolick</name><uri>https://profiles.google.com/109747073147504760416</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='32' src='//lh4.googleusercontent.com/-pgtwy5F24tA/AAAAAAAAAAI/AAAAAAAAAAA/ZfSNeF9Egr8/s512-c/photo.jpg'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-10332387.post-1196388148880339116</id><published>2011-11-30T07:30:00.000-05:00</published><updated>2011-11-30T08:46:48.560-05:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='agile software development'/><category scheme='http://www.blogger.com/atom/ns#' term='innovation'/><category scheme='http://www.blogger.com/atom/ns#' term='cio'/><title type='text'>Top Ten Attributes of Agile Platforms</title><summary type='text'>
In my last post, I stated that technology teams could achieve a 2X speed to market by leveraging agile platforms. Here are my top ten attributes of agile platforms:




Fast and easy to learn - It lets average developers learn and be productive with short ramp up time. It has a combination of tools and documentation that lets my whole team start using it quickly.
Built on standards - Because its</summary><link rel='replies' type='application/atom+xml' href='http://ctotodevelopers.blogspot.com/feeds/1196388148880339116/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://ctotodevelopers.blogspot.com/2011/11/top-ten-attributes-of-agile-platforms.html#comment-form' title='1 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/10332387/posts/default/1196388148880339116'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/10332387/posts/default/1196388148880339116'/><link rel='alternate' type='text/html' href='http://ctotodevelopers.blogspot.com/2011/11/top-ten-attributes-of-agile-platforms.html' title='Top Ten Attributes of Agile Platforms'/><author><name>Isaac Sacolick</name><uri>https://profiles.google.com/109747073147504760416</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='32' src='//lh4.googleusercontent.com/-pgtwy5F24tA/AAAAAAAAAAI/AAAAAAAAAAA/ZfSNeF9Egr8/s512-c/photo.jpg'/></author><thr:total>1</thr:total></entry><entry><id>tag:blogger.com,1999:blog-10332387.post-3992867636188547459</id><published>2011-10-28T07:24:00.001-04:00</published><updated>2011-10-28T07:24:34.689-04:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='agile software development'/><category scheme='http://www.blogger.com/atom/ns#' term='project management'/><category scheme='http://www.blogger.com/atom/ns#' term='innovation'/><category scheme='http://www.blogger.com/atom/ns#' term='cio'/><title type='text'>Achieving 2X in Speed To Market Using Agile Platforms</title><summary type='text'>


Wenger Giant Swiss Army Knife

Developing extendable technology  platforms is what makes agile teams and agile businesses nimble. For simplicity I'm going to call a platform as any single or stack of technologies that are leveraged in more than one product or business process. Since a product or business process is somewhat fungible, what I really mean is more than one application developed </summary><link rel='replies' type='application/atom+xml' href='http://ctotodevelopers.blogspot.com/feeds/3992867636188547459/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://ctotodevelopers.blogspot.com/2011/10/achieving-2x-in-speed-to-market-using.html#comment-form' title='2 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/10332387/posts/default/3992867636188547459'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/10332387/posts/default/3992867636188547459'/><link rel='alternate' type='text/html' href='http://ctotodevelopers.blogspot.com/2011/10/achieving-2x-in-speed-to-market-using.html' title='Achieving 2X in Speed To Market Using Agile Platforms'/><author><name>Isaac Sacolick</name><uri>https://profiles.google.com/109747073147504760416</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='32' src='//lh4.googleusercontent.com/-pgtwy5F24tA/AAAAAAAAAAI/AAAAAAAAAAA/ZfSNeF9Egr8/s512-c/photo.jpg'/></author><thr:total>2</thr:total></entry><entry><id>tag:blogger.com,1999:blog-10332387.post-6995304034288709500</id><published>2011-10-10T23:04:00.000-04:00</published><updated>2011-10-10T23:04:29.740-04:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='product management'/><category scheme='http://www.blogger.com/atom/ns#' term='agile planning'/><category scheme='http://www.blogger.com/atom/ns#' term='agile software development'/><category scheme='http://www.blogger.com/atom/ns#' term='innovation'/><title type='text'>Simple Agile Product Development</title><summary type='text'>
I firmly believe the best products are simple.

What does simple mean? Simple to use, simple to understand, simple to sell, simple to market, simple to engineer, simple to test, simple to deploy.

Simplicity comes from design patterns, reuse, and focus. User interfaces need to be easily understood. Our brains understand patterns; color schemes, design elements, navigation, messages, </summary><link rel='replies' type='application/atom+xml' href='http://ctotodevelopers.blogspot.com/feeds/6995304034288709500/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://ctotodevelopers.blogspot.com/2011/10/simple-agile-product-development.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/10332387/posts/default/6995304034288709500'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/10332387/posts/default/6995304034288709500'/><link rel='alternate' type='text/html' href='http://ctotodevelopers.blogspot.com/2011/10/simple-agile-product-development.html' title='Simple Agile Product Development'/><author><name>Isaac Sacolick</name><uri>https://profiles.google.com/109747073147504760416</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='32' src='//lh4.googleusercontent.com/-pgtwy5F24tA/AAAAAAAAAAI/AAAAAAAAAAA/ZfSNeF9Egr8/s512-c/photo.jpg'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-10332387.post-4146119069886393695</id><published>2011-09-22T07:41:00.000-04:00</published><updated>2011-09-22T07:43:51.082-04:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='mobile'/><category scheme='http://www.blogger.com/atom/ns#' term='innovation'/><category scheme='http://www.blogger.com/atom/ns#' term='about me'/><category scheme='http://www.blogger.com/atom/ns#' term='cio'/><title type='text'>Being a CIO: One Year Later</title><summary type='text'>
Last year, I published a series on my first hundred days as CIO at McGraw-Hill Construction. I've largely been quiet since then, unfortunately (from a blogging perspective), with my head down working with the Business and IT teams. We've rolled out some new products like Dodge SpecShare Suite, upgraded several technology platforms, and established an agile project management office among many </summary><link rel='replies' type='application/atom+xml' href='http://ctotodevelopers.blogspot.com/feeds/4146119069886393695/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://ctotodevelopers.blogspot.com/2011/09/being-cio-one-year-later.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/10332387/posts/default/4146119069886393695'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/10332387/posts/default/4146119069886393695'/><link rel='alternate' type='text/html' href='http://ctotodevelopers.blogspot.com/2011/09/being-cio-one-year-later.html' title='Being a CIO: One Year Later'/><author><name>Isaac Sacolick</name><uri>https://profiles.google.com/109747073147504760416</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='32' src='//lh4.googleusercontent.com/-pgtwy5F24tA/AAAAAAAAAAI/AAAAAAAAAAA/ZfSNeF9Egr8/s512-c/photo.jpg'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-10332387.post-3219460116166625313</id><published>2011-09-15T18:07:00.001-04:00</published><updated>2011-09-15T18:08:55.856-04:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='product management'/><category scheme='http://www.blogger.com/atom/ns#' term='agile planning'/><category scheme='http://www.blogger.com/atom/ns#' term='agile software development'/><category scheme='http://www.blogger.com/atom/ns#' term='software development'/><category scheme='http://www.blogger.com/atom/ns#' term='project management'/><category scheme='http://www.blogger.com/atom/ns#' term='cio'/><title type='text'>How to Kill Projects and Develop Agile Programs Part 2</title><summary type='text'>
In How to Kill Projects and Develop Agile Programs Part 1, I listed the first steps in moving from projects to programs. Embrace but control projects, execute the agile process, identify and measure productivity impediments.

All three are important. What you need to demonstrate is that you have a team that is transparent, productive, and can execute on business priorities. You want business </summary><link rel='replies' type='application/atom+xml' href='http://ctotodevelopers.blogspot.com/feeds/3219460116166625313/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://ctotodevelopers.blogspot.com/2011/09/how-to-kill-projects-and-develop-agile.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/10332387/posts/default/3219460116166625313'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/10332387/posts/default/3219460116166625313'/><link rel='alternate' type='text/html' href='http://ctotodevelopers.blogspot.com/2011/09/how-to-kill-projects-and-develop-agile.html' title='How to Kill Projects and Develop Agile Programs Part 2'/><author><name>Isaac Sacolick</name><uri>https://profiles.google.com/109747073147504760416</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='32' src='//lh4.googleusercontent.com/-pgtwy5F24tA/AAAAAAAAAAI/AAAAAAAAAAA/ZfSNeF9Egr8/s512-c/photo.jpg'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-10332387.post-4620166929387334729</id><published>2011-08-09T16:30:00.002-04:00</published><updated>2011-08-09T19:30:04.109-04:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='organizational change'/><category scheme='http://www.blogger.com/atom/ns#' term='product management'/><category scheme='http://www.blogger.com/atom/ns#' term='agile planning'/><category scheme='http://www.blogger.com/atom/ns#' term='agile software development'/><category scheme='http://www.blogger.com/atom/ns#' term='project management'/><category scheme='http://www.blogger.com/atom/ns#' term='innovation'/><category scheme='http://www.blogger.com/atom/ns#' term='it management'/><category scheme='http://www.blogger.com/atom/ns#' term='cio'/><title type='text'>Trying to Develop a Death Star or a Flux Capacitor?</title><summary type='text'>This was the question I asked a Product Owner last week. I was encouraging him to think small and simple. I suggested the flux capacitor, a "simple" invention engineered by one man that changed the world. Don't try to build that death star that required a large army of storm troopers and the powers of the dark force to construct.

I thought about this discussion all weekend because, after many </summary><link rel='replies' type='application/atom+xml' href='http://ctotodevelopers.blogspot.com/feeds/4620166929387334729/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://ctotodevelopers.blogspot.com/2011/08/trying-to-develop-death-star-or-flux.html#comment-form' title='3 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/10332387/posts/default/4620166929387334729'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/10332387/posts/default/4620166929387334729'/><link rel='alternate' type='text/html' href='http://ctotodevelopers.blogspot.com/2011/08/trying-to-develop-death-star-or-flux.html' title='Trying to Develop a Death Star or a Flux Capacitor?'/><author><name>Isaac Sacolick</name><uri>https://profiles.google.com/109747073147504760416</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='32' src='//lh4.googleusercontent.com/-pgtwy5F24tA/AAAAAAAAAAI/AAAAAAAAAAA/ZfSNeF9Egr8/s512-c/photo.jpg'/></author><media:thumbnail xmlns:media='http://search.yahoo.com/mrss/' url='http://3.bp.blogspot.com/-fmGOK2YiTNc/TkFMiUaHU4I/AAAAAAAAADg/KTeabN8TIq8/s72-c/flux+capacitor.JPG' height='72' width='72'/><thr:total>3</thr:total></entry><entry><id>tag:blogger.com,1999:blog-10332387.post-5787129206039633414</id><published>2011-06-20T06:12:00.000-04:00</published><updated>2011-06-20T06:12:12.790-04:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='organizational change'/><category scheme='http://www.blogger.com/atom/ns#' term='product management'/><category scheme='http://www.blogger.com/atom/ns#' term='agile planning'/><category scheme='http://www.blogger.com/atom/ns#' term='project management'/><category scheme='http://www.blogger.com/atom/ns#' term='innovation'/><category scheme='http://www.blogger.com/atom/ns#' term='cio'/><title type='text'>How to Kill Projects and Develop Agile Programs Part 1</title><summary type='text'>Last post I covered why product development organizations need to kill projects and move to agile programs Here's how:

1) Embrace, but control projects

The first thing to realize is that there is an organizational dynamic around projects. So trying to "kill projects" in one step just isn't going to work and you'll get wrapped up in many change management challenges.

Instead, I suggest doing </summary><link rel='replies' type='application/atom+xml' href='http://ctotodevelopers.blogspot.com/feeds/5787129206039633414/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://ctotodevelopers.blogspot.com/2011/06/how-to-kill-projects-and-develop-agile.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/10332387/posts/default/5787129206039633414'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/10332387/posts/default/5787129206039633414'/><link rel='alternate' type='text/html' href='http://ctotodevelopers.blogspot.com/2011/06/how-to-kill-projects-and-develop-agile.html' title='How to Kill Projects and Develop Agile Programs Part 1'/><author><name>Isaac Sacolick</name><uri>https://profiles.google.com/109747073147504760416</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='32' src='//lh4.googleusercontent.com/-pgtwy5F24tA/AAAAAAAAAAI/AAAAAAAAAAA/ZfSNeF9Egr8/s512-c/photo.jpg'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-10332387.post-7286120659085895996</id><published>2011-06-09T07:45:00.001-04:00</published><updated>2011-06-09T07:45:00.852-04:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='organizational change'/><category scheme='http://www.blogger.com/atom/ns#' term='product management'/><category scheme='http://www.blogger.com/atom/ns#' term='agile planning'/><category scheme='http://www.blogger.com/atom/ns#' term='project management'/><category scheme='http://www.blogger.com/atom/ns#' term='innovation'/><category scheme='http://www.blogger.com/atom/ns#' term='cio'/><title type='text'>Kill Projects and Develop Agile Programs</title><summary type='text'>My last couple of posts covered the need to define markets before products as the first shift in transforming product delivery. The second issue to tackle is shifting from projects to programs.

Projects kill product development organizations. By definition, a project assumes a beginning and an end. The beginning requires deigning, justifying, and planning the project. The end assumes that </summary><link rel='replies' type='application/atom+xml' href='http://ctotodevelopers.blogspot.com/feeds/7286120659085895996/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://ctotodevelopers.blogspot.com/2011/06/kill-projects-and-develop-agile.html#comment-form' title='8 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/10332387/posts/default/7286120659085895996'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/10332387/posts/default/7286120659085895996'/><link rel='alternate' type='text/html' href='http://ctotodevelopers.blogspot.com/2011/06/kill-projects-and-develop-agile.html' title='Kill Projects and Develop Agile Programs'/><author><name>Isaac Sacolick</name><uri>https://profiles.google.com/109747073147504760416</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='32' src='//lh4.googleusercontent.com/-pgtwy5F24tA/AAAAAAAAAAI/AAAAAAAAAAA/ZfSNeF9Egr8/s512-c/photo.jpg'/></author><thr:total>8</thr:total></entry><entry><id>tag:blogger.com,1999:blog-10332387.post-7116750760070377538</id><published>2011-05-20T08:00:00.002-04:00</published><updated>2011-05-20T08:00:11.257-04:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='organizational change'/><category scheme='http://www.blogger.com/atom/ns#' term='product management'/><category scheme='http://www.blogger.com/atom/ns#' term='agile planning'/><category scheme='http://www.blogger.com/atom/ns#' term='project management'/><category scheme='http://www.blogger.com/atom/ns#' term='innovation'/><category scheme='http://www.blogger.com/atom/ns#' term='cio'/><title type='text'>Keys to Successful Product Definition</title><summary type='text'>In my last post, I discussed some of the key questions around market definition and suggested that in most situations, answers to these questions are needed before going into product or service definition. My rationale is simple

There are many possible product or service definitions possible for a single market.
I believe that optimal product definition is a collaborative process. 
Product </summary><link rel='replies' type='application/atom+xml' href='http://ctotodevelopers.blogspot.com/feeds/7116750760070377538/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://ctotodevelopers.blogspot.com/2011/05/keys-to-successful-product-definition.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/10332387/posts/default/7116750760070377538'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/10332387/posts/default/7116750760070377538'/><link rel='alternate' type='text/html' href='http://ctotodevelopers.blogspot.com/2011/05/keys-to-successful-product-definition.html' title='Keys to Successful Product Definition'/><author><name>Isaac Sacolick</name><uri>https://profiles.google.com/109747073147504760416</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='32' src='//lh4.googleusercontent.com/-pgtwy5F24tA/AAAAAAAAAAI/AAAAAAAAAAA/ZfSNeF9Egr8/s512-c/photo.jpg'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-10332387.post-4344298723563027736</id><published>2011-05-11T08:45:00.006-04:00</published><updated>2011-05-19T20:53:59.998-04:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='organizational change'/><category scheme='http://www.blogger.com/atom/ns#' term='product management'/><category scheme='http://www.blogger.com/atom/ns#' term='agile planning'/><category scheme='http://www.blogger.com/atom/ns#' term='innovation'/><category scheme='http://www.blogger.com/atom/ns#' term='cio'/><title type='text'>Dear Product Manager, Think Markets Before Product Definition!</title><summary type='text'>My last post introduced the transformation from a product to a market and platform organization and from a projects to programs. The rationale behind these transformations is to get to a more agile, nimble product and technology organization that can support a larger number of development initiatives, both new and enhancement.


Key Questions to ask on Market Definition

Let's start with some </summary><link rel='replies' type='application/atom+xml' href='http://ctotodevelopers.blogspot.com/feeds/4344298723563027736/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://ctotodevelopers.blogspot.com/2011/05/dear-product-manager-think-markets.html#comment-form' title='3 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/10332387/posts/default/4344298723563027736'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/10332387/posts/default/4344298723563027736'/><link rel='alternate' type='text/html' href='http://ctotodevelopers.blogspot.com/2011/05/dear-product-manager-think-markets.html' title='Dear Product Manager, Think Markets Before Product Definition!'/><author><name>Isaac Sacolick</name><uri>https://profiles.google.com/109747073147504760416</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='32' src='//lh4.googleusercontent.com/-pgtwy5F24tA/AAAAAAAAAAI/AAAAAAAAAAA/ZfSNeF9Egr8/s512-c/photo.jpg'/></author><thr:total>3</thr:total></entry><entry><id>tag:blogger.com,1999:blog-10332387.post-4428563194790935325</id><published>2011-05-02T08:15:00.004-04:00</published><updated>2011-05-02T08:15:00.187-04:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='organizational change'/><category scheme='http://www.blogger.com/atom/ns#' term='product management'/><category scheme='http://www.blogger.com/atom/ns#' term='agile planning'/><category scheme='http://www.blogger.com/atom/ns#' term='agile software development'/><category scheme='http://www.blogger.com/atom/ns#' term='project management'/><category scheme='http://www.blogger.com/atom/ns#' term='innovation'/><category scheme='http://www.blogger.com/atom/ns#' term='about me'/><category scheme='http://www.blogger.com/atom/ns#' term='cio'/><title type='text'>Shifting to a Market, Program, and Platform Organization</title><summary type='text'>As technologists, product developers, and marketers, we all love to work on the brand new idea. It might be a simple enhancement or a whole new application to a new audience, we are all motivated by creating something new and the prospect of success. 

I spent the first half of my career working in startups where the thrill of building something new was easily attainable. Or was it? The truth is,</summary><link rel='replies' type='application/atom+xml' href='http://ctotodevelopers.blogspot.com/feeds/4428563194790935325/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://ctotodevelopers.blogspot.com/2011/05/shifting-to-market-program-and-platform.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/10332387/posts/default/4428563194790935325'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/10332387/posts/default/4428563194790935325'/><link rel='alternate' type='text/html' href='http://ctotodevelopers.blogspot.com/2011/05/shifting-to-market-program-and-platform.html' title='Shifting to a Market, Program, and Platform Organization'/><author><name>Isaac Sacolick</name><uri>https://profiles.google.com/109747073147504760416</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='32' src='//lh4.googleusercontent.com/-pgtwy5F24tA/AAAAAAAAAAI/AAAAAAAAAAA/ZfSNeF9Egr8/s512-c/photo.jpg'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-10332387.post-7164836588320483884</id><published>2011-03-08T06:48:00.000-05:00</published><updated>2011-03-08T06:48:02.064-05:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='site performance'/><category scheme='http://www.blogger.com/atom/ns#' term='agile software development'/><category scheme='http://www.blogger.com/atom/ns#' term='project management'/><category scheme='http://www.blogger.com/atom/ns#' term='cio'/><title type='text'>Agile Process Improvement Using .... Agile!</title><summary type='text'>When I talk to leaders and teams about agile and scrum, they get the basics right away - sprint length, stand ups, commitments, getting to done, and basic backlog management. After that, I'm usually asked a flood of questions. How do we engage the Business? How should we estimate? How do we handle forecasting end dates and financials? What should we do with stories that don't achieve 'done'? What</summary><link rel='replies' type='application/atom+xml' href='http://ctotodevelopers.blogspot.com/feeds/7164836588320483884/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://ctotodevelopers.blogspot.com/2011/03/agile-process-improvement-using-agile.html#comment-form' title='3 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/10332387/posts/default/7164836588320483884'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/10332387/posts/default/7164836588320483884'/><link rel='alternate' type='text/html' href='http://ctotodevelopers.blogspot.com/2011/03/agile-process-improvement-using-agile.html' title='Agile Process Improvement Using .... Agile!'/><author><name>Isaac Sacolick</name><uri>https://profiles.google.com/109747073147504760416</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='32' src='//lh4.googleusercontent.com/-pgtwy5F24tA/AAAAAAAAAAI/AAAAAAAAAAA/ZfSNeF9Egr8/s512-c/photo.jpg'/></author><thr:total>3</thr:total></entry><entry><id>tag:blogger.com,1999:blog-10332387.post-5928265501900118557</id><published>2011-02-09T17:45:00.001-05:00</published><updated>2011-02-09T17:46:35.890-05:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='project management'/><category scheme='http://www.blogger.com/atom/ns#' term='cio'/><category scheme='http://www.blogger.com/atom/ns#' term='offshore development'/><title type='text'>Top 10 Reasons to Visit Your Offshore Teams</title><summary type='text'>


Me at the Taj Mahal on a very cloudy day
I recently made a trip to India to visit our teams performing business operations, development, and support activities. It's a trip I like to do at least annually to get a sense of how teams are performing and where to make both improvements and investments.

Below are some of the areas I explore when visiting offshore teams: 
Learn the culture - Who </summary><link rel='replies' type='application/atom+xml' href='http://ctotodevelopers.blogspot.com/feeds/5928265501900118557/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://ctotodevelopers.blogspot.com/2011/02/top-10-reasons-to-visit-your-offshore.html#comment-form' title='1 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/10332387/posts/default/5928265501900118557'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/10332387/posts/default/5928265501900118557'/><link rel='alternate' type='text/html' href='http://ctotodevelopers.blogspot.com/2011/02/top-10-reasons-to-visit-your-offshore.html' title='Top 10 Reasons to Visit Your Offshore Teams'/><author><name>Isaac Sacolick</name><uri>https://profiles.google.com/109747073147504760416</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='32' src='//lh4.googleusercontent.com/-pgtwy5F24tA/AAAAAAAAAAI/AAAAAAAAAAA/ZfSNeF9Egr8/s512-c/photo.jpg'/></author><media:thumbnail xmlns:media='http://search.yahoo.com/mrss/' url='http://farm6.static.flickr.com/5085/5376126440_9521336613_t.jpg' height='72' width='72'/><thr:total>1</thr:total></entry><entry><id>tag:blogger.com,1999:blog-10332387.post-8937594769060161657</id><published>2011-01-03T17:44:00.000-05:00</published><updated>2011-01-03T17:44:30.639-05:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='product management'/><category scheme='http://www.blogger.com/atom/ns#' term='mobile'/><category scheme='http://www.blogger.com/atom/ns#' term='SaaS'/><category scheme='http://www.blogger.com/atom/ns#' term='enterprise 2.0'/><category scheme='http://www.blogger.com/atom/ns#' term='innovation'/><category scheme='http://www.blogger.com/atom/ns#' term='about me'/><category scheme='http://www.blogger.com/atom/ns#' term='it management'/><category scheme='http://www.blogger.com/atom/ns#' term='cio'/><category scheme='http://www.blogger.com/atom/ns#' term='cloud computing'/><title type='text'>A CIO New Year's Resolutions</title><summary type='text'>I'm certain many CIOs will relate to some of these resolutions... I'm also certain that this is an incomplete list. I'm not trying to cover a full CIO agenda or responsibilities, but am pointing out some areas that at least I will try to aspire to in 2011.

Not in any particular order....  

1) Blog and Tweet more - to better  contribute to your company, customers, colleagues, staff, and </summary><link rel='replies' type='application/atom+xml' href='http://ctotodevelopers.blogspot.com/feeds/8937594769060161657/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://ctotodevelopers.blogspot.com/2011/01/cio-new-years-resolutions.html#comment-form' title='1 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/10332387/posts/default/8937594769060161657'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/10332387/posts/default/8937594769060161657'/><link rel='alternate' type='text/html' href='http://ctotodevelopers.blogspot.com/2011/01/cio-new-years-resolutions.html' title='A CIO New Year&apos;s Resolutions'/><author><name>Isaac Sacolick</name><uri>https://profiles.google.com/109747073147504760416</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='32' src='//lh4.googleusercontent.com/-pgtwy5F24tA/AAAAAAAAAAI/AAAAAAAAAAA/ZfSNeF9Egr8/s512-c/photo.jpg'/></author><thr:total>1</thr:total></entry><entry><id>tag:blogger.com,1999:blog-10332387.post-8078145840443190017</id><published>2010-09-07T18:39:00.000-04:00</published><updated>2010-09-07T18:39:02.077-04:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='organizational change'/><category scheme='http://www.blogger.com/atom/ns#' term='about me'/><category scheme='http://www.blogger.com/atom/ns#' term='cio'/><title type='text'>100 Days as CIO; A Retrospective</title><summary type='text'>It's been a little over 100 days since I started my new CIO post. When I started back in May, I published My First 100 Days as CIO with reference links I used to help develop my plan. About 1/3 of the way through, I published a Top 10 Guidance Tips to New CIOs and IT Leaders with some simple advice to those in new IT leadership positions. I even tweeted through my first 100 days. Now, after a </summary><link rel='replies' type='application/atom+xml' href='http://ctotodevelopers.blogspot.com/feeds/8078145840443190017/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://ctotodevelopers.blogspot.com/2010/09/100-days-as-cio-retrospective.html#comment-form' title='6 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/10332387/posts/default/8078145840443190017'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/10332387/posts/default/8078145840443190017'/><link rel='alternate' type='text/html' href='http://ctotodevelopers.blogspot.com/2010/09/100-days-as-cio-retrospective.html' title='100 Days as CIO; A Retrospective'/><author><name>Isaac Sacolick</name><uri>https://profiles.google.com/109747073147504760416</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='32' src='//lh4.googleusercontent.com/-pgtwy5F24tA/AAAAAAAAAAI/AAAAAAAAAAA/ZfSNeF9Egr8/s512-c/photo.jpg'/></author><thr:total>6</thr:total></entry><entry><id>tag:blogger.com,1999:blog-10332387.post-6905602094519202430</id><published>2010-08-11T07:32:00.000-04:00</published><updated>2010-08-11T07:32:02.371-04:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='agile planning'/><category scheme='http://www.blogger.com/atom/ns#' term='project management'/><category scheme='http://www.blogger.com/atom/ns#' term='it management'/><category scheme='http://www.blogger.com/atom/ns#' term='cio'/><title type='text'>How To Get a Team to Think Agile</title><summary type='text'>I've seen this issue before; a team is struggling to move into an agile process. In my case, they are using agile to plan out an architecture. It's a smart team, but they are immediately jumping into solving problems and developing artifacts. The problem is, using agile process (scrum specifically) for planning, problem solving, developing a strategy, documenting an architecture requires some </summary><link rel='replies' type='application/atom+xml' href='http://ctotodevelopers.blogspot.com/feeds/6905602094519202430/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://ctotodevelopers.blogspot.com/2010/08/how-to-get-team-to-think-agile.html#comment-form' title='3 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/10332387/posts/default/6905602094519202430'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/10332387/posts/default/6905602094519202430'/><link rel='alternate' type='text/html' href='http://ctotodevelopers.blogspot.com/2010/08/how-to-get-team-to-think-agile.html' title='How To Get a Team to Think Agile'/><author><name>Isaac Sacolick</name><uri>https://profiles.google.com/109747073147504760416</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='32' src='//lh4.googleusercontent.com/-pgtwy5F24tA/AAAAAAAAAAI/AAAAAAAAAAA/ZfSNeF9Egr8/s512-c/photo.jpg'/></author><thr:total>3</thr:total></entry><entry><id>tag:blogger.com,1999:blog-10332387.post-430950108397611594</id><published>2010-07-13T18:48:00.000-04:00</published><updated>2010-07-13T18:48:33.948-04:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='organizational change'/><category scheme='http://www.blogger.com/atom/ns#' term='product management'/><category scheme='http://www.blogger.com/atom/ns#' term='agile software development'/><category scheme='http://www.blogger.com/atom/ns#' term='software development'/><category scheme='http://www.blogger.com/atom/ns#' term='project management'/><category scheme='http://www.blogger.com/atom/ns#' term='innovation'/><category scheme='http://www.blogger.com/atom/ns#' term='it management'/><category scheme='http://www.blogger.com/atom/ns#' term='cio'/><title type='text'>Getting from Software Projects and Maintenance to Agile Programs</title><summary type='text'>There is significant discussion in CIO circles on moving more IT spend out of the maintenance and into either enhancement work, new product development, innovation, or even R&amp;D. As I’ve explored this issue, there are a number of causes of high maintenance worth exploring:

1)    The product requires technologists to respond to customer issues, address service level deficiencies, investigate root </summary><link rel='replies' type='application/atom+xml' href='http://ctotodevelopers.blogspot.com/feeds/430950108397611594/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://ctotodevelopers.blogspot.com/2010/07/getting-from-software-projects-and.html#comment-form' title='3 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/10332387/posts/default/430950108397611594'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/10332387/posts/default/430950108397611594'/><link rel='alternate' type='text/html' href='http://ctotodevelopers.blogspot.com/2010/07/getting-from-software-projects-and.html' title='Getting from Software Projects and Maintenance to Agile Programs'/><author><name>Isaac Sacolick</name><uri>https://profiles.google.com/109747073147504760416</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='32' src='//lh4.googleusercontent.com/-pgtwy5F24tA/AAAAAAAAAAI/AAAAAAAAAAA/ZfSNeF9Egr8/s512-c/photo.jpg'/></author><thr:total>3</thr:total></entry><entry><id>tag:blogger.com,1999:blog-10332387.post-4228877343173797645</id><published>2010-06-21T07:12:00.000-04:00</published><updated>2010-06-21T07:12:44.634-04:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='about me'/><category scheme='http://www.blogger.com/atom/ns#' term='cio'/><title type='text'>Top 10 Guidance Tips to New CIOs and IT Leaders</title><summary type='text'>It's been awhile since my last post. What can I say, the first 100 days of being CIO at a new job is busy. There's people to meet, the business to learn, and the technology to understand. Some things need immediate attention, others are things that can be dealt with later. It's easy to be overwhelmed.

So, almost halfway into my 100 days, I can give new CIOs some advice. This goes beyond building</summary><link rel='replies' type='application/atom+xml' href='http://ctotodevelopers.blogspot.com/feeds/4228877343173797645/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://ctotodevelopers.blogspot.com/2010/06/top-10-guidance-tips-to-new-cios-and-it.html#comment-form' title='9 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/10332387/posts/default/4228877343173797645'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/10332387/posts/default/4228877343173797645'/><link rel='alternate' type='text/html' href='http://ctotodevelopers.blogspot.com/2010/06/top-10-guidance-tips-to-new-cios-and-it.html' title='Top 10 Guidance Tips to New CIOs and IT Leaders'/><author><name>Isaac Sacolick</name><uri>https://profiles.google.com/109747073147504760416</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='32' src='//lh4.googleusercontent.com/-pgtwy5F24tA/AAAAAAAAAAI/AAAAAAAAAAA/ZfSNeF9Egr8/s512-c/photo.jpg'/></author><thr:total>9</thr:total></entry><entry><id>tag:blogger.com,1999:blog-10332387.post-2257615845778825748</id><published>2010-05-14T00:12:00.000-04:00</published><updated>2010-05-14T00:12:01.359-04:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='about me'/><category scheme='http://www.blogger.com/atom/ns#' term='it management'/><category scheme='http://www.blogger.com/atom/ns#' term='cio'/><category scheme='http://www.blogger.com/atom/ns#' term='twitter'/><title type='text'>First 100 Days as CIO</title><summary type='text'>I started a new position this week as VP Technology / CIO of McGraw-Hill Construction and have started to work on a 100 day plan. Poking around a little bit, I've found a number of good references on this subject:
Forrester's new CIO 100 Day Plan - Advises building a personal checklist. Has a good starting list of major learning and action tasks. Recommends "let your business peers know you are </summary><link rel='replies' type='application/atom+xml' href='http://ctotodevelopers.blogspot.com/feeds/2257615845778825748/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://ctotodevelopers.blogspot.com/2010/05/first-100-days-as-cio.html#comment-form' title='12 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/10332387/posts/default/2257615845778825748'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/10332387/posts/default/2257615845778825748'/><link rel='alternate' type='text/html' href='http://ctotodevelopers.blogspot.com/2010/05/first-100-days-as-cio.html' title='First 100 Days as CIO'/><author><name>Isaac Sacolick</name><uri>https://profiles.google.com/109747073147504760416</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='32' src='//lh4.googleusercontent.com/-pgtwy5F24tA/AAAAAAAAAAI/AAAAAAAAAAA/ZfSNeF9Egr8/s512-c/photo.jpg'/></author><thr:total>12</thr:total></entry><entry><id>tag:blogger.com,1999:blog-10332387.post-4615951921240903143</id><published>2010-04-29T14:58:00.000-04:00</published><updated>2010-04-29T14:58:28.141-04:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='web 2.0'/><category scheme='http://www.blogger.com/atom/ns#' term='social media'/><category scheme='http://www.blogger.com/atom/ns#' term='enterprise 2.0'/><category scheme='http://www.blogger.com/atom/ns#' term='cio'/><category scheme='http://www.blogger.com/atom/ns#' term='twitter'/><title type='text'>Top CIOs talk Social Networking Usage and Policy</title><summary type='text'>Last week I moderated a panel on Social Networking and Media to a group of approximately 50 CIOs at the Global CIO Forum sponsored by Telwares. We covered social networking from a number of perspectives:
Integrating social networking functionality into products (example, Twitter, LinkedIn like Business Exchange has done or Facebook integration as others have done successfullt)
Social media/</summary><link rel='replies' type='application/atom+xml' href='http://ctotodevelopers.blogspot.com/feeds/4615951921240903143/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://ctotodevelopers.blogspot.com/2010/04/top-cios-talk-social-networking-usage.html#comment-form' title='2 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/10332387/posts/default/4615951921240903143'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/10332387/posts/default/4615951921240903143'/><link rel='alternate' type='text/html' href='http://ctotodevelopers.blogspot.com/2010/04/top-cios-talk-social-networking-usage.html' title='Top CIOs talk Social Networking Usage and Policy'/><author><name>Isaac Sacolick</name><uri>https://profiles.google.com/109747073147504760416</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='32' src='//lh4.googleusercontent.com/-pgtwy5F24tA/AAAAAAAAAAI/AAAAAAAAAAA/ZfSNeF9Egr8/s512-c/photo.jpg'/></author><thr:total>2</thr:total></entry><entry><id>tag:blogger.com,1999:blog-10332387.post-8665420209186495445</id><published>2010-04-05T22:03:00.000-04:00</published><updated>2010-04-05T22:03:06.770-04:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='project management'/><category scheme='http://www.blogger.com/atom/ns#' term='enterprise 2.0'/><category scheme='http://www.blogger.com/atom/ns#' term='it management'/><category scheme='http://www.blogger.com/atom/ns#' term='cio'/><category scheme='http://www.blogger.com/atom/ns#' term='startup cto'/><title type='text'>In my CIO Toolkit: Quickbase</title><summary type='text'>One of the things I look for when introducing new tools and processes is what I term "easy on-ramps". Basically, that means that a small group of "believers" (to steal a term from McAfee's Enterprise 2.0 book) can start leveraging the tool quickly and easily. It also means that as the Believers benefit from the tool and build up its use cases, these same on-ramps make it just as easy for the next</summary><link rel='replies' type='application/atom+xml' href='http://ctotodevelopers.blogspot.com/feeds/8665420209186495445/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://ctotodevelopers.blogspot.com/2010/04/in-my-cio-toolkit-quickbase.html#comment-form' title='3 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/10332387/posts/default/8665420209186495445'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/10332387/posts/default/8665420209186495445'/><link rel='alternate' type='text/html' href='http://ctotodevelopers.blogspot.com/2010/04/in-my-cio-toolkit-quickbase.html' title='In my CIO Toolkit: Quickbase'/><author><name>Isaac Sacolick</name><uri>https://profiles.google.com/109747073147504760416</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='32' src='//lh4.googleusercontent.com/-pgtwy5F24tA/AAAAAAAAAAI/AAAAAAAAAAA/ZfSNeF9Egr8/s512-c/photo.jpg'/></author><thr:total>3</thr:total></entry><entry><id>tag:blogger.com,1999:blog-10332387.post-4491085993340272884</id><published>2010-03-09T18:44:00.000-05:00</published><updated>2010-03-09T18:44:17.670-05:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='product management'/><category scheme='http://www.blogger.com/atom/ns#' term='agile software development'/><category scheme='http://www.blogger.com/atom/ns#' term='project management'/><category scheme='http://www.blogger.com/atom/ns#' term='cio'/><title type='text'>Building Business - IT Relationship: Agile Iteration #1</title><summary type='text'>Have you heard this one yet, "We're not ready to talk to Technology yet, we're still in strategic planning on the product and priorities. We'll talk soon when we have requirements ready".

Ba humbug. Here's my answer to this issue. The key Business / IT engagement question is:

What are some of the biggest issues or opportunities that need to be addressed for some of your core customers in the </summary><link rel='replies' type='application/atom+xml' href='http://ctotodevelopers.blogspot.com/feeds/4491085993340272884/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://ctotodevelopers.blogspot.com/2010/03/building-business-it-relationship-agile.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/10332387/posts/default/4491085993340272884'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/10332387/posts/default/4491085993340272884'/><link rel='alternate' type='text/html' href='http://ctotodevelopers.blogspot.com/2010/03/building-business-it-relationship-agile.html' title='Building Business - IT Relationship: Agile Iteration #1'/><author><name>Isaac Sacolick</name><uri>https://profiles.google.com/109747073147504760416</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='32' src='//lh4.googleusercontent.com/-pgtwy5F24tA/AAAAAAAAAAI/AAAAAAAAAAA/ZfSNeF9Egr8/s512-c/photo.jpg'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-10332387.post-3958652993341689400</id><published>2010-02-24T08:57:00.000-05:00</published><updated>2010-02-24T08:57:41.212-05:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='organizational change'/><category scheme='http://www.blogger.com/atom/ns#' term='product management'/><category scheme='http://www.blogger.com/atom/ns#' term='agile software development'/><category scheme='http://www.blogger.com/atom/ns#' term='project management'/><category scheme='http://www.blogger.com/atom/ns#' term='innovation'/><category scheme='http://www.blogger.com/atom/ns#' term='it management'/><category scheme='http://www.blogger.com/atom/ns#' term='cio'/><category scheme='http://www.blogger.com/atom/ns#' term='business exchange'/><title type='text'>Criteria for a First Agile Project</title><summary type='text'>I like to say that the best time to adopt agile in a large company or an enterprise is when there are the right business conditions. This may seem odd for a software development process, but while the development team has a lot to master when it comes to agile, it's the business functions that exhibit the most changes and must also put a lot of trust in their technology colleagues.

I speak this </summary><link rel='replies' type='application/atom+xml' href='http://ctotodevelopers.blogspot.com/feeds/3958652993341689400/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://ctotodevelopers.blogspot.com/2010/02/criteria-for-first-agile-project.html#comment-form' title='2 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/10332387/posts/default/3958652993341689400'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/10332387/posts/default/3958652993341689400'/><link rel='alternate' type='text/html' href='http://ctotodevelopers.blogspot.com/2010/02/criteria-for-first-agile-project.html' title='Criteria for a First Agile Project'/><author><name>Isaac Sacolick</name><uri>https://profiles.google.com/109747073147504760416</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='32' src='//lh4.googleusercontent.com/-pgtwy5F24tA/AAAAAAAAAAI/AAAAAAAAAAA/ZfSNeF9Egr8/s512-c/photo.jpg'/></author><thr:total>2</thr:total></entry><entry><id>tag:blogger.com,1999:blog-10332387.post-8948833751193440445</id><published>2010-02-16T08:54:00.000-05:00</published><updated>2010-02-16T08:54:46.054-05:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='organizational change'/><category scheme='http://www.blogger.com/atom/ns#' term='product management'/><category scheme='http://www.blogger.com/atom/ns#' term='agile software development'/><category scheme='http://www.blogger.com/atom/ns#' term='software development'/><category scheme='http://www.blogger.com/atom/ns#' term='project management'/><category scheme='http://www.blogger.com/atom/ns#' term='it management'/><category scheme='http://www.blogger.com/atom/ns#' term='cio'/><title type='text'>Four Phases of Maturing Enterprise Agile Development</title><summary type='text'>Are you a technology executive looking to adopt or migrate to an agile software development practice? According to a Forrester survey Mainstream Adoption Has Changed Agility, 35% of IT professionals say their development practice most closely resembles an agile development practice causing the media proclamation that agile is now mainstream. But of course this also means that 65% are not </summary><link rel='replies' type='application/atom+xml' href='http://ctotodevelopers.blogspot.com/feeds/8948833751193440445/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://ctotodevelopers.blogspot.com/2010/02/four-phases-of-maturing-enterprise.html#comment-form' title='1 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/10332387/posts/default/8948833751193440445'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/10332387/posts/default/8948833751193440445'/><link rel='alternate' type='text/html' href='http://ctotodevelopers.blogspot.com/2010/02/four-phases-of-maturing-enterprise.html' title='Four Phases of Maturing Enterprise Agile Development'/><author><name>Isaac Sacolick</name><uri>https://profiles.google.com/109747073147504760416</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='32' src='//lh4.googleusercontent.com/-pgtwy5F24tA/AAAAAAAAAAI/AAAAAAAAAAA/ZfSNeF9Egr8/s512-c/photo.jpg'/></author><thr:total>1</thr:total></entry><entry><id>tag:blogger.com,1999:blog-10332387.post-6181537786392187217</id><published>2010-02-01T09:10:00.001-05:00</published><updated>2010-02-01T09:19:24.543-05:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='organizational change'/><category scheme='http://www.blogger.com/atom/ns#' term='product management'/><category scheme='http://www.blogger.com/atom/ns#' term='agile software development'/><category scheme='http://www.blogger.com/atom/ns#' term='software development'/><category scheme='http://www.blogger.com/atom/ns#' term='project management'/><category scheme='http://www.blogger.com/atom/ns#' term='innovation'/><category scheme='http://www.blogger.com/atom/ns#' term='cio'/><title type='text'>Adopting Agile Development  - The role of the CIO</title><summary type='text'>I've been covering the CIO path to credibility. First, the CIO must be able to negotiate priorities and develop a path for consistent delivery - which is why I thing the CIO loves Agile (or should love it). So if you are buying into my methodology, the next step the CIO must determine is how to introduce an agile development life cycle to both the Technology and the Business organizations.

Now </summary><link rel='replies' type='application/atom+xml' href='http://ctotodevelopers.blogspot.com/feeds/6181537786392187217/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://ctotodevelopers.blogspot.com/2010/02/adopting-agile-development-role-of-cio.html#comment-form' title='1 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/10332387/posts/default/6181537786392187217'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/10332387/posts/default/6181537786392187217'/><link rel='alternate' type='text/html' href='http://ctotodevelopers.blogspot.com/2010/02/adopting-agile-development-role-of-cio.html' title='Adopting Agile Development  - The role of the CIO'/><author><name>Isaac Sacolick</name><uri>https://profiles.google.com/109747073147504760416</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='32' src='//lh4.googleusercontent.com/-pgtwy5F24tA/AAAAAAAAAAI/AAAAAAAAAAA/ZfSNeF9Egr8/s512-c/photo.jpg'/></author><thr:total>1</thr:total></entry><entry><id>tag:blogger.com,1999:blog-10332387.post-6354201927271281651</id><published>2010-01-28T08:30:00.001-05:00</published><updated>2010-01-28T08:39:24.989-05:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='web development'/><category scheme='http://www.blogger.com/atom/ns#' term='mobile'/><category scheme='http://www.blogger.com/atom/ns#' term='innovation'/><category scheme='http://www.blogger.com/atom/ns#' term='in the news'/><category scheme='http://www.blogger.com/atom/ns#' term='about me'/><category scheme='http://www.blogger.com/atom/ns#' term='media and publishing'/><title type='text'>How the iPad could be a Game Changer</title><summary type='text'>Doing some poking around today and this evening on the iPad, and the vibe I'm getting is ho-hum. Gadget enthusiasts are somewhat disappointed on the lack of some features (sd card, camera) but investors are enthused over the $499 entry price. Obviously the Apple designers had to make some tough calls on what hardware features they had to include given constraints on cost, physical size, and </summary><link rel='replies' type='application/atom+xml' href='http://ctotodevelopers.blogspot.com/feeds/6354201927271281651/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://ctotodevelopers.blogspot.com/2010/01/how-ipad-could-be-game-changer.html#comment-form' title='3 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/10332387/posts/default/6354201927271281651'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/10332387/posts/default/6354201927271281651'/><link rel='alternate' type='text/html' href='http://ctotodevelopers.blogspot.com/2010/01/how-ipad-could-be-game-changer.html' title='How the iPad could be a Game Changer'/><author><name>Isaac Sacolick</name><uri>https://profiles.google.com/109747073147504760416</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='32' src='//lh4.googleusercontent.com/-pgtwy5F24tA/AAAAAAAAAAI/AAAAAAAAAAA/ZfSNeF9Egr8/s512-c/photo.jpg'/></author><thr:total>3</thr:total></entry><entry><id>tag:blogger.com,1999:blog-10332387.post-3434506365441170882</id><published>2010-01-25T08:36:00.001-05:00</published><updated>2010-01-25T08:42:15.942-05:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='agile software development'/><category scheme='http://www.blogger.com/atom/ns#' term='innovation'/><category scheme='http://www.blogger.com/atom/ns#' term='it management'/><category scheme='http://www.blogger.com/atom/ns#' term='cio'/><title type='text'>Why the CIO Loves Agile Development</title><summary type='text'>Let's say you're following my last two posts on negotiating business priorities. You're the CIO and have just been given a set of business priorities and now need to get your IT team aligned and executing. Let's play out a couple of scenarios:

You go back to the sponsors, assign a business analyst and work on requirements and a project plan. Once requirements are largely stable, you then look at</summary><link rel='replies' type='application/atom+xml' href='http://ctotodevelopers.blogspot.com/feeds/3434506365441170882/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://ctotodevelopers.blogspot.com/2010/01/why-cio-loves-agile-development.html#comment-form' title='1 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/10332387/posts/default/3434506365441170882'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/10332387/posts/default/3434506365441170882'/><link rel='alternate' type='text/html' href='http://ctotodevelopers.blogspot.com/2010/01/why-cio-loves-agile-development.html' title='Why the CIO Loves Agile Development'/><author><name>Isaac Sacolick</name><uri>https://profiles.google.com/109747073147504760416</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='32' src='//lh4.googleusercontent.com/-pgtwy5F24tA/AAAAAAAAAAI/AAAAAAAAAAA/ZfSNeF9Egr8/s512-c/photo.jpg'/></author><thr:total>1</thr:total></entry><entry><id>tag:blogger.com,1999:blog-10332387.post-6323649105293434639</id><published>2010-01-04T09:30:00.002-05:00</published><updated>2010-01-04T09:32:32.776-05:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='product management'/><category scheme='http://www.blogger.com/atom/ns#' term='business plans'/><category scheme='http://www.blogger.com/atom/ns#' term='it management'/><category scheme='http://www.blogger.com/atom/ns#' term='cio'/><title type='text'>Why CIOs Must Negotiate before Collaboration</title><summary type='text'>Several CIOs questioned my last post and why The Most Important Job of the CIO is to Negotiate with the Business  and not collaboration or partnership?  So before I get into how CIOs can establish credibility, let me elaborate a bit on my last post. My rationale on negotiation before collaboration is quite simple:
Before you can collaborate and have a true partnership between Business and </summary><link rel='replies' type='application/atom+xml' href='http://ctotodevelopers.blogspot.com/feeds/6323649105293434639/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://ctotodevelopers.blogspot.com/2010/01/why-cios-must-negotiate-before.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/10332387/posts/default/6323649105293434639'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/10332387/posts/default/6323649105293434639'/><link rel='alternate' type='text/html' href='http://ctotodevelopers.blogspot.com/2010/01/why-cios-must-negotiate-before.html' title='Why CIOs Must Negotiate before Collaboration'/><author><name>Isaac Sacolick</name><uri>https://profiles.google.com/109747073147504760416</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='32' src='//lh4.googleusercontent.com/-pgtwy5F24tA/AAAAAAAAAAI/AAAAAAAAAAA/ZfSNeF9Egr8/s512-c/photo.jpg'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-10332387.post-2088298387730149342</id><published>2009-12-22T07:10:00.001-05:00</published><updated>2009-12-22T07:21:51.165-05:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='product management'/><category scheme='http://www.blogger.com/atom/ns#' term='innovation'/><category scheme='http://www.blogger.com/atom/ns#' term='it management'/><category scheme='http://www.blogger.com/atom/ns#' term='cio'/><title type='text'>The Most Important Job of the CIO</title><summary type='text'>I was having a discussion today with a colleague about the role of a business unit CIO and told him quite definitively:The Most Important Job of the CIO is to Negotiate with the Businessand to be successful, the CIO should aim to spend 50-75% of his or her time working directly with the Business at all levels of the organization.My rationale is quite simple. I've never been in a business that has</summary><link rel='replies' type='application/atom+xml' href='http://ctotodevelopers.blogspot.com/feeds/2088298387730149342/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://ctotodevelopers.blogspot.com/2009/12/most-important-job-of-cio-is-to.html#comment-form' title='6 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/10332387/posts/default/2088298387730149342'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/10332387/posts/default/2088298387730149342'/><link rel='alternate' type='text/html' href='http://ctotodevelopers.blogspot.com/2009/12/most-important-job-of-cio-is-to.html' title='The Most Important Job of the CIO'/><author><name>Isaac Sacolick</name><uri>https://profiles.google.com/109747073147504760416</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='32' src='//lh4.googleusercontent.com/-pgtwy5F24tA/AAAAAAAAAAI/AAAAAAAAAAA/ZfSNeF9Egr8/s512-c/photo.jpg'/></author><thr:total>6</thr:total></entry><entry><id>tag:blogger.com,1999:blog-10332387.post-584672723690152876</id><published>2009-12-08T08:45:00.000-05:00</published><updated>2009-12-08T11:19:27.343-05:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='organizational change'/><category scheme='http://www.blogger.com/atom/ns#' term='agile software development'/><category scheme='http://www.blogger.com/atom/ns#' term='innovation'/><category scheme='http://www.blogger.com/atom/ns#' term='it management'/><category scheme='http://www.blogger.com/atom/ns#' term='cio'/><title type='text'>What is Really Meant by Failing Early, Failing Often, and Failing Cheap?</title><summary type='text'>li {margin: .8em 0}What do we mean about failing early, failing fast, failing often, or failing cheap? Why is "failing" a good, positive outcome for some features, agile projects or agile delivery? Why is it needed for innovation?Failure was once an absolute outcome. You either succeeded or failed in your business, your project or your investment. Once something was marked as a failure, it was </summary><link rel='replies' type='application/atom+xml' href='http://ctotodevelopers.blogspot.com/feeds/584672723690152876/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://ctotodevelopers.blogspot.com/2009/12/what-is-really-meant-by-failing-early.html#comment-form' title='5 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/10332387/posts/default/584672723690152876'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/10332387/posts/default/584672723690152876'/><link rel='alternate' type='text/html' href='http://ctotodevelopers.blogspot.com/2009/12/what-is-really-meant-by-failing-early.html' title='What is Really Meant by Failing Early, Failing Often, and Failing Cheap?'/><author><name>Isaac Sacolick</name><uri>https://profiles.google.com/109747073147504760416</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='32' src='//lh4.googleusercontent.com/-pgtwy5F24tA/AAAAAAAAAAI/AAAAAAAAAAA/ZfSNeF9Egr8/s512-c/photo.jpg'/></author><thr:total>5</thr:total></entry><entry><id>tag:blogger.com,1999:blog-10332387.post-6716250534257267685</id><published>2009-12-03T08:00:00.000-05:00</published><updated>2009-12-03T09:04:46.292-05:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='in the news'/><category scheme='http://www.blogger.com/atom/ns#' term='media and publishing'/><title type='text'>What Could Save Media Businesses</title><summary type='text'>li {margin: .8em 0}So what will save the media industry? John Byrne's assessment of the issues are dead on1) Print advertising will never come back. There are just too many options for advertisers today and too much pressure on rates. Sadly, success in print will be measured in single-digit declines, forever. 2) Online advertising will never offset those declines nor save print. There’s far too </summary><link rel='replies' type='application/atom+xml' href='http://ctotodevelopers.blogspot.com/feeds/6716250534257267685/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://ctotodevelopers.blogspot.com/2009/12/what-could-save-media-businesses.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/10332387/posts/default/6716250534257267685'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/10332387/posts/default/6716250534257267685'/><link rel='alternate' type='text/html' href='http://ctotodevelopers.blogspot.com/2009/12/what-could-save-media-businesses.html' title='What Could Save Media Businesses'/><author><name>Isaac Sacolick</name><uri>https://profiles.google.com/109747073147504760416</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='32' src='//lh4.googleusercontent.com/-pgtwy5F24tA/AAAAAAAAAAI/AAAAAAAAAAA/ZfSNeF9Egr8/s512-c/photo.jpg'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-10332387.post-5778205083323765790</id><published>2009-11-30T23:15:00.002-05:00</published><updated>2009-12-01T11:52:37.761-05:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='web 2.0'/><category scheme='http://www.blogger.com/atom/ns#' term='agile software development'/><category scheme='http://www.blogger.com/atom/ns#' term='in the news'/><category scheme='http://www.blogger.com/atom/ns#' term='about me'/><category scheme='http://www.blogger.com/atom/ns#' term='media and publishing'/><category scheme='http://www.blogger.com/atom/ns#' term='business exchange'/><title type='text'>My Time Leading Tech at BusinessWeek</title><summary type='text'>Today was my last full day heading technology at BusinessWeek (or CIO as my superiors acknowledge).I’m very proud of the BusinessWeek Technology Team’s accomplishments during my tenure. Some of our product accomplishments have been very public. We launched, Business Exchange, a social platform for business professionals. If you haven’t checked out this platform then I encourage you to spend some </summary><link rel='replies' type='application/atom+xml' href='http://ctotodevelopers.blogspot.com/feeds/5778205083323765790/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://ctotodevelopers.blogspot.com/2009/11/my-time-leading-tech-at-businessweek.html#comment-form' title='1 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/10332387/posts/default/5778205083323765790'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/10332387/posts/default/5778205083323765790'/><link rel='alternate' type='text/html' href='http://ctotodevelopers.blogspot.com/2009/11/my-time-leading-tech-at-businessweek.html' title='My Time Leading Tech at BusinessWeek'/><author><name>Isaac Sacolick</name><uri>https://profiles.google.com/109747073147504760416</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='32' src='//lh4.googleusercontent.com/-pgtwy5F24tA/AAAAAAAAAAI/AAAAAAAAAAA/ZfSNeF9Egr8/s512-c/photo.jpg'/></author><media:thumbnail xmlns:media='http://search.yahoo.com/mrss/' url='http://2.bp.blogspot.com/_y1jpflueSAA/SxVJacphtyI/AAAAAAAAACw/Elx5e25RSY0/s72-c/BWDevTeam1.JPG' height='72' width='72'/><thr:total>1</thr:total></entry><entry><id>tag:blogger.com,1999:blog-10332387.post-7190110051934606372</id><published>2009-11-17T08:30:00.000-05:00</published><updated>2009-11-17T09:05:12.858-05:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='enterprise 2.0'/><category scheme='http://www.blogger.com/atom/ns#' term='innovation'/><category scheme='http://www.blogger.com/atom/ns#' term='cio'/><title type='text'>Turning Good Ideas into Operational Reality</title><summary type='text'>li {margin: .8em 0}Lots of companies these days are focused on innovation and idea generation. In fact, one of the major reasons CIOs are backing Enterprise 2.0 is to provide tools to the entire distributed organization for idea capture, collaboration, and ranking. Here are some of my tips on fostering "useful" idea generation so that the organization can implement the best ideas:Communicate the </summary><link rel='replies' type='application/atom+xml' href='http://ctotodevelopers.blogspot.com/feeds/7190110051934606372/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://ctotodevelopers.blogspot.com/2009/11/turning-good-ideas-into-operational.html#comment-form' title='2 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/10332387/posts/default/7190110051934606372'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/10332387/posts/default/7190110051934606372'/><link rel='alternate' type='text/html' href='http://ctotodevelopers.blogspot.com/2009/11/turning-good-ideas-into-operational.html' title='Turning Good Ideas into Operational Reality'/><author><name>Isaac Sacolick</name><uri>https://profiles.google.com/109747073147504760416</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='32' src='//lh4.googleusercontent.com/-pgtwy5F24tA/AAAAAAAAAAI/AAAAAAAAAAA/ZfSNeF9Egr8/s512-c/photo.jpg'/></author><thr:total>2</thr:total></entry><entry><id>tag:blogger.com,1999:blog-10332387.post-8882140943586740851</id><published>2009-11-03T08:07:00.001-05:00</published><updated>2009-11-03T15:01:22.189-05:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='web development'/><category scheme='http://www.blogger.com/atom/ns#' term='agile software development'/><category scheme='http://www.blogger.com/atom/ns#' term='software development'/><category scheme='http://www.blogger.com/atom/ns#' term='project management'/><title type='text'>No Scrum Master? No Problem</title><summary type='text'>How should Enterprises fill the Scrum Master Role?I field this question very often and especially from members of technology organizations where agile and scrum in particular is being introduced top down from Management. I've blogged a bit on Product Owners in the Enterprise and Why Project Managers are still needed, but what about Scrum Masters?Some ThoughtsHere's how this question surfaced over</summary><link rel='replies' type='application/atom+xml' href='http://ctotodevelopers.blogspot.com/feeds/8882140943586740851/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://ctotodevelopers.blogspot.com/2009/11/no-scrum-master-no-problem.html#comment-form' title='5 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/10332387/posts/default/8882140943586740851'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/10332387/posts/default/8882140943586740851'/><link rel='alternate' type='text/html' href='http://ctotodevelopers.blogspot.com/2009/11/no-scrum-master-no-problem.html' title='No Scrum Master? No Problem'/><author><name>Isaac Sacolick</name><uri>https://profiles.google.com/109747073147504760416</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='32' src='//lh4.googleusercontent.com/-pgtwy5F24tA/AAAAAAAAAAI/AAAAAAAAAAA/ZfSNeF9Egr8/s512-c/photo.jpg'/></author><thr:total>5</thr:total></entry><entry><id>tag:blogger.com,1999:blog-10332387.post-8360661116555823012</id><published>2009-10-27T08:30:00.000-04:00</published><updated>2009-12-08T00:03:55.276-05:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='organizational change'/><category scheme='http://www.blogger.com/atom/ns#' term='product management'/><category scheme='http://www.blogger.com/atom/ns#' term='software development'/><category scheme='http://www.blogger.com/atom/ns#' term='project management'/><category scheme='http://www.blogger.com/atom/ns#' term='innovation'/><title type='text'>When Organizational Silos Hurt Innovation</title><summary type='text'>What's wrong with these two pictures?a) A product manager is working on the latest strategic initiative. She's researching competition, finding opportunities in the marketplace, considering price points, sizing up the revenue potential and evaluating vendors. She may even narrow down the list of vendors to an optimal one or two, and if she's really dangerous, will determine exactly what's needed </summary><link rel='replies' type='application/atom+xml' href='http://ctotodevelopers.blogspot.com/feeds/8360661116555823012/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://ctotodevelopers.blogspot.com/2009/10/when-organizational-silos-hurt.html#comment-form' title='4 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/10332387/posts/default/8360661116555823012'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/10332387/posts/default/8360661116555823012'/><link rel='alternate' type='text/html' href='http://ctotodevelopers.blogspot.com/2009/10/when-organizational-silos-hurt.html' title='When Organizational Silos Hurt Innovation'/><author><name>Isaac Sacolick</name><uri>https://profiles.google.com/109747073147504760416</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='32' src='//lh4.googleusercontent.com/-pgtwy5F24tA/AAAAAAAAAAI/AAAAAAAAAAA/ZfSNeF9Egr8/s512-c/photo.jpg'/></author><thr:total>4</thr:total></entry><entry><id>tag:blogger.com,1999:blog-10332387.post-532960427806082847</id><published>2009-10-16T09:50:00.006-04:00</published><updated>2009-10-16T12:38:14.566-04:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='web 2.0'/><category scheme='http://www.blogger.com/atom/ns#' term='innovation'/><category scheme='http://www.blogger.com/atom/ns#' term='in the news'/><category scheme='http://www.blogger.com/atom/ns#' term='business exchange'/><title type='text'>Bloomberg Buys BusinessWeek - and its Innovative Digital Team</title><summary type='text'>There have been  many articles this week on Bloomberg's acquisition of BusinessWeek. Linked below are a couple of my favorite quotes; a small testament to an innovative digital team that has launched a unique social media product Business Exchange and has completed several forward thinking upgrades to BusinessWeek.comWill BusinessWeek bring social media to Bloomberg?That's because BusinessWeek, </summary><link rel='replies' type='application/atom+xml' href='http://ctotodevelopers.blogspot.com/feeds/532960427806082847/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://ctotodevelopers.blogspot.com/2009/10/bloomberg-buys-businessweek-and-its.html#comment-form' title='1 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/10332387/posts/default/532960427806082847'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/10332387/posts/default/532960427806082847'/><link rel='alternate' type='text/html' href='http://ctotodevelopers.blogspot.com/2009/10/bloomberg-buys-businessweek-and-its.html' title='Bloomberg Buys BusinessWeek - and its Innovative Digital Team'/><author><name>Isaac Sacolick</name><uri>https://profiles.google.com/109747073147504760416</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='32' src='//lh4.googleusercontent.com/-pgtwy5F24tA/AAAAAAAAAAI/AAAAAAAAAAA/ZfSNeF9Egr8/s512-c/photo.jpg'/></author><thr:total>1</thr:total></entry><entry><id>tag:blogger.com,1999:blog-10332387.post-9163469715945738149</id><published>2009-10-12T09:02:00.001-04:00</published><updated>2009-10-16T08:56:52.323-04:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='agile software development'/><category scheme='http://www.blogger.com/atom/ns#' term='innovation'/><category scheme='http://www.blogger.com/atom/ns#' term='it management'/><title type='text'>Collaboration between Business and IT Leads to Innovation</title><summary type='text'>I wanted to follow up my post on the Top 5 Reasons Why Agile Development Spurs Innovation with a little more detail.We used to think of product development as one fundamental question; Build vs. Buy. Once a product was conceptualized, a search was conducted to find the most suitable software solutions and a feature point analysis was completed. An engineering team was only brought in to evaluate </summary><link rel='replies' type='application/atom+xml' href='http://ctotodevelopers.blogspot.com/feeds/9163469715945738149/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://ctotodevelopers.blogspot.com/2009/10/collaboration-between-business-and-it.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/10332387/posts/default/9163469715945738149'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/10332387/posts/default/9163469715945738149'/><link rel='alternate' type='text/html' href='http://ctotodevelopers.blogspot.com/2009/10/collaboration-between-business-and-it.html' title='Collaboration between Business and IT Leads to Innovation'/><author><name>Isaac Sacolick</name><uri>https://profiles.google.com/109747073147504760416</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='32' src='//lh4.googleusercontent.com/-pgtwy5F24tA/AAAAAAAAAAI/AAAAAAAAAAA/ZfSNeF9Egr8/s512-c/photo.jpg'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-10332387.post-8000422329992471918</id><published>2009-10-08T12:19:00.002-04:00</published><updated>2009-10-08T12:20:34.710-04:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='site performance'/><category scheme='http://www.blogger.com/atom/ns#' term='social media'/><category scheme='http://www.blogger.com/atom/ns#' term='in the news'/><category scheme='http://www.blogger.com/atom/ns#' term='twitter'/><title type='text'>Twitter outage - and Why Consistent Performance on Social Networks is Hard</title><summary type='text'>Keeping social networks up and running is no easy task. Today's casualty, Twitter is down again. I suspect that their engineers are in the "war room" thinking about what the root cause is and resolving it quickly. Perhaps it's another denial of service (DoS) attack.Why are performance issues hard on social networking sites? A few reasons:Content sites are easy to cache. Social networks have </summary><link rel='replies' type='application/atom+xml' href='http://ctotodevelopers.blogspot.com/feeds/8000422329992471918/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://ctotodevelopers.blogspot.com/2009/10/twitter-outage-and-why-consistent.html#comment-form' title='1 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/10332387/posts/default/8000422329992471918'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/10332387/posts/default/8000422329992471918'/><link rel='alternate' type='text/html' href='http://ctotodevelopers.blogspot.com/2009/10/twitter-outage-and-why-consistent.html' title='Twitter outage - and Why Consistent Performance on Social Networks is Hard'/><author><name>Isaac Sacolick</name><uri>https://profiles.google.com/109747073147504760416</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='32' src='//lh4.googleusercontent.com/-pgtwy5F24tA/AAAAAAAAAAI/AAAAAAAAAAA/ZfSNeF9Egr8/s512-c/photo.jpg'/></author><thr:total>1</thr:total></entry><entry><id>tag:blogger.com,1999:blog-10332387.post-5974724820164317830</id><published>2009-10-06T09:05:00.000-04:00</published><updated>2009-10-06T09:06:02.877-04:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='web development'/><category scheme='http://www.blogger.com/atom/ns#' term='software development'/><category scheme='http://www.blogger.com/atom/ns#' term='cloud computing'/><title type='text'>Ten Reasons Software Developers Need the Cloud</title><summary type='text'>Developers need cloud development environments? Why? Bottom line, developers need more than one development environment, and they need cost effective, agile ways to manage their development environments. Consider the following cases:You branch your source code and need multiple environments to validate changesYou are in the middle of testing a software upgrade, configuration change, or </summary><link rel='replies' type='application/atom+xml' href='http://ctotodevelopers.blogspot.com/feeds/5974724820164317830/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://ctotodevelopers.blogspot.com/2009/10/ten-reasons-software-developers-need.html#comment-form' title='1 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/10332387/posts/default/5974724820164317830'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/10332387/posts/default/5974724820164317830'/><link rel='alternate' type='text/html' href='http://ctotodevelopers.blogspot.com/2009/10/ten-reasons-software-developers-need.html' title='Ten Reasons Software Developers Need the Cloud'/><author><name>Isaac Sacolick</name><uri>https://profiles.google.com/109747073147504760416</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='32' src='//lh4.googleusercontent.com/-pgtwy5F24tA/AAAAAAAAAAI/AAAAAAAAAAA/ZfSNeF9Egr8/s512-c/photo.jpg'/></author><thr:total>1</thr:total></entry><entry><id>tag:blogger.com,1999:blog-10332387.post-3549996765352196583</id><published>2009-09-29T09:10:00.000-04:00</published><updated>2009-09-29T09:10:42.936-04:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='web 2.0'/><category scheme='http://www.blogger.com/atom/ns#' term='enterprise 2.0'/><category scheme='http://www.blogger.com/atom/ns#' term='innovation'/><category scheme='http://www.blogger.com/atom/ns#' term='it management'/><category scheme='http://www.blogger.com/atom/ns#' term='cio'/><category scheme='http://www.blogger.com/atom/ns#' term='twitter'/><category scheme='http://www.blogger.com/atom/ns#' term='business exchange'/><title type='text'>Why CIOs need to put Enterprise 2.0 high on their agenda</title><summary type='text'>Last week, I was able to attend two IT executive conferences - the TCS Summit and Telwares Global CIO Forum. At both shows, I was given the opportunity to present my views on innovation, agile development, and enterprise 2.0 and also highlight BusinessWeek's social media product for business professionals, Business Exchange.Here are some of my notes on what CIOs are saying and doing in Enterprise</summary><link rel='replies' type='application/atom+xml' href='http://ctotodevelopers.blogspot.com/feeds/3549996765352196583/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://ctotodevelopers.blogspot.com/2009/09/why-cios-need-to-put-enterprise-20-high.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/10332387/posts/default/3549996765352196583'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/10332387/posts/default/3549996765352196583'/><link rel='alternate' type='text/html' href='http://ctotodevelopers.blogspot.com/2009/09/why-cios-need-to-put-enterprise-20-high.html' title='Why CIOs need to put Enterprise 2.0 high on their agenda'/><author><name>Isaac Sacolick</name><uri>https://profiles.google.com/109747073147504760416</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='32' src='//lh4.googleusercontent.com/-pgtwy5F24tA/AAAAAAAAAAI/AAAAAAAAAAA/ZfSNeF9Egr8/s512-c/photo.jpg'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-10332387.post-8768166093058589915</id><published>2009-08-24T22:36:00.004-04:00</published><updated>2009-08-24T23:07:32.574-04:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='innovation'/><category scheme='http://www.blogger.com/atom/ns#' term='about me'/><title type='text'>What if we all went ECommerce Only?</title><summary type='text'>After yet another bad experience at a bricks and mortar this weekend, I pondered - what would life be like if the percentages were reverse and we did the majority of our purchases online instead of the store?If you asked that question even a year ago, there would be plenty of naysayers listing every item that's difficult to purchase without seeing the real product. Shoes, perishable items, high </summary><link rel='replies' type='application/atom+xml' href='http://ctotodevelopers.blogspot.com/feeds/8768166093058589915/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://ctotodevelopers.blogspot.com/2009/08/what-if-we-all-went-ecommerce-only.html#comment-form' title='2 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/10332387/posts/default/8768166093058589915'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/10332387/posts/default/8768166093058589915'/><link rel='alternate' type='text/html' href='http://ctotodevelopers.blogspot.com/2009/08/what-if-we-all-went-ecommerce-only.html' title='What if we all went ECommerce Only?'/><author><name>Isaac Sacolick</name><uri>https://profiles.google.com/109747073147504760416</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='32' src='//lh4.googleusercontent.com/-pgtwy5F24tA/AAAAAAAAAAI/AAAAAAAAAAA/ZfSNeF9Egr8/s512-c/photo.jpg'/></author><thr:total>2</thr:total></entry><entry><id>tag:blogger.com,1999:blog-10332387.post-8505375660372785067</id><published>2009-08-18T16:20:00.005-04:00</published><updated>2009-08-18T16:29:49.835-04:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='about me'/><category scheme='http://www.blogger.com/atom/ns#' term='business exchange'/><title type='text'>On Top of the Business World</title><summary type='text'>Well, a bit of 24 hours a fame as I've been honored as the Business Exchange featured user today and am featured on the Business Week home page. Some of my important topics are Agile Software Development and Enterprise 2.0, or you can also check out my Business Exchange profile.</summary><link rel='replies' type='application/atom+xml' href='http://ctotodevelopers.blogspot.com/feeds/8505375660372785067/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://ctotodevelopers.blogspot.com/2009/08/on-top-of-business-world.html#comment-form' title='3 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/10332387/posts/default/8505375660372785067'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/10332387/posts/default/8505375660372785067'/><link rel='alternate' type='text/html' href='http://ctotodevelopers.blogspot.com/2009/08/on-top-of-business-world.html' title='On Top of the Business World'/><author><name>Isaac Sacolick</name><uri>https://profiles.google.com/109747073147504760416</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='32' src='//lh4.googleusercontent.com/-pgtwy5F24tA/AAAAAAAAAAI/AAAAAAAAAAA/ZfSNeF9Egr8/s512-c/photo.jpg'/></author><media:thumbnail xmlns:media='http://search.yahoo.com/mrss/' url='http://2.bp.blogspot.com/_y1jpflueSAA/SosNbgqKimI/AAAAAAAAACY/dT6uOtZMavE/s72-c/IS+Featured+User+on+BW.png' height='72' width='72'/><thr:total>3</thr:total></entry><entry><id>tag:blogger.com,1999:blog-10332387.post-1029309203528926218</id><published>2009-07-14T08:51:00.004-04:00</published><updated>2009-07-14T14:43:45.286-04:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='SaaS'/><category scheme='http://www.blogger.com/atom/ns#' term='innovation'/><category scheme='http://www.blogger.com/atom/ns#' term='in the news'/><category scheme='http://www.blogger.com/atom/ns#' term='cloud computing'/><category scheme='http://www.blogger.com/atom/ns#' term='google'/><category scheme='http://www.blogger.com/atom/ns#' term='microsoft'/><title type='text'>The Next Tech Battle: Chrome OS vs. Office Web Apps</title><summary type='text'>I've seen some good posts covering Chrome OS and now Microsoft on SaaS enabling Office. These can emerge as disruptive innovations especially to small businesses and students. Google is challenging Microsoft as the OS of choice for notebooks or said another way, we've got it all wrong and it's not about replacing the OS on PC'sSo if all you want to do is get online to browse the Web, check email,</summary><link rel='replies' type='application/atom+xml' href='http://ctotodevelopers.blogspot.com/feeds/1029309203528926218/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://ctotodevelopers.blogspot.com/2009/07/next-tech-battle-chrome-os-vs-office.html#comment-form' title='2 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/10332387/posts/default/1029309203528926218'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/10332387/posts/default/1029309203528926218'/><link rel='alternate' type='text/html' href='http://ctotodevelopers.blogspot.com/2009/07/next-tech-battle-chrome-os-vs-office.html' title='The Next Tech Battle: Chrome OS vs. Office Web Apps'/><author><name>Isaac Sacolick</name><uri>https://profiles.google.com/109747073147504760416</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='32' src='//lh4.googleusercontent.com/-pgtwy5F24tA/AAAAAAAAAAI/AAAAAAAAAAA/ZfSNeF9Egr8/s512-c/photo.jpg'/></author><thr:total>2</thr:total></entry><entry><id>tag:blogger.com,1999:blog-10332387.post-801557175978447626</id><published>2009-07-10T12:49:00.000-04:00</published><updated>2009-12-08T00:03:55.277-05:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='organizational change'/><category scheme='http://www.blogger.com/atom/ns#' term='agile software development'/><title type='text'>Why Agile in the Enterprise is hard, and how to make it Easier – Multiple Stakeholders</title><summary type='text'>I’ll get straight to the point, there are several reasons, and I’m going to focus this post on one primary reason. It goes like thisAgile is optimized when there is a single product owner that can own and prioritize the backlog.In an enterprise, there are multiple stakeholders often with different priorities and different (sometime conflicting) needs around specific enhancements.Enhancements </summary><link rel='replies' type='application/atom+xml' href='http://ctotodevelopers.blogspot.com/feeds/801557175978447626/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://ctotodevelopers.blogspot.com/2009/07/why-agile-in-enterprise-is-hard-and-how.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/10332387/posts/default/801557175978447626'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/10332387/posts/default/801557175978447626'/><link rel='alternate' type='text/html' href='http://ctotodevelopers.blogspot.com/2009/07/why-agile-in-enterprise-is-hard-and-how.html' title='Why Agile in the Enterprise is hard, and how to make it Easier – Multiple Stakeholders'/><author><name>Isaac Sacolick</name><uri>https://profiles.google.com/109747073147504760416</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='32' src='//lh4.googleusercontent.com/-pgtwy5F24tA/AAAAAAAAAAI/AAAAAAAAAAA/ZfSNeF9Egr8/s512-c/photo.jpg'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-10332387.post-8099506314783131767</id><published>2009-07-05T22:28:00.004-04:00</published><updated>2009-07-05T22:43:55.096-04:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='agile software development'/><category scheme='http://www.blogger.com/atom/ns#' term='innovation'/><category scheme='http://www.blogger.com/atom/ns#' term='in the news'/><category scheme='http://www.blogger.com/atom/ns#' term='links'/><title type='text'>Top 5 Links, Week of June 28</title><summary type='text'>Agile Product Development: Why incremental development is better - Very interesting analysis on ROI, #agile vs waterfall. I'm going to need to review the tool/mathAgile Techniques, Agile Hype and the Essence of Agile [in IT and Business] -  "Agile philosophy drives a new paradigm of cooperation between IT and business"8 Challenges To Address For A Successful Transition To Agile - A really good </summary><link rel='replies' type='application/atom+xml' href='http://ctotodevelopers.blogspot.com/feeds/8099506314783131767/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://ctotodevelopers.blogspot.com/2009/07/top-5-links-week-of-june-28.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/10332387/posts/default/8099506314783131767'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/10332387/posts/default/8099506314783131767'/><link rel='alternate' type='text/html' href='http://ctotodevelopers.blogspot.com/2009/07/top-5-links-week-of-june-28.html' title='Top 5 Links, Week of June 28'/><author><name>Isaac Sacolick</name><uri>https://profiles.google.com/109747073147504760416</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='32' src='//lh4.googleusercontent.com/-pgtwy5F24tA/AAAAAAAAAAI/AAAAAAAAAAA/ZfSNeF9Egr8/s512-c/photo.jpg'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-10332387.post-2618075792343738185</id><published>2009-06-30T09:21:00.000-04:00</published><updated>2009-06-30T09:21:55.934-04:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='agile software development'/><category scheme='http://www.blogger.com/atom/ns#' term='about me'/><category scheme='http://www.blogger.com/atom/ns#' term='business exchange'/><title type='text'>Social, Agile, and Transformation June Update</title><summary type='text'>It's been an interesting couple of months, so I thought I'd update readers of this blog on some exciting newsFirst, BusinessWeek.com relaunched its home page last week. As I tweeted last week, this project has been another success story on implementing the agile lifecycle in an enterprise. I can't disclose too much of the technology secrets behind this page, but what I can say is that we didn't </summary><link rel='replies' type='application/atom+xml' href='http://ctotodevelopers.blogspot.com/feeds/2618075792343738185/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://ctotodevelopers.blogspot.com/2009/06/social-agile-and-transformation-june.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/10332387/posts/default/2618075792343738185'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/10332387/posts/default/2618075792343738185'/><link rel='alternate' type='text/html' href='http://ctotodevelopers.blogspot.com/2009/06/social-agile-and-transformation-june.html' title='Social, Agile, and Transformation June Update'/><author><name>Isaac Sacolick</name><uri>https://profiles.google.com/109747073147504760416</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='32' src='//lh4.googleusercontent.com/-pgtwy5F24tA/AAAAAAAAAAI/AAAAAAAAAAA/ZfSNeF9Egr8/s512-c/photo.jpg'/></author><media:thumbnail xmlns:media='http://search.yahoo.com/mrss/' url='http://farm3.static.flickr.com/2069/3543066955_f694819c78_t.jpg' height='72' width='72'/><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-10332387.post-361301884140505422</id><published>2009-06-23T09:34:00.000-04:00</published><updated>2009-12-08T00:03:55.278-05:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='organizational change'/><category scheme='http://www.blogger.com/atom/ns#' term='product management'/><category scheme='http://www.blogger.com/atom/ns#' term='agile software development'/><category scheme='http://www.blogger.com/atom/ns#' term='innovation'/><title type='text'>Top 5 Reasons Why Agile Development Spurs Innovation</title><summary type='text'>Following an agile software development process does not guarantee innovation, but following this development process does increase the odds of teams producing more innovation and innovative solutions. The list below illustrate elements of the agile processes that increase the likelihood of innovation:1) Agile development encourages cross functional teams and direct, frequent communication with </summary><link rel='replies' type='application/atom+xml' href='http://ctotodevelopers.blogspot.com/feeds/361301884140505422/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://ctotodevelopers.blogspot.com/2009/06/top-5-reasons-why-agile-development.html#comment-form' title='6 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/10332387/posts/default/361301884140505422'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/10332387/posts/default/361301884140505422'/><link rel='alternate' type='text/html' href='http://ctotodevelopers.blogspot.com/2009/06/top-5-reasons-why-agile-development.html' title='Top 5 Reasons Why Agile Development Spurs Innovation'/><author><name>Isaac Sacolick</name><uri>https://profiles.google.com/109747073147504760416</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='32' src='//lh4.googleusercontent.com/-pgtwy5F24tA/AAAAAAAAAAI/AAAAAAAAAAA/ZfSNeF9Egr8/s512-c/photo.jpg'/></author><thr:total>6</thr:total></entry><entry><id>tag:blogger.com,1999:blog-10332387.post-2212531914824404042</id><published>2009-06-09T08:20:00.000-04:00</published><updated>2009-12-08T00:03:55.279-05:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='organizational change'/><category scheme='http://www.blogger.com/atom/ns#' term='product management'/><category scheme='http://www.blogger.com/atom/ns#' term='agile software development'/><category scheme='http://www.blogger.com/atom/ns#' term='project management'/><category scheme='http://www.blogger.com/atom/ns#' term='innovation'/><title type='text'>Maturing agile development without a maturity model</title><summary type='text'>As you saw from my last post, I’m fairly bearish when it comes to maturity models. In many cases, maturity models are just tools used by consultants and sales engineers selling expensive ‘how to’ guides to senior IT executives. But even discounting these out, maturity models are guides to help managers size up their current processes, identify gaps, and leverage ‘off the shelf’ processes to gain </summary><link rel='replies' type='application/atom+xml' href='http://ctotodevelopers.blogspot.com/feeds/2212531914824404042/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://ctotodevelopers.blogspot.com/2009/06/maturing-agile-development-without.html#comment-form' title='2 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/10332387/posts/default/2212531914824404042'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/10332387/posts/default/2212531914824404042'/><link rel='alternate' type='text/html' href='http://ctotodevelopers.blogspot.com/2009/06/maturing-agile-development-without.html' title='Maturing agile development without a maturity model'/><author><name>Isaac Sacolick</name><uri>https://profiles.google.com/109747073147504760416</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='32' src='//lh4.googleusercontent.com/-pgtwy5F24tA/AAAAAAAAAAI/AAAAAAAAAAA/ZfSNeF9Egr8/s512-c/photo.jpg'/></author><thr:total>2</thr:total></entry><entry><id>tag:blogger.com,1999:blog-10332387.post-800791763260601953</id><published>2009-06-02T08:55:00.000-04:00</published><updated>2009-06-02T08:57:15.869-04:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='agile software development'/><category scheme='http://www.blogger.com/atom/ns#' term='project management'/><title type='text'>Agile Does Not Need A Maturity Model</title><summary type='text'>This post, Does Agile Need Its Own Process Maturity Model caught my attention. Now there's nothing wrong with the article or some of the concepts, but I feel compelled to throw in my two cents on maturity models in general and especially applied to agile software development.In general, I've only seen maturity models used in one way - to sell enterprise executives either software or services. </summary><link rel='replies' type='application/atom+xml' href='http://ctotodevelopers.blogspot.com/feeds/800791763260601953/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://ctotodevelopers.blogspot.com/2009/06/agile-does-not-need-maturity-model.html#comment-form' title='2 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/10332387/posts/default/800791763260601953'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/10332387/posts/default/800791763260601953'/><link rel='alternate' type='text/html' href='http://ctotodevelopers.blogspot.com/2009/06/agile-does-not-need-maturity-model.html' title='Agile Does Not Need A Maturity Model'/><author><name>Isaac Sacolick</name><uri>https://profiles.google.com/109747073147504760416</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='32' src='//lh4.googleusercontent.com/-pgtwy5F24tA/AAAAAAAAAAI/AAAAAAAAAAA/ZfSNeF9Egr8/s512-c/photo.jpg'/></author><thr:total>2</thr:total></entry><entry><id>tag:blogger.com,1999:blog-10332387.post-8658705916501099551</id><published>2009-05-27T18:10:00.000-04:00</published><updated>2009-05-27T18:16:06.437-04:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='SaaS'/><category scheme='http://www.blogger.com/atom/ns#' term='amazon'/><category scheme='http://www.blogger.com/atom/ns#' term='cloud computing'/><category scheme='http://www.blogger.com/atom/ns#' term='startup cto'/><title type='text'>Amazon Cloud - Becoming a Storm?</title><summary type='text'>When Amazon Web Services came out with S3 and EC2, I was skeptical even though I was and continue to be a strong proponent of SaaS. Why would I buy hosting from a large internet retailer when there are so many companies offering inexpensive hosting models?One year later, I began using S3 via JungleDisk at home as a way to backup my hundreds of gigabytes of photos.Then a couple of weeks ago, I saw</summary><link rel='replies' type='application/atom+xml' href='http://ctotodevelopers.blogspot.com/feeds/8658705916501099551/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://ctotodevelopers.blogspot.com/2009/05/amazon-cloud-becoming-storm.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/10332387/posts/default/8658705916501099551'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/10332387/posts/default/8658705916501099551'/><link rel='alternate' type='text/html' href='http://ctotodevelopers.blogspot.com/2009/05/amazon-cloud-becoming-storm.html' title='Amazon Cloud - Becoming a Storm?'/><author><name>Isaac Sacolick</name><uri>https://profiles.google.com/109747073147504760416</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='32' src='//lh4.googleusercontent.com/-pgtwy5F24tA/AAAAAAAAAAI/AAAAAAAAAAA/ZfSNeF9Egr8/s512-c/photo.jpg'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-10332387.post-154387346140507469</id><published>2009-04-28T09:40:00.000-04:00</published><updated>2009-04-28T09:41:05.612-04:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='web 2.0'/><category scheme='http://www.blogger.com/atom/ns#' term='media and publishing'/><title type='text'>Retaining and Growing Readers on Newspaper Web and Mobile Sites</title><summary type='text'>I am from one of the last generations of ritual NY Times Sunday edition readers. I have fond memories of taking the tree with me to parks and beaches during the summertime to read the magazine and many of the other sections. I even found my first out of college jobs from a help wanted ad in the Times that my wife (then girlfriend) mailed to me while finishing grad school at the University of </summary><link rel='replies' type='application/atom+xml' href='http://ctotodevelopers.blogspot.com/feeds/154387346140507469/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://ctotodevelopers.blogspot.com/2009/04/retaining-and-growing-readers-on.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/10332387/posts/default/154387346140507469'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/10332387/posts/default/154387346140507469'/><link rel='alternate' type='text/html' href='http://ctotodevelopers.blogspot.com/2009/04/retaining-and-growing-readers-on.html' title='Retaining and Growing Readers on Newspaper Web and Mobile Sites'/><author><name>Isaac Sacolick</name><uri>https://profiles.google.com/109747073147504760416</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='32' src='//lh4.googleusercontent.com/-pgtwy5F24tA/AAAAAAAAAAI/AAAAAAAAAAA/ZfSNeF9Egr8/s512-c/photo.jpg'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-10332387.post-2978045727914438364</id><published>2009-04-16T10:00:00.000-04:00</published><updated>2009-04-16T10:00:59.774-04:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='product management'/><category scheme='http://www.blogger.com/atom/ns#' term='agile software development'/><title type='text'>Business Responsibilities working with Agile Teams Part 2</title><summary type='text'>See Business Responsibilities working with Agile Teams Part 1 where I cover some important responsibilities: Dedicating time to define requirements, setting reasonable customer expectations, and developing a methodology for prioritizing.The list below is a bit more tactical and technical:1) Learn the lingo and the process - Don't look at agile as a 'tech process'. When I discuss agile to business</summary><link rel='replies' type='application/atom+xml' href='http://ctotodevelopers.blogspot.com/feeds/2978045727914438364/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://ctotodevelopers.blogspot.com/2009/04/business-responsibilities-working-with_16.html#comment-form' title='1 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/10332387/posts/default/2978045727914438364'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/10332387/posts/default/2978045727914438364'/><link rel='alternate' type='text/html' href='http://ctotodevelopers.blogspot.com/2009/04/business-responsibilities-working-with_16.html' title='Business Responsibilities working with Agile Teams Part 2'/><author><name>Isaac Sacolick</name><uri>https://profiles.google.com/109747073147504760416</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='32' src='//lh4.googleusercontent.com/-pgtwy5F24tA/AAAAAAAAAAI/AAAAAAAAAAA/ZfSNeF9Egr8/s512-c/photo.jpg'/></author><thr:total>1</thr:total></entry><entry><id>tag:blogger.com,1999:blog-10332387.post-1139549702695540354</id><published>2009-04-10T09:11:00.001-04:00</published><updated>2009-04-10T09:11:32.573-04:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='product management'/><category scheme='http://www.blogger.com/atom/ns#' term='agile software development'/><category scheme='http://www.blogger.com/atom/ns#' term='business exchange'/><title type='text'>Business Responsibilities working with Agile Teams Part 1</title><summary type='text'>I enjoy talking to General Managers, Product Managers, and other members of a business teams about the benefits of going agile. Their eyes light up when I talk about the basics. They get to see completed product at the end of each iteration, get the ability to change priorities and requirements, and there is minimal up front work developing requirements. They 'get it' - speed to market and the </summary><link rel='replies' type='application/atom+xml' href='http://ctotodevelopers.blogspot.com/feeds/1139549702695540354/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://ctotodevelopers.blogspot.com/2009/04/business-responsibilities-working-with.html#comment-form' title='1 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/10332387/posts/default/1139549702695540354'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/10332387/posts/default/1139549702695540354'/><link rel='alternate' type='text/html' href='http://ctotodevelopers.blogspot.com/2009/04/business-responsibilities-working-with.html' title='Business Responsibilities working with Agile Teams Part 1'/><author><name>Isaac Sacolick</name><uri>https://profiles.google.com/109747073147504760416</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='32' src='//lh4.googleusercontent.com/-pgtwy5F24tA/AAAAAAAAAAI/AAAAAAAAAAA/ZfSNeF9Egr8/s512-c/photo.jpg'/></author><thr:total>1</thr:total></entry><entry><id>tag:blogger.com,1999:blog-10332387.post-1777548573062872256</id><published>2009-03-26T00:03:00.000-04:00</published><updated>2009-03-26T00:04:42.375-04:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='agile software development'/><category scheme='http://www.blogger.com/atom/ns#' term='project management'/><title type='text'>Enterprise Agile Development - Why you still need Project Managers</title><summary type='text'>I've been asked lately about the role of project managers on agile or SCRUM teams. While project managers can perform specific roles within the team, they often perform functions that go beyond the scope of an agile team's direct responsibilities. Some specifics:Scrum and agile are very team and inward facing. Project managers help manage all the external dependencies including vendors, suppliers</summary><link rel='replies' type='application/atom+xml' href='http://ctotodevelopers.blogspot.com/feeds/1777548573062872256/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://ctotodevelopers.blogspot.com/2009/03/enterprise-agile-development-why-you.html#comment-form' title='3 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/10332387/posts/default/1777548573062872256'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/10332387/posts/default/1777548573062872256'/><link rel='alternate' type='text/html' href='http://ctotodevelopers.blogspot.com/2009/03/enterprise-agile-development-why-you.html' title='Enterprise Agile Development - Why you still need Project Managers'/><author><name>Isaac Sacolick</name><uri>https://profiles.google.com/109747073147504760416</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='32' src='//lh4.googleusercontent.com/-pgtwy5F24tA/AAAAAAAAAAI/AAAAAAAAAAA/ZfSNeF9Egr8/s512-c/photo.jpg'/></author><thr:total>3</thr:total></entry><entry><id>tag:blogger.com,1999:blog-10332387.post-6957284993696702096</id><published>2009-03-18T00:02:00.000-04:00</published><updated>2009-03-17T22:30:56.178-04:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='agile software development'/><category scheme='http://www.blogger.com/atom/ns#' term='project management'/><category scheme='http://www.blogger.com/atom/ns#' term='offshore development'/><title type='text'>Offshore Agile Development - Totally Feasible!</title><summary type='text'>I just returned from Chennai, India where I had the pleasure of working with a relatively small team of developers. We started working with them a year ago with the simple goal of  getting one project completed for Business Exchange. Over the course of the year, we've tripled the size of the team and now have several teams practicing agile development similar to how we do it on site.Myth: You </summary><link rel='replies' type='application/atom+xml' href='http://ctotodevelopers.blogspot.com/feeds/6957284993696702096/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://ctotodevelopers.blogspot.com/2009/03/offshore-agile-development-totally.html#comment-form' title='2 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/10332387/posts/default/6957284993696702096'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/10332387/posts/default/6957284993696702096'/><link rel='alternate' type='text/html' href='http://ctotodevelopers.blogspot.com/2009/03/offshore-agile-development-totally.html' title='Offshore Agile Development - Totally Feasible!'/><author><name>Isaac Sacolick</name><uri>https://profiles.google.com/109747073147504760416</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='32' src='//lh4.googleusercontent.com/-pgtwy5F24tA/AAAAAAAAAAI/AAAAAAAAAAA/ZfSNeF9Egr8/s512-c/photo.jpg'/></author><thr:total>2</thr:total></entry><entry><id>tag:blogger.com,1999:blog-10332387.post-5454409048892909354</id><published>2009-02-23T08:39:00.000-05:00</published><updated>2009-02-23T08:39:43.899-05:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='agile software development'/><category scheme='http://www.blogger.com/atom/ns#' term='project management'/><category scheme='http://www.blogger.com/atom/ns#' term='it management'/><title type='text'>Top Ten Thoughts for SCRUM Newbies</title><summary type='text'>My colleagues and I from BusinessWeek gave a presentation last week covering our agile planning and development process and ended with an intro to SCRUM by @silviogalea. Roughly the same time, @jurgenappelo posted an excellent, easy to follow slideshare on The Zen of SCRUM 1.0. Here are my top takeaways (no particular order) from these presentations plus some of my own thoughts:1) Organizations </summary><link rel='replies' type='application/atom+xml' href='http://ctotodevelopers.blogspot.com/feeds/5454409048892909354/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://ctotodevelopers.blogspot.com/2009/02/top-ten-thoughts-for-scrum-newbies.html#comment-form' title='2 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/10332387/posts/default/5454409048892909354'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/10332387/posts/default/5454409048892909354'/><link rel='alternate' type='text/html' href='http://ctotodevelopers.blogspot.com/2009/02/top-ten-thoughts-for-scrum-newbies.html' title='Top Ten Thoughts for SCRUM Newbies'/><author><name>Isaac Sacolick</name><uri>https://profiles.google.com/109747073147504760416</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='32' src='//lh4.googleusercontent.com/-pgtwy5F24tA/AAAAAAAAAAI/AAAAAAAAAAA/ZfSNeF9Egr8/s512-c/photo.jpg'/></author><thr:total>2</thr:total></entry><entry><id>tag:blogger.com,1999:blog-10332387.post-8807280326370379359</id><published>2009-02-12T22:38:00.002-05:00</published><updated>2009-02-12T22:44:41.901-05:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='SaaS'/><category scheme='http://www.blogger.com/atom/ns#' term='enterprise 2.0'/><category scheme='http://www.blogger.com/atom/ns#' term='it management'/><title type='text'>How does your SaaS vendor respond to the scalability question?</title><summary type='text'>Ask some CTO’s about how their product scales and they’ll whip out a logical diagram showing you redundant networks, redundant firewalls, load balancers, clustered application servers, redundant databases, and SAN storage. If you’re lucky they’ll tell you about their software stack and then throw in a bit about their software development life cycle.If this is how your SaaS vendor responds to </summary><link rel='replies' type='application/atom+xml' href='http://ctotodevelopers.blogspot.com/feeds/8807280326370379359/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://ctotodevelopers.blogspot.com/2009/02/how-does-your-saas-vendor-respond-to.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/10332387/posts/default/8807280326370379359'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/10332387/posts/default/8807280326370379359'/><link rel='alternate' type='text/html' href='http://ctotodevelopers.blogspot.com/2009/02/how-does-your-saas-vendor-respond-to.html' title='How does your SaaS vendor respond to the scalability question?'/><author><name>Isaac Sacolick</name><uri>https://profiles.google.com/109747073147504760416</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='32' src='//lh4.googleusercontent.com/-pgtwy5F24tA/AAAAAAAAAAI/AAAAAAAAAAA/ZfSNeF9Egr8/s512-c/photo.jpg'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-10332387.post-8586185812675330171</id><published>2009-02-08T21:10:00.003-05:00</published><updated>2009-02-08T21:35:13.550-05:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='product management'/><category scheme='http://www.blogger.com/atom/ns#' term='agile software development'/><category scheme='http://www.blogger.com/atom/ns#' term='project management'/><title type='text'>Agile Product Owners in the Enterprise</title><summary type='text'>I really like this post Agile Product Owner and Agile Product Manager in the Enterprise that highlights the organizational issue of trying to staff agile product owners in the enterprise's technology organization. Staffed this way, product owners are bound to contend with product managers because their responsibilities somewhat overlap. On the other hand, trying to get a product manager to take </summary><link rel='replies' type='application/atom+xml' href='http://ctotodevelopers.blogspot.com/feeds/8586185812675330171/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://ctotodevelopers.blogspot.com/2009/02/agile-product-owners-in-enterprise.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/10332387/posts/default/8586185812675330171'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/10332387/posts/default/8586185812675330171'/><link rel='alternate' type='text/html' href='http://ctotodevelopers.blogspot.com/2009/02/agile-product-owners-in-enterprise.html' title='Agile Product Owners in the Enterprise'/><author><name>Isaac Sacolick</name><uri>https://profiles.google.com/109747073147504760416</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='32' src='//lh4.googleusercontent.com/-pgtwy5F24tA/AAAAAAAAAAI/AAAAAAAAAAA/ZfSNeF9Egr8/s512-c/photo.jpg'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-10332387.post-2094039396865534087</id><published>2009-02-03T21:30:00.003-05:00</published><updated>2009-02-03T21:45:05.260-05:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='SaaS'/><category scheme='http://www.blogger.com/atom/ns#' term='enterprise 2.0'/><category scheme='http://www.blogger.com/atom/ns#' term='it management'/><title type='text'>Evaluating SaaS Vendors – Understanding Business Models and Profitability</title><summary type='text'>For those of you who don’t know, I was CTO of a SaaS vendor a number of years ago. In addition to building a SaaS platform (back then in 1996 when we started we were an ASP – application service provider), we acquired and merged with a number of other SaaS companies. Part of my job was to evaluate the viability of the SaaS company's technology platform and operations. So I have a few things to </summary><link rel='replies' type='application/atom+xml' href='http://ctotodevelopers.blogspot.com/feeds/2094039396865534087/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://ctotodevelopers.blogspot.com/2009/02/evaluating-saas-vendors-understanding.html#comment-form' title='4 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/10332387/posts/default/2094039396865534087'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/10332387/posts/default/2094039396865534087'/><link rel='alternate' type='text/html' href='http://ctotodevelopers.blogspot.com/2009/02/evaluating-saas-vendors-understanding.html' title='Evaluating SaaS Vendors – Understanding Business Models and Profitability'/><author><name>Isaac Sacolick</name><uri>https://profiles.google.com/109747073147504760416</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='32' src='//lh4.googleusercontent.com/-pgtwy5F24tA/AAAAAAAAAAI/AAAAAAAAAAA/ZfSNeF9Egr8/s512-c/photo.jpg'/></author><thr:total>4</thr:total></entry><entry><id>tag:blogger.com,1999:blog-10332387.post-4127219100705249830</id><published>2009-01-27T00:01:00.000-05:00</published><updated>2009-01-27T00:02:13.701-05:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='SaaS'/><category scheme='http://www.blogger.com/atom/ns#' term='enterprise 2.0'/><category scheme='http://www.blogger.com/atom/ns#' term='it management'/><title type='text'>Don't be afraid of SaaS, but Diligence is Required</title><summary type='text'>I was disappointed with last weeks eWeek articles covering SaaS reliability. They covered KITE for measuring reliability, but did not cover similar offerings such as Gomez or Siteseer. Their top 10 things you should know now about SaaS read like a bunch of scare tactics; is it really cost effective, can they maintain SLAs, is the vendor viable - all real, legitimate concerns, but somewhat an </summary><link rel='replies' type='application/atom+xml' href='http://ctotodevelopers.blogspot.com/feeds/4127219100705249830/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://ctotodevelopers.blogspot.com/2009/01/dont-be-afraid-of-saas-but-diligence-is.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/10332387/posts/default/4127219100705249830'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/10332387/posts/default/4127219100705249830'/><link rel='alternate' type='text/html' href='http://ctotodevelopers.blogspot.com/2009/01/dont-be-afraid-of-saas-but-diligence-is.html' title='Don&apos;t be afraid of SaaS, but Diligence is Required'/><author><name>Isaac Sacolick</name><uri>https://profiles.google.com/109747073147504760416</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='32' src='//lh4.googleusercontent.com/-pgtwy5F24tA/AAAAAAAAAAI/AAAAAAAAAAA/ZfSNeF9Egr8/s512-c/photo.jpg'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-10332387.post-2566677833687027751</id><published>2009-01-20T21:15:00.001-05:00</published><updated>2009-01-20T21:19:02.953-05:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='software qa'/><category scheme='http://www.blogger.com/atom/ns#' term='agile software development'/><category scheme='http://www.blogger.com/atom/ns#' term='software development'/><title type='text'>Call 4th Down Audibles in Agile Development, But Don't Pull The Goalie</title><summary type='text'>I got some questions about my tweet from last week on 4th down audibles and pulling goalies. Here's what I meant in more detail...When you start an iteration, the team makes some best estimates on what can be accomplished in an iteration. The estimates are partially based on effort, but also based on risk. When a story's implementation requires familiar technologies, developers will often rate it</summary><link rel='replies' type='application/atom+xml' href='http://ctotodevelopers.blogspot.com/feeds/2566677833687027751/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://ctotodevelopers.blogspot.com/2009/01/call-4th-down-audibles-in-agile.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/10332387/posts/default/2566677833687027751'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/10332387/posts/default/2566677833687027751'/><link rel='alternate' type='text/html' href='http://ctotodevelopers.blogspot.com/2009/01/call-4th-down-audibles-in-agile.html' title='Call 4th Down Audibles in Agile Development, But Don&apos;t Pull The Goalie'/><author><name>Isaac Sacolick</name><uri>https://profiles.google.com/109747073147504760416</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='32' src='//lh4.googleusercontent.com/-pgtwy5F24tA/AAAAAAAAAAI/AAAAAAAAAAA/ZfSNeF9Egr8/s512-c/photo.jpg'/></author><media:thumbnail xmlns:media='http://search.yahoo.com/mrss/' url='http://2.bp.blogspot.com/_y1jpflueSAA/SXVNNPky1QI/AAAAAAAAAB0/WT7Grvq_Omg/s72-c/Tweet1.jpg' height='72' width='72'/><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-10332387.post-2923633409277531335</id><published>2009-01-14T23:40:00.008-05:00</published><updated>2009-01-15T00:21:55.468-05:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='customer service'/><title type='text'>NAS Network Storage for the Home and Advice for Device Manufacturers</title><summary type='text'>I expect that there will be a boom in storage device and services for the home market over the next couple of years. People are already consuming larger amounts of disk for audio, video, and images. With larger storage needs, backing up onto CD's or DVD's becomes more cumbersome. At the same time trends show that people are upgrading their PC's less frequently. The result is that they are </summary><link rel='replies' type='application/atom+xml' href='http://ctotodevelopers.blogspot.com/feeds/2923633409277531335/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://ctotodevelopers.blogspot.com/2009/01/nas-network-storage-for-home-and-advice.html#comment-form' title='3 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/10332387/posts/default/2923633409277531335'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/10332387/posts/default/2923633409277531335'/><link rel='alternate' type='text/html' href='http://ctotodevelopers.blogspot.com/2009/01/nas-network-storage-for-home-and-advice.html' title='NAS Network Storage for the Home and Advice for Device Manufacturers'/><author><name>Isaac Sacolick</name><uri>https://profiles.google.com/109747073147504760416</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='32' src='//lh4.googleusercontent.com/-pgtwy5F24tA/AAAAAAAAAAI/AAAAAAAAAAA/ZfSNeF9Egr8/s512-c/photo.jpg'/></author><thr:total>3</thr:total></entry><entry><id>tag:blogger.com,1999:blog-10332387.post-3586515509707194829</id><published>2009-01-05T22:48:00.012-05:00</published><updated>2009-01-08T00:18:44.086-05:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='social media'/><category scheme='http://www.blogger.com/atom/ns#' term='about me'/><category scheme='http://www.blogger.com/atom/ns#' term='twitter'/><title type='text'>My Views on Twitter</title><summary type='text'>I have to admit, but when I first heard about Twitter I thought it was a tool for the young and well connected. Instead of text'ing friends individually, a college student could Tweet her thoughts and let her friends know what clubs and parties to attend that evening.Boy, was I wrong.Then the bloggers and social media enthusiasts picked it up. PR picked it up. And today I saw to what extent </summary><link rel='replies' type='application/atom+xml' href='http://ctotodevelopers.blogspot.com/feeds/3586515509707194829/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://ctotodevelopers.blogspot.com/2009/01/my-views-on-twitter.html#comment-form' title='4 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/10332387/posts/default/3586515509707194829'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/10332387/posts/default/3586515509707194829'/><link rel='alternate' type='text/html' href='http://ctotodevelopers.blogspot.com/2009/01/my-views-on-twitter.html' title='My Views on Twitter'/><author><name>Isaac Sacolick</name><uri>https://profiles.google.com/109747073147504760416</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='32' src='//lh4.googleusercontent.com/-pgtwy5F24tA/AAAAAAAAAAI/AAAAAAAAAAA/ZfSNeF9Egr8/s512-c/photo.jpg'/></author><thr:total>4</thr:total></entry><entry><id>tag:blogger.com,1999:blog-10332387.post-363970189723707296</id><published>2009-01-05T08:33:00.000-05:00</published><updated>2009-01-05T08:34:23.230-05:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='content agility'/><category scheme='http://www.blogger.com/atom/ns#' term='agile software development'/><category scheme='http://www.blogger.com/atom/ns#' term='media and publishing'/><title type='text'>Agile in 2008 to Twitter, Cloud Computing and Publishing in 2009</title><summary type='text'>Looking back to 2008, I shifted this blog from covering startups and issues for CTOs (re: Startup CTO) and covered a lot about the agile software development life cycle. Having moved from a small company, to a startup, and then to an enterprise, much of what I wrote covered agile in the enterprise. Some titles included big questions enterprises should consider before going agile,  ingredients on </summary><link rel='replies' type='application/atom+xml' href='http://ctotodevelopers.blogspot.com/feeds/363970189723707296/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://ctotodevelopers.blogspot.com/2009/01/agile-in-2008-to-twitter-cloud.html#comment-form' title='1 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/10332387/posts/default/363970189723707296'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/10332387/posts/default/363970189723707296'/><link rel='alternate' type='text/html' href='http://ctotodevelopers.blogspot.com/2009/01/agile-in-2008-to-twitter-cloud.html' title='Agile in 2008 to Twitter, Cloud Computing and Publishing in 2009'/><author><name>Isaac Sacolick</name><uri>https://profiles.google.com/109747073147504760416</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='32' src='//lh4.googleusercontent.com/-pgtwy5F24tA/AAAAAAAAAAI/AAAAAAAAAAA/ZfSNeF9Egr8/s512-c/photo.jpg'/></author><thr:total>1</thr:total></entry><entry><id>tag:blogger.com,1999:blog-10332387.post-3397184946992128489</id><published>2008-12-29T15:05:00.001-05:00</published><updated>2008-12-29T15:12:33.676-05:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='software qa'/><category scheme='http://www.blogger.com/atom/ns#' term='agile software development'/><category scheme='http://www.blogger.com/atom/ns#' term='software development'/><category scheme='http://www.blogger.com/atom/ns#' term='project management'/><title type='text'>Top 5 Attributes of Talented Agile Developers</title><summary type='text'>Instituting the agile development life cycle in an enterprise requires technology talent. I made this statement in Getting Enterprises Executives to buy into an Agile Development Lifecycle. Here are my top 5 attributes of talented agile developers and what I meant by 'technology talent':1. Agile thinkers are fast thinkers. They solve problems quickly and look for easy solutions. They are not </summary><link rel='replies' type='application/atom+xml' href='http://ctotodevelopers.blogspot.com/feeds/3397184946992128489/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://ctotodevelopers.blogspot.com/2008/12/top-5-attributes-of-talented-agile.html#comment-form' title='3 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/10332387/posts/default/3397184946992128489'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/10332387/posts/default/3397184946992128489'/><link rel='alternate' type='text/html' href='http://ctotodevelopers.blogspot.com/2008/12/top-5-attributes-of-talented-agile.html' title='Top 5 Attributes of Talented Agile Developers'/><author><name>Isaac Sacolick</name><uri>https://profiles.google.com/109747073147504760416</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='32' src='//lh4.googleusercontent.com/-pgtwy5F24tA/AAAAAAAAAAI/AAAAAAAAAAA/ZfSNeF9Egr8/s512-c/photo.jpg'/></author><thr:total>3</thr:total></entry><entry><id>tag:blogger.com,1999:blog-10332387.post-2829308579082765412</id><published>2008-12-04T00:02:00.001-05:00</published><updated>2008-12-04T00:06:01.313-05:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='agile software development'/><category scheme='http://www.blogger.com/atom/ns#' term='software development'/><category scheme='http://www.blogger.com/atom/ns#' term='it management'/><title type='text'>Is Your Enterprise Ready for Agile Development?</title><summary type='text'>What happens when an Enterprise wants to 'go agile'?One of the beauties of agile is in its name. Who doesn't want to be agile? Can you imagine CIO of X Enterprise saying he or she doesn't want their IT departments to be agile? Agile proponents did themselves a favor adopting the generic 'agile development' to represent processes like SCRUM, Extreme Programming, etc.But enterprises have a few </summary><link rel='replies' type='application/atom+xml' href='http://ctotodevelopers.blogspot.com/feeds/2829308579082765412/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://ctotodevelopers.blogspot.com/2008/12/is-your-enterprise-ready-for-agile.html#comment-form' title='1 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/10332387/posts/default/2829308579082765412'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/10332387/posts/default/2829308579082765412'/><link rel='alternate' type='text/html' href='http://ctotodevelopers.blogspot.com/2008/12/is-your-enterprise-ready-for-agile.html' title='Is Your Enterprise Ready for Agile Development?'/><author><name>Isaac Sacolick</name><uri>https://profiles.google.com/109747073147504760416</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='32' src='//lh4.googleusercontent.com/-pgtwy5F24tA/AAAAAAAAAAI/AAAAAAAAAAA/ZfSNeF9Egr8/s512-c/photo.jpg'/></author><thr:total>1</thr:total></entry><entry><id>tag:blogger.com,1999:blog-10332387.post-3330330312909984792</id><published>2008-11-24T00:30:00.000-05:00</published><updated>2008-11-24T00:37:04.126-05:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='agile software development'/><category scheme='http://www.blogger.com/atom/ns#' term='enterprise 2.0'/><category scheme='http://www.blogger.com/atom/ns#' term='about me'/><category scheme='http://www.blogger.com/atom/ns#' term='it management'/><category scheme='http://www.blogger.com/atom/ns#' term='startup cto'/><title type='text'>Getting Enterprise Executives to buy in to an Agile Development Lifecycle</title><summary type='text'>People have asked me, "how do you get executive buy in on moving a department or team to an agile development software lifecycle"? The answer isn't straightforward, but I feel it largely depends on three key elements:The business drivers on investment or change in the software delivery modelOrganizational dynamics and cultureTalent in the technology organizationWhen people have talked to me about</summary><link rel='replies' type='application/atom+xml' href='http://ctotodevelopers.blogspot.com/feeds/3330330312909984792/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://ctotodevelopers.blogspot.com/2008/11/getting-enterprise-executives-to-buy-in.html#comment-form' title='1 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/10332387/posts/default/3330330312909984792'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/10332387/posts/default/3330330312909984792'/><link rel='alternate' type='text/html' href='http://ctotodevelopers.blogspot.com/2008/11/getting-enterprise-executives-to-buy-in.html' title='Getting Enterprise Executives to buy in to an Agile Development Lifecycle'/><author><name>Isaac Sacolick</name><uri>https://profiles.google.com/109747073147504760416</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='32' src='//lh4.googleusercontent.com/-pgtwy5F24tA/AAAAAAAAAAI/AAAAAAAAAAA/ZfSNeF9Egr8/s512-c/photo.jpg'/></author><thr:total>1</thr:total></entry><entry><id>tag:blogger.com,1999:blog-10332387.post-1212697753859311132</id><published>2008-11-18T23:18:00.005-05:00</published><updated>2008-11-18T23:35:30.291-05:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='customer service'/><category scheme='http://www.blogger.com/atom/ns#' term='about me'/><title type='text'>Customer Service Trouble: Changing Flights on Continental</title><summary type='text'>As technologists, we all know bad customer service and poorly designed IT systems when we see them. Folks, that's exactly what I saw last Thursday night when I flied from Newark to Charlotte on Continental Airlines. Flights were delayed due to weather and I went to have my flight changed to an earlier flight. Here's what I went through:Went on the customer service line. Waited five minutes. Agent</summary><link rel='replies' type='application/atom+xml' href='http://ctotodevelopers.blogspot.com/feeds/1212697753859311132/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://ctotodevelopers.blogspot.com/2008/11/customer-service-trouble-changing.html#comment-form' title='3 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/10332387/posts/default/1212697753859311132'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/10332387/posts/default/1212697753859311132'/><link rel='alternate' type='text/html' href='http://ctotodevelopers.blogspot.com/2008/11/customer-service-trouble-changing.html' title='Customer Service Trouble: Changing Flights on Continental'/><author><name>Isaac Sacolick</name><uri>https://profiles.google.com/109747073147504760416</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='32' src='//lh4.googleusercontent.com/-pgtwy5F24tA/AAAAAAAAAAI/AAAAAAAAAAA/ZfSNeF9Egr8/s512-c/photo.jpg'/></author><thr:total>3</thr:total></entry><entry><id>tag:blogger.com,1999:blog-10332387.post-345684090318045066</id><published>2008-11-13T00:19:00.007-05:00</published><updated>2008-11-24T00:59:26.717-05:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='web 2.0'/><category scheme='http://www.blogger.com/atom/ns#' term='content agility'/><category scheme='http://www.blogger.com/atom/ns#' term='agile software development'/><category scheme='http://www.blogger.com/atom/ns#' term='software development'/><category scheme='http://www.blogger.com/atom/ns#' term='business exchange'/><title type='text'>Presentation On Achieving Content Agility in a Web 2.0 Environment</title><summary type='text'>Here is the presentation I gave at Mark Logic's Digital Publishing Summit last week:Achieving Content Agility in a Web 2.0 EnvironmentView SlideShare presentation or Upload your own. (tags: agile web2.0)</summary><link rel='replies' type='application/atom+xml' href='http://ctotodevelopers.blogspot.com/feeds/345684090318045066/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://ctotodevelopers.blogspot.com/2008/11/presentation-on-achieving-content.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/10332387/posts/default/345684090318045066'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/10332387/posts/default/345684090318045066'/><link rel='alternate' type='text/html' href='http://ctotodevelopers.blogspot.com/2008/11/presentation-on-achieving-content.html' title='Presentation On Achieving Content Agility in a Web 2.0 Environment'/><author><name>Isaac Sacolick</name><uri>https://profiles.google.com/109747073147504760416</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='32' src='//lh4.googleusercontent.com/-pgtwy5F24tA/AAAAAAAAAAI/AAAAAAAAAAA/ZfSNeF9Egr8/s512-c/photo.jpg'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-10332387.post-999807254884328772</id><published>2008-11-06T22:34:00.004-05:00</published><updated>2008-11-06T22:59:39.014-05:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='web 2.0'/><category scheme='http://www.blogger.com/atom/ns#' term='content agility'/><category scheme='http://www.blogger.com/atom/ns#' term='agile software development'/><category scheme='http://www.blogger.com/atom/ns#' term='about me'/><category scheme='http://www.blogger.com/atom/ns#' term='business exchange'/><title type='text'>Content Agility at Marklogic's Digital Publishing Symposium</title><summary type='text'>Thanks to Dave Kellogg for inviting me to speak at this year's Mark Logic Digital Publishing Summit. I spoke about how the publishing industry is at a crossroads:Traditional media faces revenue challengesWeb 2.0 startups challenged, short runway on funding, needs to become cash positiveMany technology options for web 2.0, contentXML publishing technologies matureAgile processes become ‘enterprise</summary><link rel='replies' type='application/atom+xml' href='http://ctotodevelopers.blogspot.com/feeds/999807254884328772/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://ctotodevelopers.blogspot.com/2008/11/content-agility-at-marklogics-digital.html#comment-form' title='1 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/10332387/posts/default/999807254884328772'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/10332387/posts/default/999807254884328772'/><link rel='alternate' type='text/html' href='http://ctotodevelopers.blogspot.com/2008/11/content-agility-at-marklogics-digital.html' title='Content Agility at Marklogic&apos;s Digital Publishing Symposium'/><author><name>Isaac Sacolick</name><uri>https://profiles.google.com/109747073147504760416</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='32' src='//lh4.googleusercontent.com/-pgtwy5F24tA/AAAAAAAAAAI/AAAAAAAAAAA/ZfSNeF9Egr8/s512-c/photo.jpg'/></author><thr:total>1</thr:total></entry><entry><id>tag:blogger.com,1999:blog-10332387.post-2509710160022929243</id><published>2008-10-30T07:01:00.000-04:00</published><updated>2008-10-30T07:06:59.096-04:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='web 2.0'/><category scheme='http://www.blogger.com/atom/ns#' term='content agility'/><category scheme='http://www.blogger.com/atom/ns#' term='about me'/><category scheme='http://www.blogger.com/atom/ns#' term='media and publishing'/><category scheme='http://www.blogger.com/atom/ns#' term='business exchange'/><title type='text'>Newspapers and Magazines Need Content Agility</title><summary type='text'>Next week, I will be speaking at the Mark Logic Digital Publishing Summit on the topic Achieving Content Agility in a Web 2.0 Environment. The timing is impeccable as the NY Times Mourns Old Media Decline covering layoffs at Time and Gannett among other cutbacks in newspapers and magazines. Business Exchange has topics on Newspaper Revenue, Newspaper Companies and the Magazine Industry covering </summary><link rel='replies' type='application/atom+xml' href='http://ctotodevelopers.blogspot.com/feeds/2509710160022929243/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://ctotodevelopers.blogspot.com/2008/10/newspapers-and-magazines-need-content.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/10332387/posts/default/2509710160022929243'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/10332387/posts/default/2509710160022929243'/><link rel='alternate' type='text/html' href='http://ctotodevelopers.blogspot.com/2008/10/newspapers-and-magazines-need-content.html' title='Newspapers and Magazines Need Content Agility'/><author><name>Isaac Sacolick</name><uri>https://profiles.google.com/109747073147504760416</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='32' src='//lh4.googleusercontent.com/-pgtwy5F24tA/AAAAAAAAAAI/AAAAAAAAAAA/ZfSNeF9Egr8/s512-c/photo.jpg'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-10332387.post-7575648010557429503</id><published>2008-10-15T22:43:00.005-04:00</published><updated>2008-10-15T23:15:50.916-04:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='agile software development'/><category scheme='http://www.blogger.com/atom/ns#' term='software development'/><category scheme='http://www.blogger.com/atom/ns#' term='project management'/><category scheme='http://www.blogger.com/atom/ns#' term='it management'/><title type='text'>Agile Development as a Driver to Orginizational Change</title><summary type='text'>I gave a short talk today to a group of VPs and CIOs on the nature of Agile. In a true startup, it's very easy for the team to adopt agile. But in an enterprise, agile development is a relatively new software lifecycle. Only recently, maybe the last few years has the agile community established best practices and methodologies that can apply to development performed in larger companies.In </summary><link rel='replies' type='application/atom+xml' href='http://ctotodevelopers.blogspot.com/feeds/7575648010557429503/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://ctotodevelopers.blogspot.com/2008/10/agile-development-as-driver-to.html#comment-form' title='4 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/10332387/posts/default/7575648010557429503'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/10332387/posts/default/7575648010557429503'/><link rel='alternate' type='text/html' href='http://ctotodevelopers.blogspot.com/2008/10/agile-development-as-driver-to.html' title='Agile Development as a Driver to Orginizational Change'/><author><name>Isaac Sacolick</name><uri>https://profiles.google.com/109747073147504760416</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='32' src='//lh4.googleusercontent.com/-pgtwy5F24tA/AAAAAAAAAAI/AAAAAAAAAAA/ZfSNeF9Egr8/s512-c/photo.jpg'/></author><media:thumbnail xmlns:media='http://search.yahoo.com/mrss/' url='http://3.bp.blogspot.com/_y1jpflueSAA/SPatRnZgGAI/AAAAAAAAABI/nk6KwMhrQl4/s72-c/Agile+Teams.gif' height='72' width='72'/><thr:total>4</thr:total></entry><entry><id>tag:blogger.com,1999:blog-10332387.post-7314847038000267142</id><published>2008-09-23T22:16:00.005-04:00</published><updated>2008-09-23T22:49:27.409-04:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='mobile'/><category scheme='http://www.blogger.com/atom/ns#' term='in the news'/><category scheme='http://www.blogger.com/atom/ns#' term='google'/><category scheme='http://www.blogger.com/atom/ns#' term='microsoft'/><category scheme='http://www.blogger.com/atom/ns#' term='apple'/><title type='text'>Platform Wars III: Android vs IPhone vs Blackberry</title><summary type='text'>As I read all the news on the G1 Android, it reminds me of the platform wars (Windows vs Unix) and the browser wars (Netscape vs Microsoft and now Microsoft vs Firefox vs Chrome). Mobile is truly maturing into a competitive environment for application delivery and today's battlefield clearly is IPhone vs. Blackberry vs. Android.I'm not an expert in mobile technology, but I am intrigued on how all</summary><link rel='replies' type='application/atom+xml' href='http://ctotodevelopers.blogspot.com/feeds/7314847038000267142/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://ctotodevelopers.blogspot.com/2008/09/platform-wars-iii-android-vs-iphone-vs.html#comment-form' title='1 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/10332387/posts/default/7314847038000267142'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/10332387/posts/default/7314847038000267142'/><link rel='alternate' type='text/html' href='http://ctotodevelopers.blogspot.com/2008/09/platform-wars-iii-android-vs-iphone-vs.html' title='Platform Wars III: Android vs IPhone vs Blackberry'/><author><name>Isaac Sacolick</name><uri>https://profiles.google.com/109747073147504760416</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='32' src='//lh4.googleusercontent.com/-pgtwy5F24tA/AAAAAAAAAAI/AAAAAAAAAAA/ZfSNeF9Egr8/s512-c/photo.jpg'/></author><thr:total>1</thr:total></entry><entry><id>tag:blogger.com,1999:blog-10332387.post-2441560991880346667</id><published>2008-09-18T23:02:00.009-04:00</published><updated>2008-09-19T00:04:49.382-04:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='web 2.0'/><category scheme='http://www.blogger.com/atom/ns#' term='agile software development'/><category scheme='http://www.blogger.com/atom/ns#' term='about me'/><category scheme='http://www.blogger.com/atom/ns#' term='business exchange'/><title type='text'>What is Business Exchange</title><summary type='text'>Just over a year ago, I joined BusinessWeek to lead the technology efforts around a new product called Business Exchange. One year and many agile development cycles later, the product is live and gaining activity.Business Exchange started with a simple vision statement. Aggregate content from business oriented sources, organize them into business topics that users can create, and prioritize the </summary><link rel='replies' type='application/atom+xml' href='http://ctotodevelopers.blogspot.com/feeds/2441560991880346667/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://ctotodevelopers.blogspot.com/2008/09/what-is-business-exchange.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/10332387/posts/default/2441560991880346667'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/10332387/posts/default/2441560991880346667'/><link rel='alternate' type='text/html' href='http://ctotodevelopers.blogspot.com/2008/09/what-is-business-exchange.html' title='What is Business Exchange'/><author><name>Isaac Sacolick</name><uri>https://profiles.google.com/109747073147504760416</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='32' src='//lh4.googleusercontent.com/-pgtwy5F24tA/AAAAAAAAAAI/AAAAAAAAAAA/ZfSNeF9Egr8/s512-c/photo.jpg'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-10332387.post-1807181109261567199</id><published>2008-09-07T22:27:00.003-04:00</published><updated>2008-09-07T22:52:19.334-04:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='web development'/><category scheme='http://www.blogger.com/atom/ns#' term='agile software development'/><category scheme='http://www.blogger.com/atom/ns#' term='software development'/><category scheme='http://www.blogger.com/atom/ns#' term='project management'/><title type='text'>Top 7 Ingredients to Establishing an Agile Development Practice</title><summary type='text'>More and more teams and companies are considering agile processes, SCRUM, Extreme, or hybrids to either pilot new initiatives or to establish the practice. Unfortunately, adopting agile is often sponsored by the Development Team and they can easily underestimate the organizational changes and boundaries needed for success. Below are seven key ingredients to kicking off a successful agile </summary><link rel='replies' type='application/atom+xml' href='http://ctotodevelopers.blogspot.com/feeds/1807181109261567199/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://ctotodevelopers.blogspot.com/2008/09/top-7-ingredients-to-establishing-agile.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/10332387/posts/default/1807181109261567199'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/10332387/posts/default/1807181109261567199'/><link rel='alternate' type='text/html' href='http://ctotodevelopers.blogspot.com/2008/09/top-7-ingredients-to-establishing-agile.html' title='Top 7 Ingredients to Establishing an Agile Development Practice'/><author><name>Isaac Sacolick</name><uri>https://profiles.google.com/109747073147504760416</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='32' src='//lh4.googleusercontent.com/-pgtwy5F24tA/AAAAAAAAAAI/AAAAAAAAAAA/ZfSNeF9Egr8/s512-c/photo.jpg'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-10332387.post-5035386757846326926</id><published>2008-09-01T22:01:00.003-04:00</published><updated>2008-09-01T22:18:39.866-04:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='agile software development'/><category scheme='http://www.blogger.com/atom/ns#' term='software development'/><category scheme='http://www.blogger.com/atom/ns#' term='project management'/><category scheme='http://www.blogger.com/atom/ns#' term='about me'/><title type='text'>Larger Scale Agile Development</title><summary type='text'>Back in January, we had one team at BusinessWeek practicing agile software development. The team was successful completing iterations, demoing to stakeholders, and releasing product to a growing audience.We then needed to scale. We added a second team and a third team offshore. We segmented the work so that there was minimal overlap between teams. Things got a little more complicated because we </summary><link rel='replies' type='application/atom+xml' href='http://ctotodevelopers.blogspot.com/feeds/5035386757846326926/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://ctotodevelopers.blogspot.com/2008/09/larger-scale-agile-development.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/10332387/posts/default/5035386757846326926'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/10332387/posts/default/5035386757846326926'/><link rel='alternate' type='text/html' href='http://ctotodevelopers.blogspot.com/2008/09/larger-scale-agile-development.html' title='Larger Scale Agile Development'/><author><name>Isaac Sacolick</name><uri>https://profiles.google.com/109747073147504760416</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='32' src='//lh4.googleusercontent.com/-pgtwy5F24tA/AAAAAAAAAAI/AAAAAAAAAAA/ZfSNeF9Egr8/s512-c/photo.jpg'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-10332387.post-5651624955706662974</id><published>2008-07-15T22:32:00.004-04:00</published><updated>2008-07-15T22:41:19.893-04:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='web 2.0'/><category scheme='http://www.blogger.com/atom/ns#' term='security'/><title type='text'>Good Read: Web 2.0 Security Dangers</title><summary type='text'>I'm always looking for good articles describing real security issues on Web 2.0 sites. Web 2.0: Communication, Collaboration -- and Danger is a really good read. Good quotes below if you don’t have the time to read through the article.Application layer technology can be expensive and hard to implement, however:…finds it appalling that 97 percent of organizations are still using packet filters as </summary><link rel='replies' type='application/atom+xml' href='http://ctotodevelopers.blogspot.com/feeds/5651624955706662974/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://ctotodevelopers.blogspot.com/2008/07/good-read-web-20-security-dangers.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/10332387/posts/default/5651624955706662974'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/10332387/posts/default/5651624955706662974'/><link rel='alternate' type='text/html' href='http://ctotodevelopers.blogspot.com/2008/07/good-read-web-20-security-dangers.html' title='Good Read: Web 2.0 Security Dangers'/><author><name>Isaac Sacolick</name><uri>https://profiles.google.com/109747073147504760416</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='32' src='//lh4.googleusercontent.com/-pgtwy5F24tA/AAAAAAAAAAI/AAAAAAAAAAA/ZfSNeF9Egr8/s512-c/photo.jpg'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-10332387.post-5151625221435998073</id><published>2008-06-30T23:44:00.000-04:00</published><updated>2008-06-30T23:44:25.675-04:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='web 2.0'/><category scheme='http://www.blogger.com/atom/ns#' term='agile software development'/><category scheme='http://www.blogger.com/atom/ns#' term='software development'/><category scheme='http://www.blogger.com/atom/ns#' term='project management'/><category scheme='http://www.blogger.com/atom/ns#' term='startup cto'/><title type='text'>Why Stories Work where Requirements Documents Fail</title><summary type='text'>In a traditional development practice, a product manager writes a long document describing the software requirements. Hopefully the document is diagram heavy, clear and concise. The document is handed to analysts who break the requirements down to development tasks and a project manager develops a schedule and assigns resources to tasks.In my experience, this rarely happens. In the real world, </summary><link rel='replies' type='application/atom+xml' href='http://ctotodevelopers.blogspot.com/feeds/5151625221435998073/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://ctotodevelopers.blogspot.com/2008/06/why-stories-work-where-requirements.html#comment-form' title='1 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/10332387/posts/default/5151625221435998073'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/10332387/posts/default/5151625221435998073'/><link rel='alternate' type='text/html' href='http://ctotodevelopers.blogspot.com/2008/06/why-stories-work-where-requirements.html' title='Why Stories Work where Requirements Documents Fail'/><author><name>Isaac Sacolick</name><uri>https://profiles.google.com/109747073147504760416</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='32' src='//lh4.googleusercontent.com/-pgtwy5F24tA/AAAAAAAAAAI/AAAAAAAAAAA/ZfSNeF9Egr8/s512-c/photo.jpg'/></author><thr:total>1</thr:total></entry><entry><id>tag:blogger.com,1999:blog-10332387.post-3308465477475285124</id><published>2008-06-19T22:56:00.006-04:00</published><updated>2008-06-19T23:40:40.431-04:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='agile software development'/><category scheme='http://www.blogger.com/atom/ns#' term='software development'/><category scheme='http://www.blogger.com/atom/ns#' term='project management'/><category scheme='http://www.blogger.com/atom/ns#' term='startup cto'/><title type='text'>Why Agile Product Planning Is Important</title><summary type='text'>Most agile product planning revolves around the commitment of stories to an iteration. This specifically addresses how many stories, story points, or features can be completed in an iteration. Stories are estimated in points and a team's velocity is measured as the total number of successfully completed story points in an iteration. If the velocity is consistent, the team can estimate the stories</summary><link rel='replies' type='application/atom+xml' href='http://ctotodevelopers.blogspot.com/feeds/3308465477475285124/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://ctotodevelopers.blogspot.com/2008/06/why-agile-product-planning-is-important.html#comment-form' title='2 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/10332387/posts/default/3308465477475285124'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/10332387/posts/default/3308465477475285124'/><link rel='alternate' type='text/html' href='http://ctotodevelopers.blogspot.com/2008/06/why-agile-product-planning-is-important.html' title='Why Agile Product Planning Is Important'/><author><name>Isaac Sacolick</name><uri>https://profiles.google.com/109747073147504760416</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='32' src='//lh4.googleusercontent.com/-pgtwy5F24tA/AAAAAAAAAAI/AAAAAAAAAAA/ZfSNeF9Egr8/s512-c/photo.jpg'/></author><thr:total>2</thr:total></entry><entry><id>tag:blogger.com,1999:blog-10332387.post-371130070448526004</id><published>2008-06-10T22:24:00.004-04:00</published><updated>2008-06-10T22:51:39.899-04:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='agile software development'/><category scheme='http://www.blogger.com/atom/ns#' term='software development'/><category scheme='http://www.blogger.com/atom/ns#' term='project management'/><category scheme='http://www.blogger.com/atom/ns#' term='startup cto'/><title type='text'>Agile in the Enterprise: Big Questions Enterprises Should Consider When Going Agile</title><summary type='text'>When a CIO, development manager, or a team decides to 'go agile', what does this mean for other colleagues that work with this team? What does it mean to Product Managers that are responsible for developing business cases and delivering product requirements? What happens if there are technical teams that are on the periphery of the core software development group such as QA teams, operations, </summary><link rel='replies' type='application/atom+xml' href='http://ctotodevelopers.blogspot.com/feeds/371130070448526004/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://ctotodevelopers.blogspot.com/2008/06/agile-in-enterprise-big-questions.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/10332387/posts/default/371130070448526004'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/10332387/posts/default/371130070448526004'/><link rel='alternate' type='text/html' href='http://ctotodevelopers.blogspot.com/2008/06/agile-in-enterprise-big-questions.html' title='Agile in the Enterprise: Big Questions Enterprises Should Consider When Going Agile'/><author><name>Isaac Sacolick</name><uri>https://profiles.google.com/109747073147504760416</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='32' src='//lh4.googleusercontent.com/-pgtwy5F24tA/AAAAAAAAAAI/AAAAAAAAAAA/ZfSNeF9Egr8/s512-c/photo.jpg'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-10332387.post-8550281022630463354</id><published>2008-05-05T22:44:00.004-04:00</published><updated>2008-05-05T23:03:39.673-04:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='agile software development'/><category scheme='http://www.blogger.com/atom/ns#' term='software development'/><category scheme='http://www.blogger.com/atom/ns#' term='project management'/><title type='text'>The ScrumMaster - A role or responsibility?</title><summary type='text'>At a recent industry event for publishers, I sat at a table with a number of agile development leaders and we discussed the ScrumMaster role. Do you have a dedicated ScrumMaster? For the most part, the answer came back as a ‘no’ for a number of philosophical and funding reasons.    Agile practitioners love to talk about roles and responsibilities. You need a product owner, largely responsible for</summary><link rel='replies' type='application/atom+xml' href='http://ctotodevelopers.blogspot.com/feeds/8550281022630463354/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://ctotodevelopers.blogspot.com/2008/05/scrummaster-role-or-responsibility.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/10332387/posts/default/8550281022630463354'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/10332387/posts/default/8550281022630463354'/><link rel='alternate' type='text/html' href='http://ctotodevelopers.blogspot.com/2008/05/scrummaster-role-or-responsibility.html' title='The ScrumMaster - A role or responsibility?'/><author><name>Isaac Sacolick</name><uri>https://profiles.google.com/109747073147504760416</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='32' src='//lh4.googleusercontent.com/-pgtwy5F24tA/AAAAAAAAAAI/AAAAAAAAAAA/ZfSNeF9Egr8/s512-c/photo.jpg'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-10332387.post-6181147931068967799</id><published>2008-04-18T22:45:00.004-04:00</published><updated>2008-04-18T23:16:22.583-04:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='web development'/><category scheme='http://www.blogger.com/atom/ns#' term='agile software development'/><category scheme='http://www.blogger.com/atom/ns#' term='software development'/><category scheme='http://www.blogger.com/atom/ns#' term='pair progrmming'/><title type='text'>When to use Pair Programming</title><summary type='text'>Several years ago right about when Extreme Programming (XP) became popular, one of the developers on a team I was managing wanted to give pair programming a try. He paired up with another programmer and went to work on some of our more complicated algorithms. I can't tell you today whether that pair produced better quality code or if they were more productive, but they certainly felt proud of </summary><link rel='replies' type='application/atom+xml' href='http://ctotodevelopers.blogspot.com/feeds/6181147931068967799/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://ctotodevelopers.blogspot.com/2008/04/when-to-use-pair-programming.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/10332387/posts/default/6181147931068967799'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/10332387/posts/default/6181147931068967799'/><link rel='alternate' type='text/html' href='http://ctotodevelopers.blogspot.com/2008/04/when-to-use-pair-programming.html' title='When to use Pair Programming'/><author><name>Isaac Sacolick</name><uri>https://profiles.google.com/109747073147504760416</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='32' src='//lh4.googleusercontent.com/-pgtwy5F24tA/AAAAAAAAAAI/AAAAAAAAAAA/ZfSNeF9Egr8/s512-c/photo.jpg'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-10332387.post-1491950910661771489</id><published>2008-02-16T08:58:00.002-05:00</published><updated>2008-02-16T09:25:05.768-05:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='software qa'/><category scheme='http://www.blogger.com/atom/ns#' term='software development'/><category scheme='http://www.blogger.com/atom/ns#' term='project management'/><title type='text'>Implementing Agile Load Testing</title><summary type='text'>Someone recently asked me, "How do you implement load testing so early in the development process"? I thought about the question for a second before coming up with the following answer:1) Don't just say you're going to load test, do it - If you're a team lead, manager, or qa engineer it's easy to make excuses why you can't start testing early in the development process. But there are always some </summary><link rel='replies' type='application/atom+xml' href='http://ctotodevelopers.blogspot.com/feeds/1491950910661771489/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://ctotodevelopers.blogspot.com/2008/02/implementing-agile-load-testing.html#comment-form' title='2 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/10332387/posts/default/1491950910661771489'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/10332387/posts/default/1491950910661771489'/><link rel='alternate' type='text/html' href='http://ctotodevelopers.blogspot.com/2008/02/implementing-agile-load-testing.html' title='Implementing Agile Load Testing'/><author><name>Isaac Sacolick</name><uri>https://profiles.google.com/109747073147504760416</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='32' src='//lh4.googleusercontent.com/-pgtwy5F24tA/AAAAAAAAAAI/AAAAAAAAAAA/ZfSNeF9Egr8/s512-c/photo.jpg'/></author><thr:total>2</thr:total></entry><entry><id>tag:blogger.com,1999:blog-10332387.post-4973280529804775464</id><published>2008-02-07T21:00:00.000-05:00</published><updated>2008-02-07T21:40:05.753-05:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='software qa'/><category scheme='http://www.blogger.com/atom/ns#' term='sandisk'/><category scheme='http://www.blogger.com/atom/ns#' term='customer service'/><category scheme='http://www.blogger.com/atom/ns#' term='rhapsody'/><title type='text'>Yikes! Defects, Bad Docs -&gt; Customer Frustration</title><summary type='text'>I recently purchased a Sandisk e250 so that I can take advantage of Rhapsody On The Go's music subscription service. I opened the device and plugged it into my USB port thinking that I needed to charge up the device before I could use it. Unfortunately, my system churned and produced an error message "unrecognized device". With very little troubleshooting help, I was forced to call Sandisk for </summary><link rel='replies' type='application/atom+xml' href='http://ctotodevelopers.blogspot.com/feeds/4973280529804775464/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://ctotodevelopers.blogspot.com/2008/02/yikes-defects-bad-docs-customer.html#comment-form' title='4 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/10332387/posts/default/4973280529804775464'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/10332387/posts/default/4973280529804775464'/><link rel='alternate' type='text/html' href='http://ctotodevelopers.blogspot.com/2008/02/yikes-defects-bad-docs-customer.html' title='Yikes! Defects, Bad Docs -&gt; Customer Frustration'/><author><name>Isaac Sacolick</name><uri>https://profiles.google.com/109747073147504760416</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='32' src='//lh4.googleusercontent.com/-pgtwy5F24tA/AAAAAAAAAAI/AAAAAAAAAAA/ZfSNeF9Egr8/s512-c/photo.jpg'/></author><thr:total>4</thr:total></entry><entry><id>tag:blogger.com,1999:blog-10332387.post-8539889119386883114</id><published>2008-02-01T23:17:00.000-05:00</published><updated>2008-02-01T23:51:26.330-05:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='software qa'/><category scheme='http://www.blogger.com/atom/ns#' term='web development'/><category scheme='http://www.blogger.com/atom/ns#' term='software development'/><title type='text'>The First Load Test Always Fails</title><summary type='text'>Here is a typical, very simplified load testing scenario:The tester defines one or more workflows through the application and simulates them in a tool. The tool allows setting the number of virtual users, the delay between clicks, and other parameters that determine how much load to generate. The tester determines an appropriate load based on the website's metrics or projected metrics. She then </summary><link rel='replies' type='application/atom+xml' href='http://ctotodevelopers.blogspot.com/feeds/8539889119386883114/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://ctotodevelopers.blogspot.com/2008/02/first-load-test-always-fails.html#comment-form' title='1 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/10332387/posts/default/8539889119386883114'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/10332387/posts/default/8539889119386883114'/><link rel='alternate' type='text/html' href='http://ctotodevelopers.blogspot.com/2008/02/first-load-test-always-fails.html' title='The First Load Test Always Fails'/><author><name>Isaac Sacolick</name><uri>https://profiles.google.com/109747073147504760416</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='32' src='//lh4.googleusercontent.com/-pgtwy5F24tA/AAAAAAAAAAI/AAAAAAAAAAA/ZfSNeF9Egr8/s512-c/photo.jpg'/></author><thr:total>1</thr:total></entry><entry><id>tag:blogger.com,1999:blog-10332387.post-6658077060923214552</id><published>2007-10-15T21:59:00.000-04:00</published><updated>2007-10-15T22:15:26.976-04:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='web development'/><category scheme='http://www.blogger.com/atom/ns#' term='software development'/><category scheme='http://www.blogger.com/atom/ns#' term='standards'/><title type='text'>Is FreeMarker Another Velocity? Or Just Use JSP?</title><summary type='text'>My team is  currently exploring Freemarker as a web view and template language. "Jsp is overkill for what we need", "no code snippets in view code", "it supports tag libraries", "the macros are powerful" were all listed as top benefits. In addition, there is some interest in developing tests that validate the output of views.I'm scratching my head on this one. Another template language? I used </summary><link rel='replies' type='application/atom+xml' href='http://ctotodevelopers.blogspot.com/feeds/6658077060923214552/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://ctotodevelopers.blogspot.com/2007/10/is-freemarker-another-velocity-or-just.html#comment-form' title='3 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/10332387/posts/default/6658077060923214552'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/10332387/posts/default/6658077060923214552'/><link rel='alternate' type='text/html' href='http://ctotodevelopers.blogspot.com/2007/10/is-freemarker-another-velocity-or-just.html' title='Is FreeMarker Another Velocity? Or Just Use JSP?'/><author><name>Isaac Sacolick</name><uri>https://profiles.google.com/109747073147504760416</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='32' src='//lh4.googleusercontent.com/-pgtwy5F24tA/AAAAAAAAAAI/AAAAAAAAAAA/ZfSNeF9Egr8/s512-c/photo.jpg'/></author><thr:total>3</thr:total></entry><entry><id>tag:blogger.com,1999:blog-10332387.post-7854463878958685641</id><published>2007-09-30T09:09:00.001-04:00</published><updated>2007-10-01T22:38:20.061-04:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='software qa'/><category scheme='http://www.blogger.com/atom/ns#' term='software development'/><category scheme='http://www.blogger.com/atom/ns#' term='startup cto'/><title type='text'>Automatic or Nightly Builds? When, Why, and Why Not</title><summary type='text'>I've had two different development teams over the past couple of months try to convince me that implementing either nightly or automatic software builds is critical. Now I've been a part of many software development teams and none of them employed any of these builds. This includes a  shrink wrap software package company that had a half dozen products built from a very large common code base and </summary><link rel='replies' type='application/atom+xml' href='http://ctotodevelopers.blogspot.com/feeds/7854463878958685641/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://ctotodevelopers.blogspot.com/2007/09/automatic-or-nightly-builds-when-why.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/10332387/posts/default/7854463878958685641'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/10332387/posts/default/7854463878958685641'/><link rel='alternate' type='text/html' href='http://ctotodevelopers.blogspot.com/2007/09/automatic-or-nightly-builds-when-why.html' title='Automatic or Nightly Builds? When, Why, and Why Not'/><author><name>Isaac Sacolick</name><uri>https://profiles.google.com/109747073147504760416</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='32' src='//lh4.googleusercontent.com/-pgtwy5F24tA/AAAAAAAAAAI/AAAAAAAAAAA/ZfSNeF9Egr8/s512-c/photo.jpg'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-10332387.post-8554154217821142197</id><published>2007-09-05T23:24:00.000-04:00</published><updated>2007-09-05T23:57:11.151-04:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='software development'/><category scheme='http://www.blogger.com/atom/ns#' term='project management'/><category scheme='http://www.blogger.com/atom/ns#' term='startup cto'/><title type='text'>Top 10 Tips On Version Control for Small Agile Software Teams</title><summary type='text'>Version control is a fundamental software management tool and process. If you're looking to setup a development environment for a startup, I highly recommend getting version control in place as a step 0. Even startups that have very few developers (even one!) will find long term benefits in having version control configured before development begins. In more established development teams, </summary><link rel='replies' type='application/atom+xml' href='http://ctotodevelopers.blogspot.com/feeds/8554154217821142197/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://ctotodevelopers.blogspot.com/2007/09/top-10-tips-on-version-control-for.html#comment-form' title='5 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/10332387/posts/default/8554154217821142197'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/10332387/posts/default/8554154217821142197'/><link rel='alternate' type='text/html' href='http://ctotodevelopers.blogspot.com/2007/09/top-10-tips-on-version-control-for.html' title='Top 10 Tips On Version Control for Small Agile Software Teams'/><author><name>Isaac Sacolick</name><uri>https://profiles.google.com/109747073147504760416</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='32' src='//lh4.googleusercontent.com/-pgtwy5F24tA/AAAAAAAAAAI/AAAAAAAAAAA/ZfSNeF9Egr8/s512-c/photo.jpg'/></author><thr:total>5</thr:total></entry><entry><id>tag:blogger.com,1999:blog-10332387.post-8804388749667506212</id><published>2007-07-29T00:04:00.001-04:00</published><updated>2007-07-30T23:55:01.662-04:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='java'/><category scheme='http://www.blogger.com/atom/ns#' term='web 2.0'/><category scheme='http://www.blogger.com/atom/ns#' term='software development'/><category scheme='http://www.blogger.com/atom/ns#' term='startup cto'/><title type='text'>For Startups, My Two Cents on Programming Languages</title><summary type='text'>Php, Perl, Ruby, Java, or .Net. Many startups kickoff with one or two engineers and will often pick 'the best' technology stack, or just the one that they want to work on. The latest greatest framework.It's my blog, so I get to be biased. I've seen about two dozen different startup environments. Not a huge number, but not a small number either. So my opinions are largely based on what I've seen </summary><link rel='replies' type='application/atom+xml' href='http://ctotodevelopers.blogspot.com/feeds/8804388749667506212/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://ctotodevelopers.blogspot.com/2007/07/for-startups-my-two-cents-on.html#comment-form' title='1 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/10332387/posts/default/8804388749667506212'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/10332387/posts/default/8804388749667506212'/><link rel='alternate' type='text/html' href='http://ctotodevelopers.blogspot.com/2007/07/for-startups-my-two-cents-on.html' title='For Startups, My Two Cents on Programming Languages'/><author><name>Isaac Sacolick</name><uri>https://profiles.google.com/109747073147504760416</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='32' src='//lh4.googleusercontent.com/-pgtwy5F24tA/AAAAAAAAAAI/AAAAAAAAAAA/ZfSNeF9Egr8/s512-c/photo.jpg'/></author><thr:total>1</thr:total></entry><entry><id>tag:blogger.com,1999:blog-10332387.post-5895165055497974538</id><published>2007-07-09T11:27:00.000-04:00</published><updated>2007-07-09T14:54:37.709-04:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='web 2.0'/><category scheme='http://www.blogger.com/atom/ns#' term='software development'/><category scheme='http://www.blogger.com/atom/ns#' term='project management'/><category scheme='http://www.blogger.com/atom/ns#' term='it management'/><category scheme='http://www.blogger.com/atom/ns#' term='startup cto'/><title type='text'>Choosing A Development Platform For Your Startup</title><summary type='text'>Are you a Linux guy or Windows? Java, .Net, or LAMP? Or are you a Ruby gal?These questions dominate the early discussions in a startup's technology. Yes, this is a very important question because once you start investing in a development platform it becomes costly and complex to switch or even upgrade. So for a startup, choosing the development technologies is pretty much a permanent decision </summary><link rel='replies' type='application/atom+xml' href='http://ctotodevelopers.blogspot.com/feeds/5895165055497974538/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://ctotodevelopers.blogspot.com/2007/07/choosing-development-platform-for-your.html#comment-form' title='1 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/10332387/posts/default/5895165055497974538'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/10332387/posts/default/5895165055497974538'/><link rel='alternate' type='text/html' href='http://ctotodevelopers.blogspot.com/2007/07/choosing-development-platform-for-your.html' title='Choosing A Development Platform For Your Startup'/><author><name>Isaac Sacolick</name><uri>https://profiles.google.com/109747073147504760416</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='32' src='//lh4.googleusercontent.com/-pgtwy5F24tA/AAAAAAAAAAI/AAAAAAAAAAA/ZfSNeF9Egr8/s512-c/photo.jpg'/></author><thr:total>1</thr:total></entry><entry><id>tag:blogger.com,1999:blog-10332387.post-58132601727087337</id><published>2007-06-25T11:32:00.000-04:00</published><updated>2007-06-25T12:29:43.279-04:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='web 2.0'/><category scheme='http://www.blogger.com/atom/ns#' term='in the news'/><category scheme='http://www.blogger.com/atom/ns#' term='it management'/><title type='text'>Is Open Source Dying?</title><summary type='text'>Eweek has a  great title, Is Open Source Dying? that's sure to get lots of people clicking. But the article's title should really read Is Open Source Hard To Implement For Government Institutions? They are the only examples provided in this article of organizations having trouble implementing open source.I expect that large organizations will continue to have trouble implementing open source </summary><link rel='replies' type='application/atom+xml' href='http://ctotodevelopers.blogspot.com/feeds/58132601727087337/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://ctotodevelopers.blogspot.com/2007/06/is-open-source-dying.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/10332387/posts/default/58132601727087337'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/10332387/posts/default/58132601727087337'/><link rel='alternate' type='text/html' href='http://ctotodevelopers.blogspot.com/2007/06/is-open-source-dying.html' title='Is Open Source Dying?'/><author><name>Isaac Sacolick</name><uri>https://profiles.google.com/109747073147504760416</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='32' src='//lh4.googleusercontent.com/-pgtwy5F24tA/AAAAAAAAAAI/AAAAAAAAAAA/ZfSNeF9Egr8/s512-c/photo.jpg'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-10332387.post-4335037414400965784</id><published>2007-06-07T08:05:00.000-04:00</published><updated>2007-10-16T22:25:16.228-04:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='web development'/><category scheme='http://www.blogger.com/atom/ns#' term='web 2.0'/><category scheme='http://www.blogger.com/atom/ns#' term='software development'/><category scheme='http://www.blogger.com/atom/ns#' term='facebook'/><title type='text'>5 Development Tips for the Facebook API</title><summary type='text'>Below are five tips on using Facebook's API. These techniques were all used in TripConnect's Travel Profile Application that allows Facebook users to add a travel interests to their Facebook profile. I know they work in this app, but they may not be the perfect solutions.The first two tips are specific to the JAVA kit. The others are more general.1) Installation - I saw several posts in the </summary><link rel='replies' type='application/atom+xml' href='http://ctotodevelopers.blogspot.com/feeds/4335037414400965784/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://ctotodevelopers.blogspot.com/2007/06/5-development-tips-for-facebook-api.html#comment-form' title='16 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/10332387/posts/default/4335037414400965784'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/10332387/posts/default/4335037414400965784'/><link rel='alternate' type='text/html' href='http://ctotodevelopers.blogspot.com/2007/06/5-development-tips-for-facebook-api.html' title='5 Development Tips for the Facebook API'/><author><name>Isaac Sacolick</name><uri>https://profiles.google.com/109747073147504760416</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='32' src='//lh4.googleusercontent.com/-pgtwy5F24tA/AAAAAAAAAAI/AAAAAAAAAAA/ZfSNeF9Egr8/s512-c/photo.jpg'/></author><thr:total>16</thr:total></entry><entry><id>tag:blogger.com,1999:blog-10332387.post-1142303790224034010</id><published>2007-06-05T08:59:00.001-04:00</published><updated>2008-11-13T02:00:58.809-05:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='web 2.0'/><category scheme='http://www.blogger.com/atom/ns#' term='software development'/><category scheme='http://www.blogger.com/atom/ns#' term='facebook'/><category scheme='http://www.blogger.com/atom/ns#' term='in the news'/><title type='text'>Review of the Facebook API for Developers</title><summary type='text'>On May 24, Facebook officially released its Developer API.  It's probably one of the first (and definitely one of the biggest communities) to open a social network up to the development community. It's also a sharp contrast to MySpace's tactics in blocking widgets (See: MySpace security measure disables viral spread of widgets).At first, I thought it was just a proprietary widget API. In fact, </summary><link rel='replies' type='application/atom+xml' href='http://ctotodevelopers.blogspot.com/feeds/1142303790224034010/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://ctotodevelopers.blogspot.com/2007/06/review-of-facebook-api-for-developers.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/10332387/posts/default/1142303790224034010'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/10332387/posts/default/1142303790224034010'/><link rel='alternate' type='text/html' href='http://ctotodevelopers.blogspot.com/2007/06/review-of-facebook-api-for-developers.html' title='Review of the Facebook API for Developers'/><author><name>Isaac Sacolick</name><uri>https://profiles.google.com/109747073147504760416</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='32' src='//lh4.googleusercontent.com/-pgtwy5F24tA/AAAAAAAAAAI/AAAAAAAAAAA/ZfSNeF9Egr8/s512-c/photo.jpg'/></author><media:thumbnail xmlns:media='http://search.yahoo.com/mrss/' url='http://1.bp.blogspot.com/_y1jpflueSAA/RmVq73silQI/AAAAAAAAAAU/-TPbpscQdkU/s72-c/fb+tripconnect+screen+shot.JPG' height='72' width='72'/><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-10332387.post-4144873083415580272</id><published>2007-05-22T08:37:00.000-04:00</published><updated>2007-05-22T09:39:01.527-04:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='business plans'/><category scheme='http://www.blogger.com/atom/ns#' term='software development'/><category scheme='http://www.blogger.com/atom/ns#' term='project management'/><category scheme='http://www.blogger.com/atom/ns#' term='startup cto'/><title type='text'>Feasibility? Picking Features For Your Alpha Release</title><summary type='text'>In my last post, I provided some tools to help estimate the overhead in software development. The basic formula goes like this:The business plan should project a budget and desired time line for the alpha release.Subtract out some fixed costs for hardware, software systems, databases and components.Subtract out ramp up time needed to complete the software requirements, hire the development team, </summary><link rel='replies' type='application/atom+xml' href='http://ctotodevelopers.blogspot.com/feeds/4144873083415580272/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://ctotodevelopers.blogspot.com/2007/05/feasibility-picking-features-for-your.html#comment-form' title='1 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/10332387/posts/default/4144873083415580272'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/10332387/posts/default/4144873083415580272'/><link rel='alternate' type='text/html' href='http://ctotodevelopers.blogspot.com/2007/05/feasibility-picking-features-for-your.html' title='Feasibility? Picking Features For Your Alpha Release'/><author><name>Isaac Sacolick</name><uri>https://profiles.google.com/109747073147504760416</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='32' src='//lh4.googleusercontent.com/-pgtwy5F24tA/AAAAAAAAAAI/AAAAAAAAAAA/ZfSNeF9Egr8/s512-c/photo.jpg'/></author><thr:total>1</thr:total></entry><entry><id>tag:blogger.com,1999:blog-10332387.post-5807323112476991804</id><published>2007-05-07T09:17:00.000-04:00</published><updated>2007-05-07T22:53:11.047-04:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='software development'/><category scheme='http://www.blogger.com/atom/ns#' term='project management'/><category scheme='http://www.blogger.com/atom/ns#' term='startup cto'/><title type='text'>Fixed Cost Software Project Management for Startups</title><summary type='text'>In my last post, I suggested that startups plan their alpha release as a fixed cost software project. The budget is somewhat easy to work out off the business plan. You basically need to answer to fundamental questions: When does the product need to launch and how much can you afford to spend on your initial product?With those two variables as fixed, you now have to consider several scenarios to </summary><link rel='replies' type='application/atom+xml' href='http://ctotodevelopers.blogspot.com/feeds/5807323112476991804/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://ctotodevelopers.blogspot.com/2007/05/fixed-cost-software-project-management.html#comment-form' title='1 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/10332387/posts/default/5807323112476991804'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/10332387/posts/default/5807323112476991804'/><link rel='alternate' type='text/html' href='http://ctotodevelopers.blogspot.com/2007/05/fixed-cost-software-project-management.html' title='Fixed Cost Software Project Management for Startups'/><author><name>Isaac Sacolick</name><uri>https://profiles.google.com/109747073147504760416</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='32' src='//lh4.googleusercontent.com/-pgtwy5F24tA/AAAAAAAAAAI/AAAAAAAAAAA/ZfSNeF9Egr8/s512-c/photo.jpg'/></author><thr:total>1</thr:total></entry><entry><id>tag:blogger.com,1999:blog-10332387.post-2805721034968795303</id><published>2007-04-24T18:53:00.000-04:00</published><updated>2007-04-24T19:08:45.030-04:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='software development'/><category scheme='http://www.blogger.com/atom/ns#' term='project management'/><category scheme='http://www.blogger.com/atom/ns#' term='startup cto'/><title type='text'>Startup CTO – Fixed Cost Project Estimation</title><summary type='text'>In my last entry, I discussed the basics of software project estimation and some simplifications that may exist in a startup. But the underlying point of the entry was to illustrate why estimating the development time on a startup’s alpha product release can be flawed. The bottom line is, estimates require detailed requirements, managed scope changes, and accurate effort estimations – things that</summary><link rel='replies' type='application/atom+xml' href='http://ctotodevelopers.blogspot.com/feeds/2805721034968795303/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://ctotodevelopers.blogspot.com/2007/04/startup-cto-fixed-cost-project.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/10332387/posts/default/2805721034968795303'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/10332387/posts/default/2805721034968795303'/><link rel='alternate' type='text/html' href='http://ctotodevelopers.blogspot.com/2007/04/startup-cto-fixed-cost-project.html' title='Startup CTO – Fixed Cost Project Estimation'/><author><name>Isaac Sacolick</name><uri>https://profiles.google.com/109747073147504760416</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='32' src='//lh4.googleusercontent.com/-pgtwy5F24tA/AAAAAAAAAAI/AAAAAAAAAAA/ZfSNeF9Egr8/s512-c/photo.jpg'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-10332387.post-5042054574785067752</id><published>2007-04-10T12:35:00.000-04:00</published><updated>2007-04-10T16:23:47.029-04:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='crisis management'/><category scheme='http://www.blogger.com/atom/ns#' term='in the news'/><category scheme='http://www.blogger.com/atom/ns#' term='jetblue'/><title type='text'>JetBlue Postmortem - What Went Wrong</title><summary type='text'>From  What Really Happened At JetBlue"While most other airlines cancelled dozens of flights in preparation for the storm, JetBlue management opted to wait it out. The airline's policy is do to whatever it can to ensure a flight is completed, even if it means waiting for several hours""[passengers] had only one option to rebook their flights: call the JetBlue reservation office. The Navitaire </summary><link rel='replies' type='application/atom+xml' href='http://ctotodevelopers.blogspot.com/feeds/5042054574785067752/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://ctotodevelopers.blogspot.com/2007/04/jetblue-postmortem-what-went-wrong.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/10332387/posts/default/5042054574785067752'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/10332387/posts/default/5042054574785067752'/><link rel='alternate' type='text/html' href='http://ctotodevelopers.blogspot.com/2007/04/jetblue-postmortem-what-went-wrong.html' title='JetBlue Postmortem - What Went Wrong'/><author><name>Isaac Sacolick</name><uri>https://profiles.google.com/109747073147504760416</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='32' src='//lh4.googleusercontent.com/-pgtwy5F24tA/AAAAAAAAAAI/AAAAAAAAAAA/ZfSNeF9Egr8/s512-c/photo.jpg'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-10332387.post-3339534423009204902</id><published>2007-04-09T15:32:00.000-04:00</published><updated>2007-04-09T15:37:33.783-04:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='business plans'/><category scheme='http://www.blogger.com/atom/ns#' term='software development'/><category scheme='http://www.blogger.com/atom/ns#' term='project management'/><category scheme='http://www.blogger.com/atom/ns#' term='startup cto'/><title type='text'>StartUp CTO - Estimating the Product Deliverable Timeline and Cost</title><summary type='text'>In my last StartUp CTO post, I talked about the need to build an initial development plan. To start, I suggested a very simplified framework whereby screens and functional components are itemized. In the best of situations, the features are given some type of priority. Sometimes that is done using versions (this feature can wait till version X), Must/Should/Could categorizations, or some </summary><link rel='replies' type='application/atom+xml' href='http://ctotodevelopers.blogspot.com/feeds/3339534423009204902/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://ctotodevelopers.blogspot.com/2007/04/startup-cto-estimating-product.html#comment-form' title='1 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/10332387/posts/default/3339534423009204902'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/10332387/posts/default/3339534423009204902'/><link rel='alternate' type='text/html' href='http://ctotodevelopers.blogspot.com/2007/04/startup-cto-estimating-product.html' title='StartUp CTO - Estimating the Product Deliverable Timeline and Cost'/><author><name>Isaac Sacolick</name><uri>https://profiles.google.com/109747073147504760416</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='32' src='//lh4.googleusercontent.com/-pgtwy5F24tA/AAAAAAAAAAI/AAAAAAAAAAA/ZfSNeF9Egr8/s512-c/photo.jpg'/></author><thr:total>1</thr:total></entry><entry><id>tag:blogger.com,1999:blog-10332387.post-963912313373955624</id><published>2007-04-03T13:40:00.000-04:00</published><updated>2007-04-03T15:59:54.021-04:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='software qa'/><category scheme='http://www.blogger.com/atom/ns#' term='software development'/><category scheme='http://www.blogger.com/atom/ns#' term='project management'/><title type='text'>Software Requirements Gone Bad</title><summary type='text'>Here’s an example illustrating how bad software requirements can lead to unexpected results.I was searching the web for a simple algorithm. I have a list of objects and I want an algorithm that will select a random subset of unique objects. No dupes. In my search, I found a forum post with this similar question:      &gt; how do i write a java program that prints a list of 4&gt; sets of numbers each </summary><link rel='replies' type='application/atom+xml' href='http://ctotodevelopers.blogspot.com/feeds/963912313373955624/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://ctotodevelopers.blogspot.com/2007/04/software-requirements-gone-bad.html#comment-form' title='1 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/10332387/posts/default/963912313373955624'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/10332387/posts/default/963912313373955624'/><link rel='alternate' type='text/html' href='http://ctotodevelopers.blogspot.com/2007/04/software-requirements-gone-bad.html' title='Software Requirements Gone Bad'/><author><name>Isaac Sacolick</name><uri>https://profiles.google.com/109747073147504760416</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='32' src='//lh4.googleusercontent.com/-pgtwy5F24tA/AAAAAAAAAAI/AAAAAAAAAAA/ZfSNeF9Egr8/s512-c/photo.jpg'/></author><thr:total>1</thr:total></entry></feed>
