From Softjourn’s CEO

The quick answer is of course yes! Without really thinking about it we can answer this way because anything is possible, you just have to determine if it makes economic or strategic sense to do it.

Over the next few weeks I want to explore this question further, but before I get in to that I want to pose another question regarding Agile.

According to the Agile Manifesto:  Welcome changing requirements, even late in development. Agile processes harness change for the customer’s competitive advantage.

So to me this brings up a couple of questions:

1. Taking this principle in to account, are you still considered to be doing “Agile” development if right before the iteration is due new changes are requested thus pushing back the release date again? If you only release to production once every 6 or so months can you still be doing Agile development?

2. In that same vein, if you request to put off a change request until the next iteration, are you being “un-Agile”?

Short article from CIO.com, “IT Director Pleads Guilty to Deleting Organ Donation Records”, is another reminder that it doesn’t matter where the IT person is located, they could be located in your office, down the street or at the other side of the world, and still be capable of doing something to your data.  Need to have a process in place, especially when terminating someone to shut down all access, but as well to periodically monitor for all access points for “unusual” activity.