Se ha denunciado esta presentación.
Utilizamos tu perfil de LinkedIn y tus datos de actividad para personalizar los anuncios y mostrarte publicidad más relevante. Puedes cambiar tus preferencias de publicidad en cualquier momento.

Evolution of Software Engineering in NCTR Projects

1.692 visualizaciones

Publicado el

Evolution of Software Engineering in NCTR Projects

Publicado en: Tecnología
  • Inicia sesión para ver los comentarios

Evolution of Software Engineering in NCTR Projects

  1. 1. Evolution of Software Engineering in NCTR Projects Prepared by: Mohammed abbas abdalla 2016
  2. 2. NEEDS !
  3. 3. Presentation Scope  Project Management.  Software Development Life Cycle (Agile , Waterfall ,,)  Tools and Techniques.
  4. 4. Agenda  Background about NCTR  Diversity of NCTR Domains  The challenges of adapting project management methodology  NCTR journey of finding out suitable project management methodology.  Software Department as an example.
  5. 5. Background about NCTR  Nile Center for Technology Research (NCTR) has been established in the middle of the year 2007 as the first center in Sudan for applied research and development (R&D) in most of the fields of ICT, electronic.  The center is a governmental organization that belongs to the National Telecom Corporation (NTC) and registered at the business register of Sudan according to a license from the Ministry of Science and Technology (MOST).  NCTR launched three high class R&D centers in the most sounding, specialized, and leading universities in Sudan, University of Khartoum, Sudan University for Science and Technology and Karary University for Technology, in the fields of information technology, electronics systems and communication and navigation systems, respectively.
  6. 6. Background about NCTR (Domains)  Business Applications (ERP, DMS , E15 , Etc ,,)  Communications  Network  Information Security  Electronics  Cryptography
  7. 7. The challenges of adapting project management methodology in NCTR  Diversity of NCTR products  High uncertainty  Research nature of some NCTR projects  Selection of the Right Development Lifecycle  Requirements management  Tools  Working on taskforce culture  QC
  8. 8. NCTR journey  PMI - 2008 - 2010 (Waterfall)  ASAP for ERP implementation 2011 – Now (Waterfall)  PRINCE2 2011 – Now (Scrum, Waterfall) The Motivation to switch to PRINCE2  Come from IT background  Managing by stage  Business case  Focus on product  Integrated with other IT methods such as ITIL  More suitable for NCTR  Etc  Introduction of New NCTR Organization Structure 2014 – Now  Product Focus  Based On NCTR Domains
  9. 9. VP of Eng. Network & Security Business Application Communication CTO
  10. 10. Business Application Department
  11. 11. Business Application Department  2012 Establishment of software department  Consist of 3 section : Implementation, Development and Support.  Products : SHAMIL ERP, NileDox DMS, NileCare HIS  Two types of projects : Implementation, Development.  Implementation Project based on ASAP methodology  More than three implementation projects.  Development Project based on PRINCE2 for governance level and based on Scrum in delivery level.  2 development projects.
  12. 12. ERP Implementation Project
  13. 13. ERP Implementation Project Recommendations To achieve successful implementation project you have to consider the following  Contract.  Stockholder management.  Gap analysis  Communication.  Customer Top Management commitment.  Key users involvement.  Following up the methodology
  14. 14. Software Development Project  Based on PRINCE2 for project governance level.  Based on Agile Scrum for project delivery level  Three management stages  Pre-delivery Stage.  Delivery Stage.  Post-delivery Stage.  Three main roles : Product Owner, Scrum Master, Development Team.
  15. 15. Governance Level
  16. 16. Delivery Level
  17. 17. Software Development Project Pre-delivery Stage  Preparation  Building Up Product backlog  Setting up release roadmap  Next stage planning - Workshop  Requirements Pritorization  Number of Sprints  Sprint Goal for each sprint  Sprint Length  Next Stage Authorization
  18. 18. Software Development Project Pre-delivery Stage
  19. 19. Software Development Project Pre-delivery Stage
  20. 20. Software Development Project Delivery Stage  Sprint Planning - breakdown sprint goal to the tasks  Sprint Execution  Sprint Control: Daily standup meeting  End of sprint workshops - Features and process Result : Next Sprint Authorization , Premature Closure recommendation, Exception Sprint Authorization, Next Stage Authorization
  21. 21. Software Development Project Delivery Stage
  22. 22. Software Development Project Delivery Stage - Reports  End of Sprint Report  End of Stage Report  End of Project Report
  23. 23. Tools / Practices /Techniques Tools / Practices /Techniques 1 Subversion 2 CodeBeamer ALM 3 Sonar Code Analysis Tool 4 Unit Test 5 Retrospective 6 Continues Integration 7 Story Board 8 User story 9 Backlogs 10 Sprint Review 11 Design Pattern
  24. 24. Lessons Learnt  A void copycat of ready made methodology.  Do not let the consultant lead you.  Look for consultant when really needed.  Consultant for coaching, training, verification creation of methodology is your responsibility .  Simplicity is beautiful.  Learn from Experience.  Heavy documentation is not mean success of project.  Leadership and communication are very important for project success.
  25. 25. ThankYou

×