Monday, April 16, 2012

Agilety In Telcominucation Projects

Mostly at Telecommunication project OSS for billing system part the senior management at integrator company highly recommend the working base on Agility Methodology
which is given more strength and faster in delivery and result special at the project go live when the customer has rush to test the system on life plat form
also due to the high changes even during the release phase lead to a huge decrease at the maintenance phase and lack in the documentation and delivery quality from one point of view that Agile strategy does not focus at the Testing and Analysis phases as Waterfall and Spiral Methodology
and during analysis and release are highly adaptable with all changes which for a certain cases are highly preferable for project management.
while the usage of waterfall methodology or Spiral could give more focusing at the goal in term of gathering requirement and the result in term of documentation and quality because of the the testing period phase could be repeated  iteratively and at any modification the all phases should be start over.

 Main Agile principle "Individuals and interactions"  one of the mandatory factor where ever the methodology used for instance the usage of co-location and pair programing can save huge time for developer and programer and consultant because they can share same resources and the code has been verified twice in one phase and this guarantee and speed up the development and lead to same understanding for the requirement same for prototyping give better view to the customer than presenting just documents

"Customer collaboration" such a principle can give a huge advantage in project where the customer are highly educated and the marketing has a clear view about the requirement and the system solution should be implemented while give a negative result and might lead to a total crises where customers are not familiar withe the solution has no clear visibility as in new developed country in Africa and in special cases where the customer decisions hierarchy could make the customer involved in the development process has no power in taking the decisions that will lead dead end.

"Responding to change" highly recommended for customer perspective because in telecom the competitor gain the highly profit by offer the service first where gain more subscriber and this is why for same offers or services the customer might change the requirements several time in very short period while this always lead to huge mistake at the integrator side as the new modification not well documented or not fully tested and the main common mistake at the delivery version this why is highly advice-able to use any of the version tracking system in Agile Methodology.

while the idea of prototyping is welcome in telecom projects the "Working software" will be a huge disadvantage unfortunately specially at high value projects because as an integrator point of view can spend high value on development and configuration for a working version then will be by the customer and that will give both loose time and resource and at this point the customer involve and collaboration could be highly effective and can be one of the power key points and the for more efficient result and the Risk Management could be highly effective because can estimate the customer perspective and can give a quality result.

On general the working in telecom projects with minimal planning and do not directly involve long-term planning will give a high customer satisfaction and lead to successfully project on general even if that will not give the integrator the main benefits of the project and the short terms iteration give Agile methodology advantage than other module while still the integrator company insist at the Waterfall methodology cause high quality and guaranteed result also more benefits
in equivalent the consultants who prefer working on Agility mostly requested high costly this will effect the project.
Also face-to-face  for communication with the customer can be used instead of training phase but that will create a huge gap at the documentation which might be recommended in case of requirement a new version or upgrade the current version or even in migration  taking in consideration that different version could be deliver by different consultants.

Tools and techniques used by Agile as Continuous Integration could be recommended while there is no real practicing support such theory but as CI could give a quality control by automate the build and deployment and the use of commit on the baseline while all testing made on a different environment could be consider a solution in some projects same thing for domain-driven design
can be solution for many complex projects and where to many side project are involved,
also Test-driven development one of the key factor in telecom project success most of project manager are focusing on the testing in driven theory so the tests at the first development might not give a clear indication about the test made on the production level.  

No comments: