MS Event - ALM Case Study


Published on

A case study base on

Published in: Technology, Business
  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide
  • ~1 minIT related experience (Software Developer, Consultant, Product Manager, Project Manager)Team members include Developers, Builder, Tester, IT Administrators (DBAs, Network Admin)
  • ~1 minConcurrently running multiple projects that deliver world wide supportUntil 3rd quarter 2011, 12 membersBeing an AA, I work with multiple team in the company
  • ~1 minIT department in generally will land in costs center, in particular being an in-house department.The difference is fine line between the costs center and value center being under the support divisionCosts center merely support the business efficiency through process automationKey purpose of costs efficiencyContrary the IT costs normally go higherValue center take the supporting process, i.e. business process automation, to capture data and transform into business value driven information for decision makingFrom the old school, DSS – Decision Support System
  • ~1 minBusiness dynamic back by dynamic IT solution to deliver business value.
  • 1-2 minIn order for business to be dynamic, business needs…Timely management reporting to gather market intelligenceBack by solution that keep pace with their needsMost importantly attain “Time to market” de factor, which probably one the top few priorityIT responsiveness is stressed by the dynamic business needs..Time-To-Deliver = Time-To-Market
  • ~1 min
  • 1-2 minInformation inconsistency – Someone need to constant compile and update the single latest fileMultiple version from multiple sourceFile ServerIndividual PCEmailVersion overwrite – lost of information, and waste of effortLack of centralize information repository – to communicate the constant changes in informationTo store and access by all
  • 1-2 minConstraintsTimeline challengesLimited ResourcesLost of knowledge – due to manpower turn-aroundScatteredConsequencesMaintain consistency in qualityCorrectness of solutionReference - outdate print out / local soft copyIncorrect solution delivered – User complain about solution received is not what they expectedIT don’t have any fact to support
  • 1-2 minEarly deployment request – enable business to market earlyBusiness direction changes – hinder the actual expected system availabilityConsistency of build deployedSubversion, SVN, CVS – branching & mergingAll are great, but it doesn’t tied to our Mantis system
  • 1-2 minBacklog prioritization
  • ~1 minUpdate to this point, if I didn’t make aware that my team is itself is multi-nationality.Other than we developed the program in a common language, we probably havelinguistic of our own, and different culture.
  • 1 minCode check-in policy Compliance to coding standard / convention / formattingCompile error freeAttached Unit TestingAutomated buildProvide early detection of integration error in development stageTeam always build with latest changesWith historical build accessible, show stopper integration issue can be resolve separatelyReduce Bug RateEarly detection of coding error, integrationVarious reporting availability – customizable Graph view of issue reported over fixes applied
  • 2-3 minIntegrated working environment – It’s more than an IDEAccessing up-to-date documentationWork items planningBug reportingWork item progress updateIDEUnit testing ** Performance analysisApplication is multi-layered, web, app, DBA, servicesWMI is great, provided the team can build it inAssociation of requirements, test case, etc.Code changes are tested on-the-fly against the requirementsEnsure check-in code delivered the expected requirementsFocus on the key functionWasting time seeking / consolidating up-to-date documentsWaste no time trying to figure what are the work item for the dayWaste no time on upward reporting on work progressTeam motivationClear project timelineClear tasks listClear expectation of deliveryGoal oriented
  • 1 minSingle point of reference – up-to-date of requirementsCapture requirements through user story Historical reference – DocumentversioningMaintain Knowledge BasedPrevent lost of knowledge due to manpower turn-aroundEase of dealing with manpower turn-aroundEase of relocation of resourcesAlign delivery expectationAlert on changes
  • 1-2 minEffective Project PlanningVisibility of obstacleEffective Resource PlanningBetter project timeline projectionBacklog queryRate of bug discoveryRate between issue closed and issue openedReporting – Easy, self-serviceable, exportable reportingProject progress Closely monitor project progress against target completionIdentifying project obstacle base on effort distributioni.e. Another project roll-out increase maintenance effort, production issueTeam performance – able to plan more effectivelyClear project timelineClear expectation of deliveryClosely monitor project progress against target completionSchedule changes can be assess up-front if due to CR from stack holderIdentifying project obstacle base on effort distributionOverview of time spend on delivering business value work over maintaining the solution delivered. i.e. Another project roll-out increase maintenance effort, production issueDevelopment vs. MaintenanceQuality of solution deliveredMaintainability of solutionWorkload distributionBalance and effective workload distribution
  • 1-2 minAgile team that keep pace with business dynamic by delivering IT solution that’s in sync with business requirementsEnsure operation continuity with stable IT solutionReduce business operation costs, i.e. increase team productivity allows more value delivery Timely and accurate reporting allow managementResponse quickly to the ever changing marketMake better business decisionSolution that keep pace with the dynamic and agile of businessDynamic IT Solution allow the business to adjust to the dynamic marketIncrease adaptability to market changes back by IT solution that in sync with business dynamic
  • Strategic IT, spending on new capabilities that directly support new business strategies; Utility IT, all other IT spending… this category represent the accretion of an organization’s strategic innovations over many year
  • Hope you had enjoy my presentation.Life Transforming ExperienceRefer transforming the application life cycle managementAnd indeed it transform the life of my team, and those who business user who have depends on use to make their life better
  • MS Event - ALM Case Study

    1. 1. ALM the Key to DeliverBusiness ValueA life transforming experience in Creative Technology Ltd. Presented by McKhay Han, Application Architect
    2. 2. My Background 12 years experience, delivering IT Solution  SI,Services, On-Shelf, In-House  Largest system involved till-date  More than 100 servers across 4 DCs  > 60 team members Specialty  Mission-Critical Application Design  Performance Tuning Author: McKhay Han, Application Architect 2
    3. 3. About Myself Name, Sex… Email: Senior System Analyst, Creative Technology Roles:  Team Lead  Project Manager  Application Architect 9 team members Author: McKhay Han, Application Architect 3
    4. 4. Costs Center to Value CenterAn IT department that drive business value, isa value center, not a costs center. Author: McKhay Han, Application Architect 4
    5. 5. The Nature of Business Value Dynamic Business Business Value Dynamic IT Solution Author: McKhay Han, Application Architect 5
    6. 6. The Nature of Business Value Business Needs • Efficient Operation • Timely Management Reporting • Dynamic Business Solution • Time to Market IT Response • System Functionality • Application Correctness • Maintainability • Time to Deliver Author: McKhay Han, Application Architect 6
    7. 7. Begin is the Challenges Requirement Gathering Project Development Management Delivery Author: McKhay Han, Application Architect 7
    8. 8. Getting Requirements Right Reference Source  Emails  Words documents Nature of Information  Scatters  Quickly Outdated Lack of centralize approach  Datalost  Wrong requirements Author: McKhay Han, Application Architect 8
    9. 9. Development Challenges Tight project Limited Lost of Scattered time-line resources knowledge references Correctness of businessConsistency of quality Limited test coverage logic Author: McKhay Han, Application Architect 9
    10. 10. Deployment Challenges Needs to perform selective deployment  Earlydeployment request  Business direction changes Source Control disjoint from Work Schedules Consistency of build deployed against business expectation  Requirements is managed in spreadsheet  Work items in another spreadsheet  Source code in source control Author: McKhay Han, Application Architect 10
    11. 11. Project Management ChallengesLack of visibility• Project progress against target• Resource utilization• Quality of solution Project Assessment • Project planning • Evolving requirements • Project obstacle handling • Resource planning Author: McKhay Han, Application Architect 11
    12. 12. Advantage of Microsoft ALMYour journal from birth Author: McKhay Han, Application Architect 12
    13. 13. Quality Control Improvement Author: McKhay Han, Application Architect 13
    14. 14. Improve Team Productivity Integrated working environment Association of requirements, test case, work item and code check-in Automated build, test and deployment process Tight integration with MS Office Focus on the key function More motivated team Author: McKhay Han, Application Architect 14
    15. 15. Project Communication Single point of reference Historical Align reference expectation Central & Managed Information Project Knowledge reporting based Author: McKhay Han, Application Architect 15
    16. 16. Project Visibility Project dashboard  Up-to-date project progression  Timely update of schedule changes to stake holder  Visibility of resource utilization  Time spend on delivering business value versus system maintenance. Team performance visibility Workload distribution Author: McKhay Han, Application Architect 16
    17. 17. Toward Strategic IT IT solution keep pace with business dynamic Operation continuity with stable system Higher adaptability as a result of IT solution that is in sync with business dynamic Less downtime, more productive hours More accurate stake holders expectation Fair performance appraisal Author: McKhay Han, Application Architect 17
    18. 18. Reference en-us/strategies/alm 0  Briefabout the difference of “Strategic IT” and “Utility IT” Author: McKhay Han, Application Architect 18
    19. 19. Thank YouImprovement is a journey, and not the enddestination. Author: McKhay Han, Application Architect 19