Pega BPM

 Role : Pega BPM Developer
 Experience : 5+ Years
 Job Location :- Chennai
 
Job Description :-
1. Own the complete program, even if it has some onshore or offshore counterparts (Telecommunication or Non Telecommunication) - You should be part of the entire lifecycle - from requirements till deployment
2. Once you get a business requirement, think like a customer and see if it makes sense. Then tie it back to system requirements.
3. If you do not get the right transaction volumes, always assume it will be millions of transactions.
4. Be aggressive in any follow ups, meeting your timelines and obsess over quality.
5. All timelines would be aggressive, ensure that you discuss with your counterparts and raise a flag upfront if those timelines cannot be met.
6. Focus on constant development model and not a burst model. Plan for daily progress and not for last minute catch ups.
7. Ensure to send EOD status mail to your lead
8. We work on an elastic model, there is a constant evaluation for every ER (sometimes for MRs) to ensure we have the right set of developers per program. Do not hesitate in evaluating this for yourself as well as for your teams.
9. Ensure you and other team members are up to speed on the delivery model, coding practices, processes and tools. When folks move between programs in future, we do not have time to teach everyone from scratch.
10. Review your designs / code from Telecommunication LSAs.