Industry SDLCs

Industry SDLCs and Business ClimateJustin Kalicharan CredentialsDirector and Senior Technology OfficerOver 14 years of coding experience in various languages Managed Projects $80MM+Lead team over 350+ developers, BAs, Managers, QA, Technology LeadsResponsible Vendor supplier relationships for Commercial BankingPrimary Relationship IT Director to Commercial Business Partners

SDLC Methodologies used in BankingSoftware Development Life Cycles (SDLC)WaterfallAgileTest Driven DevelopmentPrototypingIterativeWaterfall

Waterfall Pros and ConProsProgression and forward progressOne time resource engagementClear Milestones for Suppliers and External groupsConsLarge gaps between requirements and implementationDifficult to requirements changes late in the processSlow to marketAgile

Agile Pros and ConsProsFast to MarketHighly adaptable to business need changesHigher rate of success at implementation

ConsHigh resource engagement neededDifficult or implement with varying interfacesWeaker documentation, contributing to knowledge silosTest Driven Development

TDD Pros and ConsProsGreat cost savings in testing, unit testing, and regression testing. 40% - 60% Defect reductionSelf documents development how to, and business logicForces cleaner design of interfaces, especially in MVC architectureConsHigh cost of writing unit test casesHigh maintenance costsHigh cost of business requirements changeWhy do we use SDLC?Resource ManagementEffort of people on the teamCost estimationWhat will this cost meFeature delivery and communicationTraining, Communication to usersChange ControlApplication supportHandle complexitySecurityRisk ManagementWhy do Projects Fail?Requirements: Unclear, lack of agreement, lack of priority, contradictory, ambiguous, imprecise.Resources: Lack of resources, resource conflicts, turnover of key resources, poor planning.Schedules: Too tight, unrealistic, overly optimistic.Planning: Based on insufficient data, missing items, insufficient details, poor estimatesRisks: Unidentified or assumed, not managed.POOR COMMUNICATION!

Future of ITProgramming Skills are a CommodityGlobalization impact on software developmentWestern needs have evolved to technical architecture, relationship management, development project leadershipBusiness AnalysisConsulting and Solutions100 IT grads in India for every Western GraduateCloud Hosted TechnologiesMobileStrategic PlanningFocus on Secondary discipline in desired industryBusiness, Marketing, ManufacturingGraduates by Country1999-20002000-20012001-20022002-20032003-20042004-2005United States108,750114,241121,263134,406137,437133,854India82,107109,376129,000139,000170,000China: MoE and CERN282,610361,270China: MoE Yearbook212,905219,563252,024351,537442,463517,225Roles and ResponsibilitiesBusiness AnalystDocument requirementsManage requirement sessionsMust have a working understanding of the technology platformMust have a working understanding of the business use casesR&RDevelopment Lead Good understanding of the business use casesExpert understanding of the technologyResponsible for designing the solutionsMust be able to manage a team of developers

How much will I get to Code as a Development Lead?Development Lead: 25%Remaining 75%Design DocumentationArchitectureTraining and knowledge transferExternal Team support, Business Unit, Quality Assurance, BADeployment supportQA, UAT, ProductionCode ReviewsR&RQA AnalystCreate test design and test casesExecutes test cases and regression testingEnsures code quality prior to production implementation

Top 10 reasons projects fail10. Dont use a specific methodology because coding is all that is really important.9. Create the project plan by working backwards from a drop dead system completion date.8. Dont bother with a data model. Just build whatever tables you need.7. Use a Technical Lead that has never built a similar system. 6. Hire forty developers to make the coding go faster.Top 10 reasons projects fail5. Building in a technology that no developer has any knowledge in.4. Three months before the system goes live, assign one junior developer to handle the data migration.3. Skip the testing phase because the project is way behind schedule.2. Change the system to support critical new requirements discovered during final development.1. Buy a commercial, off product and customize it, a lot.

Links and Referenceshttps://fullfact.org/factchecks/india_uk_engineering_science_graduates-29183http://www.forbes.com/2007/08/05/india-higher-education-oped-cx_prg_0813education.htmlhttp://www.jagranjosh.com/careers/computer-science-1288159889-1