Release Management is a serious business, no doubt! You can have the best development processes in place to build robust applications or you may have bug-free n-tier changes signed off and ready for roll-out, and yet if something goes wrong during the roll out process, critical systems may end up malfunctioning or worse, stay down for extending periods of time because of lengthy roll back procedures with potential consequences to the profitability and reputation.
Therefore, mechanisms that enable the seamless integration of development work into shippable builds that are also stored into a persistent area for quick roll back, are becoming increasingly critical for Release Managers. In this article, we will take a look in Maven one of the most popular tools that serves this process, as well as Archiva, a local repository for storing builds and their corresponding source code.
In a previous article I have given an introduction to Scrum. There, we have seen some principles of this Agile framework, pretty much a taster of what it is. In this article we will take a closer look at what it looks like when put into practice through a case study. Ready ? Let’s scrum !
As a Development Manager you have often dealt with challenging business or purely technical solutions that you want to lead your team to implement. Sure, you have always come up with a strategy but sometimes upon reviewing the result, you may have realised that the algorithm approach was inappropriate in terms of scalability. And it may be too late if you find out during UAT or worse, after some months in production.
Ideally you want to capture such an issue early in the design phase but how do you assess an abstract application (aka technical design)? The answer comes from one of the fundamental topics of Computer Science, Algorithm Complexity, In this article I will cover some of the principal concepts of this subject that may serve as a refresher for some or a good intro for others.
Complexity is of particular interest in virtual reality
It’s a recurring question: Is the Scrum Master role the equivalent of the Project Manager. In this article I want to clear up the landscape on this issue by approaching the subject from the perspective of the responsibilities that each one has in the broader picture of managing a project.
OK, I have to admit it. When it comes to project methodologies I have a special place in my heart for PRINCE2. PRojects IN Controlled Environment, as its full name goes, fascinates me because it combines the structured approach to managing projects with the flexibility usually found in Agile methodologies. In this article I will present a few key points about this method and I will focus on how project managers can benefit from it by adapting it to their project needs.
Here’s some interesting news. PMI, is going Agile. Yes you heard that right. According to their recent announcement (http://www.pmi.org/Agile.aspx) PMI acknowledges that “Agile is a topic of growing importance in project management (and) the marketplace shows this trend, as project management practitioners embrace Agile as a technique for managing successful projects”. So as they mention in their announcement “Because of these changes in the project management environment, PMI is developing an Agile certification”. At the same time there have been initiatives to introduce Agility to PRINCE2 as well
Agile methodologies are gaining ground in IT project management as they are recognised for their ability to accelerate the completion of projects while giving the flexibility to accomodate easily changes in the final product requirements virtually at any time during implementation.
One of the most popular member of this class is Scrum and in this first article I present the principles that govern its main features. In subsequent articles we will see some more specialized topics.
I would like to kick off this blog by giving an overview of what does a Development Manager
There are a number of ways to approach this subject but all revolve around the same core themes, mainly:
- Technology strategy
- Implementation of best software development industry practices
- Resources management
- Corporate management, and Stakeholder interfacing