The document discusses software project management and challenges. It notes that on average, software projects experience 45% cost overruns, 63% time overruns, and only deliver 67% of planned functionality. Common reasons for project failures include a lack of integrated tools, poor communication, and inflexible processes. The document then covers topics like software development lifecycles, management processes, development methodologies, team management best practices, and tools that can help with project management like Microsoft Project and Visual Studio ALM.

1. การบริหารโครงการซอฟต์แวร์Software Project ManagementKritKamtuoMicrosoft Innovation Center Outreach - ManagerE-Saan Software Park , KhonKaen Universitykrit.k@micthailand.net

2. What is Software ?

3. What is Application ?

4. Software & ApplicationWhat is software ?= Science & ArtWhat is application ?= Output of user requirementKey differenceSoftware = DomainApplication = Sub Domain

5. Average cost overrun: 45%

6. Time overrun: 63%

7. Functionality delivered on average: 67%

8. Software Errors: $59 Billion US Economy– US National Institute of Standards & Technology NISTThe State of the IndustryProject success is rareSucceededChallengedFailed32%44%24%200835%46%19%200615%34%51%2004Source: Extreme Chaos, The Standish Group International, Inc., 2004, 2006, 2008

9. The State of the IndustryProject success is rareSucceededChallengedFailed32%44%24%200835%46%19%200615%34%51%2004Lack of integrated toolsSeparation of business and technologyPoor team communicationProject tracking vs. project managingInflexible or immature processesDifficulty balancing productivity and predictabilitySource: Extreme Chaos, The Standish Group International, Inc., 2004, 2006, 2008

10. What is Project Management ?

11. Stakeholder(ผู้เกี่ยวข้อง)Software ProviderExecutiveSystem AnalystDeveloperTesterImplementerQuality AssuranceDocument ControllerSoftware ConsumerExecutiveProject LeaderSystem AdminPrimary UserSecondary UserPM

12. Skill for PM.Business ThinkingFinancialEconomicLocal & Global InformationNews, Conversation, Research etc.Software Development LifecycleSoftware Management ProcessSoftware Development ProcessTeam ManagementEtc.

13. Software Development Lifecycle(SDLC)

14. Software Management Process

15. Software Management ProcessSoftware Management ModelTFS (Team Foundation System, by Microsoft)TSP (Team Software Process, by SEI)PSP (Personal Software Process, by SEI)CMMIISO 29110Etc.

16. Software Development ProcessSoftware Development ModelWaterfallSpiralExtreme ProgrammingAgile **Rational Unify ProcessCMMI

17. Team ManagementMeeting – Update Project Status, Problem, Brain StromDailyWeeklyMonthlyReviewRequirementAnalysis & DesignImplementationMonitor CommitmentRisk Management

18. Meeting & Brain Strom TipsObjectiveInvite AttendeeNoteSound RecordVideo RecordOne noteSummaryShare EverythingVia EmailVia SharePoint

19. Microsoft ProjectManage ResourceManage TimeManage TaskManage CostReporting

20. WorkshopScientific Calculator

21. CreateTaskDurationStartFinishPredecessorsResource Names

22. View in MS ProjectCalendar : Over allGrant Chart : DetailNetwork Diagram : Flow ChartTask Usage : Man/Day, Man ProgressTracking Grant : Project ProgressResource Graph : OverloadResource Usage : Resource/Time

23. Visual Studio- ALM

24. Visual Studio 2010

25. What is ALM?The coordination of development life-cycle activities, including requirements, modeling, development, build, and testing, through

26. Enforcement of processes that span these activities

27. Management of relationships between development artifacts used or produced by these activities

28. Reporting on progress of the development effort as a wholeWork item tracking ensurestraceability.Work Item Database & QueriesMetrics Warehouse

29. Comprehensivebusiness intelligenceenables real-time decision making

30. You can use toolsyou already know, including…

31. SLAProgram ManagementDeploymentGovernanceDisaster RecoveryStandards ComplianceALM and Visual Studio 2010……

