{"id":105,"date":"2013-10-16T14:26:27","date_gmt":"2013-10-16T14:26:27","guid":{"rendered":"http:\/\/www.sofadeve.com\/?page_id=105"},"modified":"2014-04-14T12:12:28","modified_gmt":"2014-04-14T12:12:28","slug":"theway","status":"publish","type":"page","link":"https:\/\/sofadeve.com\/?page_id=105","title":{"rendered":"How we work – The Way"},"content":{"rendered":"

[et_pb_section][et_pb_row][et_pb_column type=”4_4″][et_pb_text admin_label=”Text” background_layout=”light” text_orientation=”left”]<\/p>\n

How we work<\/strong>
\nWe treat everything as a project. Below is an\u00a0outline of the phases a project usually comprises. This indicates the customer relation life cycle.
\nThe sequence of phases suggests a timeline. This can of course be adapted by combining or skipping phases according to client project specific requirements or wishes.We do fully subscribe to the Principles behind the Agile Manifesto<\/a>. As part of this it is about what works best. Even if it means to be Nagile in between.<\/p>\n

[\/et_pb_text][et_pb_text admin_label=”Text” background_layout=”light” text_orientation=”left”]<\/p>\n

Below is a rough outline of the main phases any project would go through in parts or in total. We \u00a0believe in ownership of the complete project life cycle to guarantee a full and successful implementation from specification to operation. The timings shown here are only rough indications and should be considered as proportions of the whole project timeline (here ~ 6 month). Of course these are hugely dependent on the scope and complexity of your project. The objective of the Acquaintance phase is to bring “Body & Soul” together. Despite our firm believe in rational, logic and expertise as key fundamentals of a successful project we also know that any team effort is highly dependent on the individuals involved working as one.<\/p>\n

[\/et_pb_text][et_pb_text admin_label=”Text” background_layout=”light” text_orientation=”left”]<\/p>\n\n\n\n\n\n\n
Acquaintance<\/th>\nIntroduction<\/th>\nSolution<\/th>\nMonitoring Controlling<\/th>\nCompletion<\/th>\n<\/tr>\n<\/thead>\n
3-5 weeks<\/td>\n3 weeks<\/td>\n2-5 weeks<\/td>\n2-5 weeks<\/td>\n7-11 weeks<\/td>\n<\/tr>\n
\n
    \n
  • Trust building<\/li>\n
  • Very small project<\/li>\n
  • Present Policies & Procedures<\/li>\n
  • Adjust Language (Terms and Habits)<\/li>\n<\/ul>\n<\/td>\n
\n
    \n
  • Analysis<\/li>\n
  • Specifications<\/li>\n
  • Environments (DEV TEST PROD)<\/li>\n<\/ul>\n<\/td>\n
\n
    \n
  • Creation Dev Environment<\/li>\n
  • Coding Execution<\/li>\n
  • Documentation<\/li>\n
  • Unit Testing<\/li>\n<\/ul>\n<\/td>\n
\n
    \n
  • Creation Test Environment<\/li>\n
  • Delivery Test Environment<\/li>\n
  • System Testing – Rework<\/li>\n
  • Documentation<\/li>\n<\/ul>\n<\/td>\n
\n