You should be inspecting and adapting the work in progress more often. You can codify your understanding in the form of test cases.
You can demo work in progress more often.
Also, the architect giving you requirements is a process smell. This suggests to me that your "stories" are more technical in nature rather than business-focused.
Satyaprakash Joshii wrote:I started creating user acceptance test cases and sending it in email to architect and manager.
Satyaprakash Joshii wrote:We are working on a product and they will find a customer for it.
The secret of how to be miserable is to constantly expect things are going to happen the way that they are "supposed" to happen.
You can have faith, which carries the understanding that you may be disappointed. Then there's being a willfully-blind idiot, which virtually guarantees it.
Has there been at least a market study done on which to base requirements for this product? If you can't say yes to this, that's another alarm.
How long have you been developing this product? If more than three months, yet another alarm bell.
My interpretation (for what it's worth) is that the OP is working for an offshore company who is doing some of the dev work for whoever this other company is.
If they (the offshore company) get paid by the hiring company
Satyaprakash Joshii wrote:
I have written in the above post on how we work. I am not sure what 'hiring company' means here.
The problem is primarily is a lack of communication and feedback. You should be inspecting and adapting the work in progress more often. You can codify your understanding in the form of test cases. You can demo work in progress more often. Also, the architect giving you requirements is a process smell. This suggests to me that your "stories" are more technical in nature rather than business-focused.
Satyaprakash Joshii wrote:he is busy too but that is expected for everyone
The secret of how to be miserable is to constantly expect things are going to happen the way that they are "supposed" to happen.
You can have faith, which carries the understanding that you may be disappointed. Then there's being a willfully-blind idiot, which virtually guarantees it.
Satyaprakash Joshii wrote:I agree that we need fast work but then they are also pointing to us missing the requirements . So not creating test cases and also not missing requirements both cannot happen together.
The secret of how to be miserable is to constantly expect things are going to happen the way that they are "supposed" to happen.
You can have faith, which carries the understanding that you may be disappointed. Then there's being a willfully-blind idiot, which virtually guarantees it.
Satyaprakash Joshii wrote:During demo there was one comment from him which said I want you to work faster instead of spending time on test cases which testing team will do (but that would be in future )..
[OCP 17 book] | [OCP 11 book] | [OCA 8 book] [OCP 8 book] [Practice tests book] [Blog] [JavaRanch FAQ] [How To Ask Questions] [Book Promos]
Other Certs: SCEA Part 1, Part 2 & 3, Core Spring 3, TOGAF part 1 and part 2
I have nothing nice to say about the architect, his attitude, or his intelligence. I'll just leave it at that and let you draw your own conclusions about what I think.
I'd argue that it takes longer to write code without test cases. Because then you have to check it manually. And you have to keep checking it manually as you add more code. This is a tremendous waste of time.
Satyaprakash Joshii wrote:
I'd argue that it takes longer to write code without test cases. Because then you have to check it manually. And you have to keep checking it manually as you add more code. This is a tremendous waste of time.
Does that mean you recommend to write code without test cases? Which way do you suggest?
The secret of how to be miserable is to constantly expect things are going to happen the way that they are "supposed" to happen.
You can have faith, which carries the understanding that you may be disappointed. Then there's being a willfully-blind idiot, which virtually guarantees it.
You can codify your understanding in the form of test cases.
Don't get me started about those stupid light bulbs. |