Making Software Management tools work for you - 2011 PHPBenelux Conference
Download as PPTX, PDF1 like917 views
The document discusses effective software management tools, emphasizing the importance of a well-structured process and the right tools for version control, task management, documentation, and testing. It provides a matrix of recommended tools for each category, outlines strategies for integrating testing into development, and suggests a method for evaluating and selecting tools. Overall, it highlights the significance of continuous adaptation and feedback in improving software project management.
Making Software Management tools work for you - 2011 PHPBenelux Conference
- 1. Making software management tools work for youJohn Mertic ( @jmertic )Partner and Community Developer Liaison at SugarCRMProvide feedback at http://joind.in/2417
- 2. Disclaimer: There are no silver bullets“For every complex problem, there is a solution that is simple, neat, and wrong.” – H. L. MenckenSource: http://www.flickr.com/photos/eschipul/4160817135
- 4. Where do you begin?“A determined soul will do more with a rusty monkey wrench than a loafer will accomplish with all the tools in a machine shop.”- Robert HughesSource: http://www.flickr.com/photos/ibnuabi/4534690993
- 5. Don’t proceed without a processSource: http://www.flickr.com/photos/lorensztajer/4316396658
- 6. Toolbox of Software Project ManagementSource: http://www.flickr.com/photos/skistz/398429879
- 7. What kinds of tools should be in the toolboxVersion ControlTask ManagementDocumentationTesting
- 8. Version ControlKeeps track of your codebaseEnables parallel developmentWhat’s you choicesBackup files manually ( not a real choice )CVS Subversion (SVN)Git
- 9. Evolution of Version Control
- 10. Task ManagementBiggest problem for teams in keeping organizedGood task management enables developers and managers to planShould support the development methodology you are using
- 11. Task Management Tool MatrixBug TrackersProject Managementweb2ProjectRedmineJIRA ( proprietary )FogBugz( proprietary )BugzillaMantisGithub Bug TrackerTracLaunchpadGoogle Docs / Excel
- 13. DocumentationUser facing documentation AND developer documentationDocumentation by nature is painful to write, so make it as much as a part of the development process as possible
- 16. The Do’s of Testing ManagementDO make automated tests automated with continuous integration Hudson / JenkinsphpUnderControl / CruiseControlDO develop a testing strategy that is integrated with build strategyDO analyze testing coverageBut don’t believe automated code coverage metrics
- 17. Testing Tools MatrixUnit TestingPHPUnitWhatever JavaScript unit testing framework you like - http://en.wikipedia.org/wiki/List_of_unit_testing_frameworks#JavascriptFunctional TestingSeleniumWatirSODA - https://github.com/sugarcrm/SODA
- 18. Testing Tools Matrix (cont)Performance TestingApacheBenchJmeterMeterMaid- https://github.com/sugarcrm/MeterMaid
- 19. How to find the tools that can work for youEvaluate where you are nowFind the problems you have in your current toolsTry out different tools that address the problems you are havingPick a tool and implement itRepeat
- 20. Thanks for coming!Tell me how you liked this talk…Submit feedback on this talk to http://joind.in/2417Contact Info:Email - [email protected] - http://jmertic.wordpress.comTwitter - @jmerticWho I work for:Partner and Community Developer Liaison at SugarCRM – http://www.sugarcrm.comWe’re hiring! [email protected]
Editor's Notes
- #2: Survey the audience, explain you will hit all demographics in one way or another
- #3: Software projects are complex beasts, not as straightforward as building a building. Use example of father-in-law’s shed, how they could scope out everything ahead of time.Building a building is more or less a perfected art, while software is still evolving. For example, compare building a building and software 40 years ago versus now.
- #4: Lots of choices is because developers first project is to build tools to support their own needs. However, each developer takes a different approach to the problem because their situation is different
- #5: Say how the quote almost invalidates the talk. The most mediocre teams will never be great with the best tools money can buy.However, a deeper look at the quote says that having the right tool is better than having the most expensive/most trendy/most used one.
- #6: Not having a process will make any implementation of tools unsuccessful. Correlate to how we see this in CRM implementations.
- #7: Differentiate between development and management tools. For example Eclipse is a development tool, but Bugzilla is a management tool ( and Git is both ).
- #9: Point out where version control fits into management ( tracking development and parallelizing teams ). Talk about how Sugar does it.
- #10: Describe the picture.Cool the fires about Git > SVN
- #11: Biggest problem for teams is keeping organized. Have lots of requests coming in, need to triage and prioritize them. Need to figure out how much can successfully be accomplished with a given amount of resources. Always make sure your tool agrees with your dev methodology
- #12: Differentiate Bug Tracker versus Project ManagementIntroduce the sticky note board
- #14: People love good documentation, but teams hate to write it. Lots of focus on tools that make it simple
- #16: Testing Is both automated and manual. Both are needed, since manual testing can uncover usability or consistency issues that automated will miss.
- #20: Reiterate the importance of your team working being able to accept the tools into their workflow.