Evolution of Software Engineering in NCTR

Projects

Prepared by:Mohammed abbas abdalla2016

NEEDS !

Presentation Scope

Project Management. Software Development Life Cycle (Agile ,

Waterfall ,,) Tools and Techniques.

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.

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.

Background about NCTR(Domains) Business Applications (ERP, DMS , E15 , Etc ,,) Communications Network Information Security Electronics Cryptography

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

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

VP of Eng.

Network & Security

Business Application

Communication

CTO

Business Application Department

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.

ERP Implementation Project

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

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.

Governance Level

SCRUM

Delivery Level

Software Development ProjectPre-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

Software Development ProjectPre-delivery Stage

Software Development ProjectPre-delivery Stage

Software Development ProjectDelivery 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

Software Development ProjectDelivery Stage

Software Development ProjectDelivery Stage - Reports End of Sprint Report End of Stage Report End of Project Report

Tools / Practices /Techniques   Tools / Practices /Techniques

 1 Subversion2 CodeBeamer ALM3 Sonar Code Analysis Tool4 Unit Test5 Retrospective 6 Continues Integration7 Story Board8 User story 9 Backlogs10 Sprint Review11  Design Pattern      

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.

Thank You