Software Development Process Seminar at HUI

1,221 views
1,042 views

Published on

0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
1,221
On SlideShare
0
From Embeds
0
Number of Embeds
2
Actions
Shares
0
Downloads
13
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide

Software Development Process Seminar at HUI

  1. 1. © 2013 KMS Technology
  2. 2. SOFTWARE DEVELOPMENTPROCESS“Software development involves profound technologicalknowledge, teamwork, processes, methods, and tools.”Christof EbertMay 2013
  3. 3. • Đào Anh Quốc – Process head at KMS• Contact– Email: quocdao@kms-technology.com3
  4. 4. SEMINAR OBJECTIVE• Share actual processes/practices applied in KMS• Exchange software development process betweenHUI and KMS4
  5. 5. 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
  6. 6. KMS PROCESS AND PRACTICES
  7. 7. ABOUT PROJECT LIFE-CYCLE7
  8. 8. KMS DEVELOPMENT PROCESSCMMi-based (RUP)8• In KMS we apply bothAgile-based (scrum)
  9. 9. SOME HIGHLIGHTS9• Estimation & planning• Customer expectation• Quality
  10. 10. ESTIMATION AND PLANNING10• Expert judgment• Story point• Two levels of planning• Short planning time
  11. 11. 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
  12. 12. CUSTOMER EXPECTATION12• Build relationship• Customer satisfaction survey
  13. 13. CASE STUDY AT WSG13Challenges:• New technology• Enforced deadline• Changing requirementsWSG• Development project• Project Accounting and ResourceManagement on iPhone and Android• Integrate web services
  14. 14. CASE STUDY AT WSG (CONT.)14
  15. 15. QUALITY15• Meet requirements• SLA• Focus to value for customer
  16. 16. AGILE FOR DISTRIBUTED TEAM
  17. 17. 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
  18. 18. 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
  19. 19. 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
  20. 20. NOT PURE AGILE20Can not apply fully agile methodology :- Onshore-offshore model- Onshore (software vendor) makes final decision- Project context
  21. 21. 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
  22. 22. AGILE-BASED PROCESS22Legend:Modified activities KMS standard activitiesSprint planningStandup meeting Weekly meetingSprint reviewRetrospective
  23. 23. 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
  24. 24. TOOLS24• v
  25. 25. 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
  26. 26. PROCESS AT CHECKPOINT HR26Challenges:• New product domain• Enforced deadline• Start with high level requirement• Fixed-priceCheckpointHR• Development project• Web-based Human Resourcesmanagement system
  27. 27. PROCESS AT CHECKPOINT HR (CONT.)27- Phase 1: RUP- Phase 2: Scrum
  28. 28. 28Internal
  29. 29. © 2013 KMS TechnologyTHANK YOU29

×