Developers are a very big part of the process and because they’re such an important cog, we would want them to be happy. We don’t want them to just give their work without having any say, or feeling like they’re nothing more than just robots putting out work. They’re an integral part of the system and it’s important that they voice their opinions.
I have talked with a lot of developers about ways to make SCRUM more developer friendly. One of the things that they asked was that they get more communication from the top down. A lot of times there isn’t a lot of information given to them as to why some parts of the process are more important than others and why some stories are more important than others.
Very often we ask them to pivot their attention from one story to another, because of the priorities, but they have no idea why. If someone hears 30 hours for a user story, then they take it literally, and think ‘by next Monday’ it will be complete, which would not be accurate. Story points are whenever we’re estimating hours, but they’re an estimate and they should not be taken literally.
The point of a user story is that we’re sitting down with the user and we’re asking them – ‘In your daily job, in order to make this software work, what do you do and what do you need it to do?’. The developers ask that we actually talk to the users and find out what they need, instead of reading a technical document. and then deciding from there, based on the architecture, what we think a user will need.
Getting Started with Generative AI-Assisted Coding
With numerous benefits to using Generative AI in coding, it’s no wonder so many organizations are harnessing this new technology to their advantage. If you haven’t started using Generative AI in coding yet, though, no need to fear. In this video, Chief Engineering Officer Janet Pierce shares three steps to help you get started with using generative AI in coding.
AI-Aided Product Engineering
AI-aided product engineering demonstrates a shift from the more traditional, development-focused use of AI. In this Tech in 2, Sparq Chief Technology Officer Derek Perry shares more about this concept and how it can help organizations with critical things like improving speed-to-market.
Better Software Development Through Collaborative Communication
Collaborative communication in software development is so important, as it helps you anticipate obstacles, figure out how to resolve them and ensure you have a well-rounded product. In this Tech in 2, Senior Consultant Jennifer Butler shares three keys to collaborative communication.
Learning From Old Code to Improve New Code
When faced with very old code, a developer might question “what were they thinking?” or “who would design something like this?” In reality, though, there’s actually a lot that can be learned from old code. In this Tech in 2, Principal Consultant Jeremy Swineheart shares three keys to learning from old code.