Already have an account?
Go to to login

To learn more, contact our sales team

Customer Driven Development

January 22nd, 2010 by Seth Kenvin

Frequent user interaction aligns our efforts

A month or so ago Andrew Angus of our customer Switch Marketing pointed out that often his firm starts multiple simultaneous projects with a single set of clients. The way our software was working, the participating clients would have to accept individual invitations to each project. He pointed out that this can be a nuisance to his clients, and that sometimes people don’t at first go through accepting each invitation resulting in their not gaining access to every project. So, his recommendation was to change our software such that when two people have been in a project together before, when one of them invites the other to a new project, the addition should be automatic with no need to accept an invitation. We agreed, and built it, and are grateful to Andrew.

Automatic addition of prior team-mates to project means no invitation acceptances which is of course mostly a benefit for video.Market7 users, but Michael Haley of our customer Bars + Tone pointed out to us that after we made that change this also can mean no notification of some new team members’ arrival in projects’ activity feeds. He finds it useful to¬†know when first log-ins happen, which makes sense to us too. So, using our agile development practices, we wrote a story in Pivotal Tracker that when an experienced video.Market7 user first into a project a new project of theirs, that occurance should go to the project’s activity feed.

Next week all of our customers will benefit from both Andew’s and Michael’s good ideas after we release new code that includes the latest customer-driven development ideas which our engineers just completed programming.

, , , , , , , , , , , , , , , , , , ,