Guidelines in Production Issue Ticket Assignments

Here are my guidelines in assigning Tickets and tasks.
1. Each of us will be assigned to work on different SCRs/tasks. I’m telling them which SCRs should be fix by EOD. Usually we fixed 3 - 6 SCRs per day.
2. The number of SCRs assigned to them depends on the difficulty of the issue. For easy SCRs, a resource can be assigned at least 2 SCRs. Most of the time the difficulty is the data setup.
3. If the SCRs are related to other SCRs or SCRs touching the same module, I usually assigned it to one resource if applicable. I usually weighing the difficulty and effort in fixing the issue.
4. SCRs assigned to the resource is usually knowledgeable on the affected modules(he can be the developer of the module or he already worked on this module)
5. By mid afternoon, I ask the status of all SCRs. If there are still difficulties in the SCRs, I setup a time (which is around 15 mins depends on the difficulty of the issue) to assist and guide in resolving the issues.
6. If ever someone finishes his task, he already knows what is his next task.

Things to Do

1. Tutorials on the following:
   1. SQL
   2. PL/SQL
   3. Oracle Forms
   4. Unix
   5. C
   6. Java
   7. J2EE
   8. SOA
   9. Oracle SOA Suites
2. Create a personal blog.
3. Update SOA Enterprise
4. Review for PL/SQL exam
5. Review for Oracle Forms Exam
6. Study IBM SOA
7. Study UML and Object Oriented Design
8. Study SCEA
9. Study Oracle SOA

Welcome to Development Standards.Net

I’m Mark Anthony Marucot. I’m 5 years in IT industry. I started this blog to document all my projects, interests and ideas.  My major online project is IT Experts Central (http://www.itexpertscentral.com). This site focused on providing free tutorials and invite IT experts worldwide to collaborate and help each other. The pagerank of the site is currently 4. I hope that this will improve later on.