I’m a new IT Business Analyst working on a digital wallet project. I’ve got a small change to work on for the mobile app. I wrote the user story and acceptance criteria. Now they want me to make JIRA tasks for the devs.
I looked at what other analysts do. They write super detailed tasks telling devs exactly what to do like changing the database.
This feels weird to me. In my old job as a Systems Analyst I’d just write the specs and then talk it over with the devs and QA folks.
I don’t think I should tell devs how to do their job. They know the tech stuff better than me. But I’m new here and still learning how things work.
What’s the right way to handle this? Should I keep it high-level or get into the nitty-gritty? I want to do a good job but also respect the devs’ expertise. Any advice?
Having worked on numerous fintech projects, I can say that the level of detail in JIRA tasks often depends on the team’s dynamics and the project’s complexity. In general, it’s best to strike a balance between providing sufficient context and avoiding micromanagement.
For a digital wallet project, I’d recommend focusing on clear user stories, acceptance criteria, and any specific business rules or regulatory requirements. Leave the technical implementation details to the developers’ discretion.
In your JIRA tasks, include links to relevant design assets, API documentation, or business logic documents. This gives developers a solid foundation without dictating their approach.
Consider scheduling brief task refinement sessions with the dev team to discuss requirements and address any questions. This collaborative approach often leads to better outcomes and stronger team relationships.
Remember, your role is to communicate business needs effectively, not to prescribe technical solutions. Trust in the developers’ expertise while ensuring they have all the necessary information to deliver a quality product.
As someone who’s been in the fintech trenches for years, I’d say there’s a sweet spot for JIRA task detail. You’re right to be cautious about overstepping into the dev’s domain.
In my experience, the best approach is to focus on the ‘what’ and ‘why’, not the ‘how’. Outline the business requirements, user flows, and expected outcomes clearly. Include any relevant design mockups or wireframes. But leave the technical implementation details to the devs.
That said, if there are specific regulatory or compliance requirements that must be met, make sure to highlight those. In fintech, those can be crucial.
I’ve found that scheduling a quick task refinement session with the dev team after creating initial JIRA tickets works wonders. It allows for clarification, catches potential issues early, and builds better team rapport.
Remember, your role is to bridge business needs and technical implementation. Provide enough context for devs to understand the bigger picture, but trust their expertise to figure out the best way to code it.
hey there, as a dev myself, i’d say keep it high-level. focus on the what, not the how. give us the requirements, user flows, and any specific fintech regulations we gotta follow. but let us figure out the technical stuff.
maybe set up a quick chat with the dev team to go over the tasks? that way we can ask questions and clear up any confusion. trust me, we appreciate not being micromanaged!