Baby Steps to SOA – Step Six: Data Services

Service-oriented ArchitectureIn the continuing Baby Steps to SOA series, we follow Doug and the IT team behind BuyMyWidget.com as they take steps to renovate their digital asset architecture. Previously, we introduced the problem and the team, started planning and analysis, decided on some metrics, and refactored the website applications. Most recently, the team has tackled identity management, introducing a CMS, and now continues with the migration of the data layer into web services.

Continue reading “Baby Steps to SOA – Step Six: Data Services”

Microsoft completes acquisition of InRelease software

TFSWhile I was at the ALM Summit in January, Claude from InCycle (now with Microsoft) was doing demos of their InRelease software.  The deployment software allowed for a massive amount of deployment configuration, moving a build between labs and retaining environment-specific configurations using a tokenized language.  The workflow definition for how the build should flow from environment to environment also allowed for accepting or rejecting the build.

I was impressed at the time, and obviously Microsoft was as well, since they started the process for acquiring the product a few months ago.  As of July 10th, the acquisition is official.

This means InRelease will soon become a full part of Visual Studio and Team Foundation Server 2013.  The preview download is available from the InCycle website.

Media:

Baby Steps to SOA – Step Five: The Move to a CMS

Service-oriented ArchitectureIn the continuing Baby Steps to SOA series, we follow Doug and the IT team behind BuyMyWidget.com as they take steps to renovate their digital asset architecture. Previously, we introduced the problem and the team, started planning and analysis, decided on some metrics, and refactored the website applications. Most recently, the team has tackled identity management, and now continues with introducing a CMS into their architecture.

Continue reading “Baby Steps to SOA – Step Five: The Move to a CMS”

Sprint Discipline: Releasing each iteration

My Thoughts:

The above is a recent post by Scott Knight on the Scott’s Thoughts blog which introduces the benefits of continuous deployment, and how we can improve our practice with the simple switch of doing real releases after each iteration. I think this post provided a great overview on the impact to Dev, Test, and PM in the process.

Really, a lot of the things mentioned by Scott are things we should be doing anyways, even if we aren’t doing a “real” release, but the fact that our code will actually go to the customer seems to make us do them more rigourously.

I would add that the DevOps team is impacted by this change as well, as deployments and updates to training/help documentation also need to occur with every release. Additionally, your support teams are usually impacted as new features are now needing to be supported by them every few weeks.

Scott's Thoughts

One of the things that I always hear about agile development and scrum in particular is the idea of creating a releasable piece of software at the end of every sprint. This is usually redefined into “a potentially releasable piece of software” at the end of each sprint. It tends to be a little more grey than that, some sprints produce a deliverable that is more potentially releasable than others so there are an infinite number of levels of potential between actually releasable and only hypothetically releasable.  Almost all of the scrum teams that I have worked with over the last 15 years have all been on the “potentially releasable” and of that spectrum.

There’s a huge difference between “potentially releasable” and “releasable”; it’s the difference between having gotten a speeding ticket and actually being a race car driver. As an experiment, the team that I am currently the scrum master for…

View original post 794 more words

Baby Steps to SoA – Step Four: Single Sign-On

Service-oriented ArchitectureIn the continuing Baby Steps to SOA series, we follow Doug and his IT team behind BuyMyWidget.com as they take steps to renovate their digital asset architecture. Previously, we introduced the problem and the team, started planning and analysis, decided on some metrics, refactored the website applications, and now we continue on our travel through the road map with tackling identity management!

Continue reading “Baby Steps to SoA – Step Four: Single Sign-On”