32. Architecture FeaturesUML modelingMicrosoft has joined OMGUse Case, Activity, Sequence, Component and Class DiagramsReverse engineer from codePush down for code generation via Domain Specific Language (DSL) modelsLayer Diagram for architecture enforcementArchitecture ExplorerMultiple views of existing systemShows relationships between system elements

33. UML Activity Diagram

34. UML Use Case Diagram

35. UML Sequence Diagram

36. UML Component Diagram

37. UML Logical Class Diagram

38. Model Explorer

39. Architecture Layer Diagram

40. Architecture Explorer

41. IntelliTrace(Historical Debugging)Reduces debug “cycling”Start DebugEncounter defectDrop into debuggerMove back through execution history to locate defectHistorical debug trace enables debugging offline test runs“As you sit in the debugger, being able to move backwards while in the debugger (or attach the execution log to a bug) has to be the killer feature coming up in the entire Visual Studio 2010 release.” -John Robbins

42. IntelliTrace

43. ProfilingUnderstand how an application uses memory and where it spends its time.Optimize intelligently.

44. Coded UI TestingEnables verification of UI functionality.Record test actions and VS will generate the resulting code.Assertions can be added to verify functionality.Like all VS tests, results can be stored in TFS.

45. Coded UI Testing Walkthrough

46. Coded UI Platform Support

47. Test Impact AnalysisIdentifies tests impacted by code changesSignificantly reduces test time

48. Testing FeaturesQA Professional focused interfaceWork Item based test case management, test planning and status trackingFocused on RequirementsIdentification of high-priority testsRobust manual testing functionalityTest definitionUser-friendly Manual Test RunnerDefect data capture toolsAutomated user interface testing

49. Visual StudioTeam Test Elements

50. Test Elements: Define Manual Test

51. Test Elements: Define Test Suite

52. Test Elements: Manage Test Plans

53. Requirements Focused

54. Microsoft Test Runner

55. Better Tester / Developer CollaborationAutomatically gathers defect and runtime detailsEliminates the “ping pong” effectEliminates the “No Repro” problem

56. Automatic Test Data Collection

57. Rich Defect Entry

58. Defect Data: Steps to Reproduce

59. Defect Data: Build & System Config

60. Test Lab BenefitsSimplifies environment setupSimplifies testing multiple configurationsEnables reverting to baseline configurationProvides checkpoints to aid defect resolutionImproves test hardware utilization

61. Test Lab Management GoalsVirtualize test lab resourcesLower technical requirements for test environment creationEnable environment recreation for defect resolution

62. Test Lab Management – Define Environment

63. Test Lab Management – Run Tests

64. Test Lab Management – Capture StateDev clicks on lvr link & selects connect to snapshot of the environment

65. 60Dev is able to access the snapshot’ed environment via LE viewer

66. Team Foundation Server 2010

67. TFS 2010 PillarsAdministrationTestingProject MgmtHighlightEasily setup and configure TFS to run in your environmentGreat collaborations between dev & testContinuous quality validationRichly capture project plans in TFSEasily track & report on project statusWizard-based setup & config experience

68. Automated install of dependencies

69. Deployment on Vista and Win 7

70. Easily expose TFS to the Internet

71. Scale-out

72. Reporting Services and Sharepoint optional

73. Consolidate servers

74. Restore, move, and archive project data

75. Test case management

76. Requirements traceability

77. Detailed quality reporting

78. Manual test runner

79. Record & playback

80. Automated UI testing

81. Intellitrace

82. Gated checkin

83. Hierarchical work items

84. Excel-based agile project management tooling

85. Generate Excel reports of work items from a work item query

86. Project dashboards in MOSS & Sharepoint

87. Typed work item linksFeatures

88. And a Whole Lot More…Version ControlWork Item TrackingBuild AutomationOffice IntegrationAdministrationReportingTeam ProcessWeb AccessTestingBranch visualization

89. Conflict resolution

90. Improved history

91. Work item hierarchy

92. Typed links