Sensitive content
Decided to switch to using agile to update features / add functionality ofJJFlex. For work they use it so I figured it would be helpful to use that methodology with this project, something that's familiar and if I screw it up, it can be fixed. We just finished a second coding sprint. Now, I've been tasked to use test plans to make sure functionality works. Then we'll plan more sprints / main scrums. Agile has funny names, but the idea is to set up small jobs, divided into tasks to get a job done. My paid changed from IT specialist to IT roject manager, so this has been super helpful even though we're simulating meetings like sprint kickoffs / after action reports. When I take my pmp exams, this will help me better learn / understand how Id do it in a larger project. To be fair, the changes that are on the roadmap for JJ Flex make it a super complex project, so not only do I get to put it on my resume, but I can use this experience to apply that be certiied a "Project Management Professional". My supervisor is on board and though it's listed as advanced when I only need intermediate, he will still, with my assistance, write justification to get the agency to cover test. I love the sact that Claude suggested that we try it. The key to making it work is keeping exhaustive documentation and context files so that all I need to tell it is to start sprint X and then move on.
Arfy
in reply to Noel Romey • • •Sensitive content