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…)

développement en parallèle

Service-Oriented Development, the best of both worlds

Should you start thinking, as an IT Director, in terms of Service-Oriented Development rather than Application Development or even Commercial Software; if you really want to meet the challenges of today’s new business requirements?

The question is worth asking no matter your line of business. Surprisingly, even though we have been praising new development methodologies such as Agile Development and other development tools and fast development approaches for more than a decade, the fact is that the majority of large and medium-sized enterprises are still moving forward with long-term expense heavy IT projects, leveraging notorious platforms such as SAP or Oracle or commercial software.

(more…)

atome unique

Software Development Performance; a question of metrics?

The assessment of software development performance, be it of a software development team or a software development project will vary greatly depending on the type of metrics used.

This request for performance assessment in software development projects is constantly coming back and is a source of major concern for Managers; which is quite normal considering the low ratio of projects delivered in time… and costs.

(more…)

Process Performance and Innovation, a bond of heart and reason

Process performance and innovation create a bond of heart and reason within any flourishing business or, at the very least, any enterprise must become innovative in order to flourish because innovation almost always leads to a gain in performance on one level or another.

Thus, the company that wants to perform must innovate and the innovative company will perform… most certainly!

(more…)

gestion et performance

Perception of Software Development Performance by Management Style

The perception of software development performance truly varies according to management style; hence, performance assessment is, in fact, a question of perception. The performance assessment of a development team is closely linked to the management style and, more precisely, to the priorities it dictates; in software development as in any other activity.

Any manager would like to have an objective assessment of the performance of both his development team and his IT department as part of a software development project. The term “objective” is the key to the riddle here. Is there an objective method for assessing the performance of a developer, a development team or a software development company? Is there a key performance indicator in software development that really tells the truth?

In fact, one can hardly count the systems, methods, and nomenclatures that have been created since the beginning of the industrial era to evaluate performance in software development, as in any other field.

(more…)

Apprentissage Machine

Some enterprises are already reaping the benefits of Machine Learning

This article is made out of excerpts from a joint Survey made by MIT & Google conducted in late 2016, and which you can download here.

Machine Learning is for many enterprises the new proving ground for Competitive Advantage. A recent survey conducted by MIT Technology Review Custom and Google Cloud reveals that while the majority of businesses are struggling to apply Machine Learning, others are hard at work developing strategies for the technology — and are already realizing genuine ROI.

The survey included 375 qualified respondents representing a variety of industries, with the preponderance coming from the technology industry (43%) but also business services (13%) and financial services (10%). Most qualified respondents were either C-level executives (39%) or enterprise developers (37%), rounded out by vice president-level executives (23%).

(more…)