Implement & Test
THE WAGILE FRAMEWORK
Here at Digital Bananas Technology, we use what we call a hybrid methodology to manage, monitor, control and deliver our digital projects on time and within budget. It has proven to be highly effective in driving the cost of development down and delivering working software our customers actually want to use with a high yield on ROI. As a tech incubator, you really want to focus on building products with low operational cost and keeping your development cost to a bare minimum with a view to deliver in phases based on immediate business needs, mid term business needs and long term business needs. To do this we need the Prince 2 methodology (managing projects in a controlled environment), Waterfall methodology (step down approach to the software development life cycle) and the Agile methodology (building bits and bobs and delivering on an incremental basis giving room for changes, feedback and improvements based on immediate business needs and benefits.) We call this methodology the WAGILE methodology as you can see below.
THE SOFTWARE DEVELOPMENT LIFE CYCLE
The software development life cycle describe a process for planning, analysing, developing, quality assuring and deploying our digital web and mobile applications. You will be provided with hands on training and practical work experience throughout the entire lifecycle of the development process. You will understand and be able to apply each stage of the lifecycle from analysis right through to deployment going through the requirement engineering process, UI and UX design, coding and deployment as a project manager, business analyst, PMO analyst, project support officer or QA manager.
THE AGILE SCRUM METHODOLOGY
The software development process has a number of their own methodologies however we focus on two main ones here at Digital Bananas Technology. One of them is the Agile process which focuses on deploying deliverables of parts of the products in small chunks every 1 – 2 weeks and repeating the process each week for a period of 4 – 5 weeks until we have depleted all the deliverables, spent the budget or there is no longer any business value to continue. This process is quite effective in getting your product to market pretty quickly and getting in right through a series of iterations giving room for feedback and changes, however without control measures put in place, it can spiral out of control. We will teach you how to merge this framework with others in order to realise it’s full potential.
THE WATERFALL METHODOLOGY
The waterfall model is a sequential design process, used in software development processes, in which progress is seen as flowing steadily downwards (like a waterfall) through the phases of conception, initiation, analysis, design, construction, testing, production/implementation and maintenance. It’s one of the oldest and widely used methodologies within the software development life cycle. It follows a step down approach allowing for greater control and can allows for more accurate project timelines, however it’s strict control process does not allow room for changes and feedback. It’s best used for products where business value is known and the modules already exist.
OUR WAGILE FRAMEWORK
We feel it imperative that our candidates gain practical work experience using a combination of the Prince 2, Waterfal and Agile methodology. The combination as mentioned earlier is what’s called a hybrid methodology, what we call WAGILE here at Digital Bananas Technology. As a project management or business analysis professional, you will have the opportunity to master each framework and easily combine them where applicable. The Prince 2 and Waterfall methodology brings control and structure to our development environment while the Agile development framework bring flexibility and adaptability to our development environment. Candidates with expertise in all stand a stronger chance of securing highly paid project management and business analysis roles.
REQUIREMENT ENGINEERING HERE AT DIGITAL BANANAS
As a project manager or business analyst, engineering business requirements from a justified business case is a process you will have to learn and master. This requires a lot of stakeholder management and interaction which involves project sponsors, tech teams, business team, third party suppliers, partners and departmental heads who have an invested interest in the project. Requirement engineering approaches differ depending on the methodology you are using and your practical work experience will cover how requirement engineering is done for both Waterfall and Agile methodology.
Once the modules of the application or the entire application has been successfully developed the next stage is quality assurance where we test each module / functionality, the entire system as a whole and finally usability, performance and security testing. It’s important to get it right the first time and to do this, QA must be seen as part of the start of the project and not something that’s done after development. Your work experience will cover this in greater detail.