In this chapter we address the question of which frameworks are best suited for A.I. projects. You can look at A.I. projects from three perspectives:
- First of all, they are projects, which means they could be handled with project management methodologies like PRINCE2 or PMI.
- On the other hand, they have a very close proximity to software development projects, so one could tend to SCRUM.
- Finally, A.I. projects very often represent metricized processes, so that a consideration with the help of process management methods like SixSigma or LeanSixSigma would be possible.
Why should this question be asked at all? What impact does the choice of management framework have on the success of the A.I. project? To do this, let’s go back in time a bit to the past:
The development of project management methodologies in modern times dates back to the 1960s when the Project Management Institute was founded and laid the foundation for structured project management with the PMBOK. Besides PMI, IMPA and PRINCE2 dominate the market as project management methods. Internationalization, growth and sustainable knowledge management had made the standardization of project management necessary. Success came very quickly and the PMI today has over 600,000 members. Project management methods generally answer the question of how projects should best be carried out.
However, with the advent of IT projects, it was seen that the waterfall project management methods that had been common until then were not consistently successful, as software development requires much more iteration than non-IT projects. As more and more IT projects failed or took exorbitantly longer to complete, agile project management methodologies such as SCRUM were introduced for software development. Scrum is a rugby term and describes a rather wild scrum from the outside, but which follows a certain logic from the inside, albeit a painful one for many participants.
In contrast to common methods, pure SCRUM only defines clear goals for so-called sprints, which usually last 1-2 weeks. After the two weeks, the results are shown to the so-called stakeholders. Central role in Scrum has the product owner, who acts here as a substitute for the project manager. The Scrum Master monitors during this time that the Scrum ethos is also adhered to. In SCRUM, the concept of the project was deliberately discarded and replaced by product, which puts the focus away from the process to the output. This has a great impact in reality and in project oriented companies.
In the next section we will see the difference between waterfall and agile project management methods. Later we will look at the role of the product owner.