1. PROJECT MANAGEMENT
FOR SOFTWARE DEVELOPERS
Matthew Levandowski | Eric Nelson | Mike Gibbons

2. CLEAN LOGIX LLC
• A small startup company started after Parent
Company Foam-it in Grand Rapids, MI
• Produces Cleaning Supply Solutions to Warehouses
in the Food and Beverage Industry.
• Primary Audience
• Adam, our boss
• He makes the decisions
• Secondary Audience
• Other Employees
• Will be using the software
• Must be enthused about the software

3. WHAT IS PROJECT MANAGEMENT
• Utilizing resources in an efficient manner to
complete tasks in a project in the time required
• Tasks depend on other tasks
• Some tasks need a specific resource
• Some resources can only be used on a specific
resource

4. ISSUES
• Initial requirements were very incomplete.
• 90% percent of features added in last 25%
development.
• How to organize the different development stages.
• How do we better assign team tasks?
• No notion of where we are at or how long to finish.

5. PHYSICAL TASK BOARDS
• VS

6. DIGITAL TASK BOARD

7. STACEY MATRIX
1. Agree and know how to
implement a project
1. Can easily move forward
2. Don’t Agree but know how to
implement
1. Scrum Meetings can help
reach agreement
3. Agree but don’t know how to
implement
1. Give time to research / plan
4. Total Chaos no one agrees and
knows how to move forward (avoid
issues)
5. The Dead Zone
1. Break down into chunks for
managing

8. WATERFALL METHOD
• Traditional method for projects
• Comprised of 5 steps:
• Requirements
• Design
• Implementation
• Verification
• Maintenance

9. REQUIREMENTS
• First step.
• Need figured out.
• Research conducted.
• Determines scope of project.

10. DESIGN
• Basic elements reviewed.
• Elements put on paper
• Elaborate from basic steps.

11. IMPLEMENTATION
• Working model constructed.

12. VERIFICATION
• Working model Tested.

13. MAINTENANCE
• Project fully implemented where needed
• Product adjustments made to ensure system works
as desired.

14. AGILE METHODS
• Newer more appealing methods.
• Address issues with Waterfall’s weakness
• Two big methodologies:
• Scrum
• Kanban

15. SCRUM
• Only do enough for project to work.
• Process of sprints – 1 month duration
• Lead by ScrumMaster
• Meetings every morning
• Teamwork, communication oriented

16. KANBAN
• Process control.
• Work-In-Progress:
• Identification and instruction
• Withdrawal Kanban:
• Hand process off to next step.
• Move more work into process.

17. PRIMARY RESEARCH
S O F T WA R E E V A L U A T I O N

18. SOFTWARE EVALUATION
Four different solutions
• ScrumWorks – Most Popular for mid size companies
• Rally – For Large Companies with tech support
• BaseCamp – Widely used for all types of management
• JIRA – Used by Large Game Companies but scales well

19. JIRA
• Primarily an issue tracker
• Has Addons like Greenhopper for Agile Support
• Price scales with # of users
• Integration with popular IDE’s
• No training costs
• On-Demand Hosting Online
• 24x7 Tech Support
• Custom Reports
• Starts at $10 / month for 10 users
• Additional $10 / month for Greenhopper

20. SCRUMWORKS
• CollabNet was founded in July, 1999 by Tim O'Reilly
• Scrum Sprint Logs, Burndown Charts
• Integrates with CollabNet’s TeamForge System
• Stand Alone Tools but Scaleable
• Release Planning / Forecasting
• Hosting for larger than 10 users
• Tech Support Plans
• Free for first 10 users no hosting

21. RALLY
• Supports Agile
• Story, Task and Kanban Boards
• Multi-team project management
• IDE and Test integration
• Free On-Demand deployment, but
also provide a on-premise based
solution including full time network
administrators minimum of $4000.
• All of these features only in
Enterprise edition which is $35 per
user a month.
• Additional Training Available

22. BASECAMP
• Online portal, Simple and easy to
use
• Documents projects from start to
finish
• Web-based tool (no required
software)
• Collaborate real-time
• Has all the essentials
• Multiple project/user
• Take management
• Whiteboards
• Etc.
• Information stored off site.
• Starts at $20

23. CONCLUSION
• Based on size of company and how much it will cost
to implement and maintain this type of software we
would recommend JIRA with Greenhopper.
• Logos – Research market for software and current
project stats
• Ethos – While we don’t have much data we will use
our research to push for more inquiry into subject
• Questions?