How To Work With SWTEAMS LTD


Published on

  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

How To Work With SWTEAMS LTD

  1. 1. How to workwith<br />SoftwareTeams<br /><br />SWTEAMS LTD, 3 Farquhar Lane, Quatre Bornes, Mauritius<br />E-mail: Phone: +230 427 5689<br />
  2. 2. Starting a project <br />Agreement on the project terms<br />Length of project (agreement)<br />Number of staff to assign on the project<br />Number of resources required from the client is managed to reflect the clients needs. (.i.e. Increase or decrease in the number of staff)<br />Technology and methods<br />SCRUM and timesheet reporting<br />Source repository and clients server connection (VPN etc)<br />Deliveries and resource/client interactions.<br />
  3. 3. Setting up the team<br />We create the teams based on skills and client needs for the project.<br />The team members are introduced to the client<br />Skype meeting or kick off-visit by client or team members on site.<br />Project requirement are discussed<br />Client and resource understanding<br />Project plan by teamlead is worked out with the client<br />Pivotal tracker and a detailed plan<br />SVN,Git or other repository server agreed with client<br />
  4. 4. Our Values<br />Introducing effective company culture<br />Involving the developers directlywith the clients, giving a mutualrelationshipadding motivation and quality.<br />Intensive training in creative and innovative IT consultancy<br />Our consultants drive to give our clients the best service<br />
  5. 5. The Project<br />We offer an on site project management training/monitoringofhow to manageyourremote resources.<br />Optional on site consultant package<br />We have weekly reviews with the client together with the developers to follow up on the progress of the project and other requirements from the client or clarification from the developers.<br />
  6. 6. Pricing (DKK)<br />Clients will only be invoiced 130 hours per month flat rate per resource out of a possible 160 hours.<br />
  7. 7. How do we scale ?<br />Moderate scaling <br />Focus on employee and client satisfaction<br />Employeetraining<br />Normal scaling phases:<br />2 to 4 new employee within 3 months.<br />Training with staff on project structures and methods<br />Introduce the company culture and clients expectations<br />
  8. 8. When is the team effective ?<br />Effectiveness in %<br />
  9. 9. A few success stories<br />Rebate Demo Project (Government of Australia)<br /><ul><li>A web service for the application of grants given by the government of Australia to the public purchasing green products.
  10. 10. The project was done in 30 days and involved 2 developers to get requirements and development.</li></li></ul><li>A few success stories<br />Android Development<br /><ul><li>This project required to port an existing application from Iphone to Android.
  11. 11. 4 developers to work on the project and they delivered after 1 month. The first week was a learning phase, and development of the application was 3 weeks.</li></li></ul><li>A few success stories<br />Project : Web shop <br /><ul><li>The client requested to build a web shop for their products with the Integration of online payment methods as well.
  12. 12. We had a team of 3 working on this project with basic knowledge of Magento, and after 3 months the project was delivered. We now have one developer doing support on Magentowebshop for the client.</li></li></ul><li>A few success stories<br />Medical Publisher Demo<br /><ul><li>The project was to demonstrate the full process and workflow for a publishing company for the weekly magazine for Doctors in Denmark (Ugeskrift for læger).
  13. 13. The project was designed based on Alfresco as workflow and task assignment module. and Drupal as web site and CMS for the organization.
  14. 14. The developer learned Drupal and Alfresco in just 3 days, and integrated the 2 systems after five days.
  15. 15. After 2 weeks we had a functional demo that demonstrated the basic flow, editing and review roles as well as publishing to the web.
  16. 16. Total time of development 3 weeks (including learning curve)</li></li></ul><li>A few success stories<br />