Michael Paul

22 reputation

bio	website	about.me/michael.paul
	location	Sacramento, CA
	age	31
visits	member for	10 months
	seen	Jul 9 '12 at 14:53
stats	profile views	1

I'm a jack of all trades kind of tech guy with spotty knowledge in different areas of programming and scripting. In other words, I learn what I need to know in order to make my job/life more productive, but I'm certainly not a programmer by any means.

@mpaul

	22 reputation	bio	website	about.me/michael.paul	visits	member for	10 months
5 badges		location	Sacramento, CA		seen	Jul 9 '12 at 14:53

summary answers questions tags badges favorites bounties reputation activity

20 Actions

suggestions reviews revisions comments badges posts accepts all

Jul 5	comment	What to expect when you're the client Good points. We just asked them to involve their testing team. (Up until this point no testing team had been involved--it was just the developer working on the front-end) so we'll see if that makes a difference in bug squashing before we see the next build of the product. I'm hoping it does, because our time is much better spent providing feedback on look and feel rather than reporting bugs. Costs more to have QA, but speed to market it faster and it means less time spent documenting bugs and more time thinking about the product.
Jul 5	awarded	Supporter
Jul 5	accepted	What to expect when you're the client
Jul 5	comment	What to expect when you're the client Thanks for your answer. To clarify: up to this point, we've gone without their QA team getting involved but we have now invoked the QA team and expect to see much better results going forward. Interesting mind map--definitely broadened my horizons. The stuff I'm finding as I evaluate the app has been all around the "Function" area of that mind map. So many other things to consider! :)
Jun 29	awarded	Editor
Jun 29	revised	Providing feedback to developers added a link to Pivotal Tracker's website.
Jun 29	comment	What to expect when you're the client In this context, "done" means the screen's developed, looks great, and has the functionality to complete the task. (For example, you're looking at a screen with a table on it, and we have the ability to tap "add" and create a new record on that table.) Mostly concerned with look, feel and functionality. Speed to market is not as important as making sure everything's as quality as it can be, but it's important nevertheless. We've indicated previously that quality is kind of lacking and are evaluating the increase/decrease in quality with every iteration. Good learning experience.
Jun 29	suggested	suggested edit on Providing feedback to developers
Jun 29	comment	Providing feedback to developers Yeah, not sure what they use if anything for this kind of thing. Visiting them isn't easy as they're 2 hours away and I have a day job (this is a side project I'm working on). We just recently had the idea to do GoToMeeting/WebEx desktop sharing so we could collaborate more efficiently, which I love. Face to face is always best. But we also want to document all the different moving parts--I really like the idea of metrics, which Pivotal Tracker provides, and I think I'm going to sign up for a trial and see how we fare with that tool. From what I've seen, it looks great.
Jun 29	comment	Providing feedback to developers This seems to be exactly what I'm looking for. Thank you. At $18/mo for the number of people we'd need to hook into it, I think it's a massive deal when compared to the amount of time and effort spent maintaining a word doc.
Jun 29	awarded	Scholar
Jun 29	accepted	Providing feedback to developers
Jun 29	comment	Providing feedback to developers Thanks, I'll check this out too.
Jun 29	comment	Providing feedback to developers Very helpful, thanks. I'll check these out.
Jun 29	comment	What to expect when you're the client They do testing in-house, but we agreed to save the testing until each portion of the app is complete... perhaps we should revisit that agreement in the future.
Jun 29	comment	What to expect when you're the client Thanks for the answer. They do have QA in house, but I we both agreed that it didn't make sense to test the app out until a section of it was considered done from a development perspective; once it had all the moving parts, then it'd go through testing to find all the bugs and work them out. I'm new to being a client (and development of any kind in general) so these answers are helpful to figure things out. Thanks.
Jun 29	awarded	Student
Jun 29	asked	What to expect when you're the client
Jun 29	awarded	Autobiographer
Jun 29	asked	Providing feedback to developers