Software Development Process Seminar at HUI
Upcoming SlideShare
Loading in...5
×
 

Software Development Process Seminar at HUI

on

  • 901 views

 

Statistics

Views

Total Views
901
Views on SlideShare
901
Embed Views
0

Actions

Likes
1
Downloads
7
Comments
0

0 Embeds 0

No embeds

Accessibility

Categories

Upload Details

Uploaded via as Adobe PDF

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

Software Development Process Seminar at HUI Software Development Process Seminar at HUI Presentation Transcript

  • © 2013 KMS Technology
  • SOFTWARE DEVELOPMENTPROCESS“Software development involves profound technologicalknowledge, teamwork, processes, methods, and tools.”Christof EbertMay 2013
  • • Đào Anh Quốc – Process head at KMS• Contact– Email: quocdao@kms-technology.com3 View slide
  • SEMINAR OBJECTIVE• Share actual processes/practices applied in KMS• Exchange software development process betweenHUI and KMS4 View slide
  • AGENDA• KMS Process and practices– Estimation & planning– Customer expectation– Quality• Agile for distributed team– Key challenges we faced– Solution– The practices that make a difference5
  • KMS PROCESS AND PRACTICES
  • ABOUT PROJECT LIFE-CYCLE7
  • KMS DEVELOPMENT PROCESSCMMi-based (RUP)8• In KMS we apply bothAgile-based (scrum)
  • SOME HIGHLIGHTS9• Estimation & planning• Customer expectation• Quality
  • ESTIMATION AND PLANNING10• Expert judgment• Story point• Two levels of planning• Short planning time
  • INVIVODATA PRACTICES11• A combination of PERT/ experiencesand Historical Data– [(O + 4M + P)/6] Effort Estimation Property• Various Project Types• Large amount of projects• High Rate of TestingDelivery & Changes• Documentation Key Challenges• Short Planning Time• The order of magnitudeestimate with narrowranges• Limited Budget• >90% Resource Utilization• 2-phase planning– 1st level planning is for resource acquisition & 1stgate acceptance of budget allocation– 2nd Level planning is for document review anddetailed estimation while developing test-cases aswell• The combination of historical data and PERTreduces risk of falling out of budget & having“acceptable” estimation• SpringBoard where al tasks rotated by team, lowpriority items in the schedule Solutions
  • CUSTOMER EXPECTATION12• Build relationship• Customer satisfaction survey
  • CASE STUDY AT WSG13Challenges:• New technology• Enforced deadline• Changing requirementsWSG• Development project• Project Accounting and ResourceManagement on iPhone and Android• Integrate web services
  • CASE STUDY AT WSG (CONT.)14
  • QUALITY15• Meet requirements• SLA• Focus to value for customer
  • AGILE FOR DISTRIBUTED TEAM
  • AGENDA• KMS Process and practices– Estimation & planning– Project management– Quality• Agile for distributed team– Key challenges we faced– Solution– The practices that make a difference17
  • CURRENT AGILE TEAMS18Most of projects:• Unknown and changing requirements• Dedicated team (time-material)• Short time to market• Small team size80% development projects in KMS adoptAgile practices
  • CHALLENGES• Distance communication– It’s not efficient and effective incommunication.• Time zone– Waiting time for exchange information– Inconvenient in arranging time for meeting• Language• Culture19
  • NOT PURE AGILE20Can not apply fully agile methodology :- Onshore-offshore model- Onshore (software vendor) makes final decision- Project context
  • SOLUTION• Communication Tools– Online collaboration software, Smart whiteboard,video/audio conferencing.• Equal teams– Both sides are aware of what is happening on theother side.– Similar type of tasks assignment.• Personal relationship between team members– Build personal relationship and culture exchangebetween onshore and offshore team members.21
  • AGILE-BASED PROCESS22Legend:Modified activities KMS standard activitiesSprint planningStandup meeting Weekly meetingSprint reviewRetrospective
  • TECHNICAL PRACTICES23• Some notes about technical practices:- It’s important to do continuous integration- Design before coding for important features- External code review for first releases, andimportant features- Follow project/industry coding convention andbest practices- Increase automation test
  • TOOLS24• v
  • RELATIONSHIP BUILDING PRACTICES25• Arrange onshore and offshore visits• Maintain a forum to share personalinteresting/information• Quarterly video meeting• Offshore updates to onshore what ishappening in offshore, and otherwise.• Connect client via Facebook,LinkedIn
  • PROCESS AT CHECKPOINT HR26Challenges:• New product domain• Enforced deadline• Start with high level requirement• Fixed-priceCheckpointHR• Development project• Web-based Human Resourcesmanagement system
  • PROCESS AT CHECKPOINT HR (CONT.)27- Phase 1: RUP- Phase 2: Scrum
  • 28Internal
  • © 2013 KMS TechnologyTHANK YOU29