Week 4
Week 4:
- Current Week Objectives - Complete my assigned stories and shadow team members
- Current Week Accomplishments/Hours Worked -
- During this week, I asked my team members if they could give me an overview of their position and if I could possibly shadow them. Doing this allowed me to learn about different IT positions and how they all integrate together.
- My first overview was with a Business System Analyst (BSA). He informed me of his roles, which includes creating the project requirements, attending meetings with the business department to clarify tasks in the IT department, and running Scrum meetings in absence of the Scrum master.
- My second overview was with a SAT tester. SAT testers check out the functionality of their team for the upcoming release, and report back to the team if they find detects. Their objective is to try to break the code written by the developers to find an error, if there is one.
- During the previous weeks I had someone with me when I wrote code because of the complexity of the project and the dependency one class had on several other components. This week I was able to code on my own, now that I have a better understanding of how everything works.
- Hours Worked: I completed a total of 39.00 hours during my fourth week (June 16th - June 20th).
- Total Hours Worked: 139.3 hours
- Next Week Objectives - Next week I will have overviews with the Tech Lead, Product Owner, UCD, and Database/Developer members on my team.
- Key Lessons Learned/New Skills Acquired - I learned how various positions integrate together to complete a project. The Product Owner has the vision of the project, BSA records the project requirements, Developers write the code, SAT testers verify that the code works, etc. I will learn more next week of the other positions required on an IT team.
- Issues and Concerns - N/A
No comments:
Post a Comment