ScrumPad Community
Bringing together serious buyers and expert agile developers to build exciting, business critical solutions.
How it Works
- Create a project and request for proposals from the community
- Receive proposals from great agile teams
- Review the proposals and select the best team
- Start collaborating with the team to build the software incrementally
How can your team use our community?
For Agile Development Teams
- Tap into a network of serious buyers
- Market your services cost-effectively
- Increase customer satisfaction using ScrumPad
- Get paid at the end of every iteration
- No reverse escrow, trust is the core of the Agile community
For Agile Buyers
- Tap into a trusted network of expert Agile developers
- Reduce risk, and accelerate ROI by receiving working software incrementally
- Collaborate easily with your developer through ScrumPad
- Tap into our trusted network of experts who can help you with preparing requirements, reviewing proposals, reviewing design, reviewing codes, etc.
- No escrow required
For Agile Experts
- Market your expertise cost-effectively
- Help spread Agile adoption
How we are different
- We encourage team-based delivery. We believe serious software can only be built by a team (at least two or more).
- We require all our developers follow one of the Agile processes- Scrum/XP/Kanban/DSDM
- We encourage incremental delivery and payment.
- We encourage collaboration (one of the four manifestos of Agile) and trust.
- We encourage our developers to be associated with Agile Alliance, Scrum Alliance, PMI, or DSDM Consortium. These organizations are involved in advancing the software development processes.
- We encourage a minimum size for projects- enough for two fulltime developers + 1 QA for 1 week = 120 hours worth of work.
Tips for win-win results
- If you are not familiar with how Agile process works, hire a consultant (someone different from your developer) who can manage this for you.
- Make sure your developers are producing working software every iteration.
- Iteration should not be more than 4 weeks, prefer 2 weeks. For smaller projects, use 1 week.
- Consider hiring a consultant to review design and codes every sprint.
- Make sure to have two separate environments- test and production, when you have a live system.
- If your developer is from another country and you are not familiar with their culture, make sure to hire a consultant who is.
- Always communicate through ScrumPad. This helps keep all conversations in the context. Also, it helps avoid any need for arbitration.
