Security and Enterprise Agility: Constraints and Solutions

Security and Enterprise Agility do not usually go hand in hand. Also, the impact of security and compliance on Agility in today’s technological environment, which requires many companies to take such measures to ensure the integrity of their operations and preserve data confidentiality, should not be underestimated.

Definitely, the constraints that certain security and compliance measures impose suggest that Security and Enterprise Agility can hardly go hand in hand.

But, no matter how many developers there are in your organization, it is possible to do software development in Agile mode. Hundreds of writings praise the merits of this development methodology, so here are some of the most important points:

  1.       Better match between deliverables and needs;
  2.       Minimize the risk of slippage by splitting the project into “sprints” and these into “tasks” of short duration;
  3.       Better communication between the various project stakeholders;
  4.       Emphasis is placed on identifying and categorizing the functionalities that will have the most added value for the organization;
  5.       In the “cost, time, functionality” trilogy, the challenge is to develop as many of the most important features as possible in the time allocated, even if it means removing features, unlike the Waterfall mode, which emphasizes features, all features, even if it means exceeding them over time.

 

Plan Management vs Value Management

(more…)

The 4 fields of Enterprise Agile Transformation

There are countless companies that have started their Enterprise Agile Transformation in recent years. With good reason, because no one would question the benefits of the Agile Method today; this is an obvious fact that is unanimously accepted in all sectors of activity.

So, contrary to what one might think, Agile is not the one who wants!

Not all organizations are ready for Agility considering that this implies giving more autonomy to business units and work teams and creating cross functional teams as well. Moreover, not all business leaders will necessarily welcome Agility with open arms.

Thus, more than processes, the Agile method calls for a work philosophy that encompasses both the personnel and structure of the organization.

The Agile Enterprise therefore calls upon a profound transformation of the organization. This comprehensive transformation will affect all facets of the Organization including Personnel, Organizational Structure, Strategy and Technology. That’s the path to a successful Agile Transformation.

(more…)

Why proceed with your Enterprise Agile Transformation?

What is Agile methodology?  What are its principles?  What are the benefits of Enterprise Agile Transformation, turning your company in an Agile Enterprise?

The result of a search for continuous improvement in the software development process, the Agile methodology appeared at the forefront of ICT in the late 1990s in response to the excesses of major software development projects in terms of schedule, budget and quality of deliverables.

And this quest for continuous improvement in software development is in fact based on the search for added value for the company (project scope) and the optimization of the performance of software development teams within fixed schedule and costs as illustrated in the diagram below: 

Plan Management vs Value Management

(more…)

croix

Custom Software Development is dead. Long Live to Custom Software Development.

Two facts play against custom software development:

  • The market is full of comprehensive software solutions such as Oracle, SAP, IBM, Salesforce, etc.
  • Horror stories are on the side of major software development projects

Considering these facts, over the years companies have chosen to install commercial software solutions (CRM, ERP, accounting software, loan management system, etc.) instead of custom software development.  And in many cases, they replaced a “home” application whose technology was obsolete.

Of course, a lot of time and effort has gone into tailoring these business solutions to “your” reality to turn into customized solutions that really meet your needs. If you encounter one of the two situations below, rest assured, you are not the only one in this situation:

  • You have different systems that do not talk to each other
  • You still have specific business needs that are not met by your commercial software solutions

(more…)

.Net bootcamp in Montreal

Finding new developers has always been a big challenge for tech companies. There are not that many developers who are looking for jobs at the moment your company look for a new recruit. From that small number of developers out there, just some of them have knowledge or experience with technologies you use in your projects. Lots of students and graduates are looking to get to the job market fast and start a successful career. Getting the goal oriented, intense education and hand on experience is why they look for a bootcamp. There are just a few bootcamps in Montreal and they teach a limited number of technologies. You will get disappointed after a quick research for bootcamps and training programs for .Net technologies.

(more…)

Best practices for backing up IT Project Documentation

There are good practices and best practices for backing up IT Project Documenation; just as in everything else.

In the first two posts of this series about IT project documentation, we dealt with the “what” or what to document and the “how” or if you prefer the format you should use.

In this post, we will not discuss the “why” but the “where” to save the documentation.

If you think this post is the poor little brother of the two previous ones, think again. Too often, the IT Project documentation is not consulted because it is not easily or readily accessible and, for the same reasons, the documentation is often out of date.

To determine the right place to save your IT Project documentation, there are 3 factors to consider:

  • What documentation must be made available?
  • Who are the users or readers?
  • What is the frequency of consultation (reading and updating)?

(more…)

IT Project documentation format; best practices

What is the most appropriate IT Project documentation format? And, what are IT Project documentation best practices in terms of format?

The question may seem strange because, for many, this question does not even arise. But on closer inspection, it deserves to linger; how should I document an IT project and with what type of format?

To highlight the challenge of an IT Project Documentation format, there are three factors to consider:

  • Object of documentation
  • Who is it for?
  • Who is it produced by?

(more…)

IT Project Documentation best practices; the object of documentation

IT Project Documentation Best Practices are not simple because the purpose of the documentation is not always obvious. First, in an IT project, you can find a lot of different documentation; the famous user manual, the requirements documentation for the software operator, the architecture and design documentation for analysts, designers and developers and the technical documentation or software documentation for programmers are the main ones examples.

In short, Documentation is like insurance, you need it but you must find the right balance.

As far as we are concerned, we will talk about the architecture and design documentation and the technical documentation of an IT development project. So, what should we document?

In this series of posts, we will address the following points:

  • What should be documented in an IT project?
  • How should we document it?
  • Where should these documents be made available to different readers?

(more…)

The vision of Service-Oriented Development, beyond Service-oriented Architecture

We would like in this post to return to the idea, beyond the Service-oriented Architecture, to the vision of Service-Oriented Development because it really is something, considering that many argue that, in IT, there was a before and after SOA Architecture!

And the reason is quite simple because, with the service-oriented architecture (SOA), the developed services found themselves at the heart of the Information Systems architecture, as an interface with both the fundamental applications and the data.

Although this may not be obvious at first glance, many developers have suddenly gained some leeway, freedom of design, some say newly enhanced creativity.

(more…)

Service Oriented Development, the benefits… without the risks!

Service Oriented Development offers all the benefits of custom software development without the risks and without the costs of a Commercial Software; this is what we intend to address in this sequel to the previous post.

We explained in the previous post that while Custom Software Development constitutes a significant risk in terms of sustainability of services and development costs; commercial software often entails huge pre-installation adaptation costs and recurring license fees.

Thus, we explained to have taken another path a few years ago because it seemed to offer the best of both worlds for both the client and the developer; service-oriented development based on three principles:

(more…)