Hi, I'm new to the site, and hoping to find some help with my current project.
I've started with a new company, and after 8 years of complex global projects, I thought I had enough in the bag to cope with most things. however, I'm struggling with this particular situation
The project is a software suite solution. Within the project are many deliverables. The products being implemented have multiple applications with differing technologies. RPG (AS400) back end, Java front end, progress components, BPM (sql) database, and a .net app. With each product there is a team of people (varying skill levels)
The problem I have is that the teams really don't mix. The RPG team is the main team, however, they have been working with this old technology and don't like change to the point a definate fear factor.
The Java and BPM teams are young and inexperienced.
The company has no real processes for software delivery, there is no project methodology being used.
Its been an uphill task to try and get the older RPG guys to,
1. follow a process
2. write documentation
3. Interact with the java and BPM teams
The Java, BPM team just don't have any experience or mentors for the work to be achieved.
So as you can see its a strange situation.
Have people been in similar situations? if so, any recommendations of how to get the teams to gel would be really appreciated... my frustrations levels are the highest level
Suggestions/comments would be welcomed
I've started with a new company, and after 8 years of complex global projects, I thought I had enough in the bag to cope with most things. however, I'm struggling with this particular situation
The project is a software suite solution. Within the project are many deliverables. The products being implemented have multiple applications with differing technologies. RPG (AS400) back end, Java front end, progress components, BPM (sql) database, and a .net app. With each product there is a team of people (varying skill levels)
The problem I have is that the teams really don't mix. The RPG team is the main team, however, they have been working with this old technology and don't like change to the point a definate fear factor.
The Java and BPM teams are young and inexperienced.
The company has no real processes for software delivery, there is no project methodology being used.
Its been an uphill task to try and get the older RPG guys to,
1. follow a process
2. write documentation
3. Interact with the java and BPM teams
The Java, BPM team just don't have any experience or mentors for the work to be achieved.
So as you can see its a strange situation.
Have people been in similar situations? if so, any recommendations of how to get the teams to gel would be really appreciated... my frustrations levels are the highest level
Suggestions/comments would be welcomed