Click here to Skip to main content
15,112,662 members

Welcome to the Lounge

   

For discussing anything related to a software developer's life but is not for programming questions. Got a programming question?

The Lounge is rated Safe For Work. If you're about to post something inappropriate for a shared office environment, then don't post it. No ads, no abuse, and no programming questions. Trolling, (political, climate, religious or whatever) will result in your account being removed.

 
JokeRe: Satoshi Nakamoto Wants his BTC Back Pin
abmv24-Feb-21 22:09
professionalabmv24-Feb-21 22:09 
GeneralRe: Satoshi Nakamoto Wants his BTC Back Pin
David O'Neil24-Feb-21 22:45
professionalDavid O'Neil24-Feb-21 22:45 
GeneralRe: Satoshi Nakamoto Wants his BTC Back Pin
abmv24-Feb-21 23:11
professionalabmv24-Feb-21 23:11 
GeneralRe: Satoshi Nakamoto Wants his BTC Back Pin
David O'Neil24-Feb-21 22:44
professionalDavid O'Neil24-Feb-21 22:44 
GeneralRe: Satoshi Nakamoto Wants his BTC Back Pin
abmv24-Feb-21 23:19
professionalabmv24-Feb-21 23:19 
GeneralRe: Satoshi Nakamoto Wants his BTC Back Pin
Dan Neely25-Feb-21 3:56
MemberDan Neely25-Feb-21 3:56 
GeneralRe: Satoshi Nakamoto Wants his BTC Back Pin
markrlondon25-Feb-21 20:49
Membermarkrlondon25-Feb-21 20:49 
GeneralAt least 1 Software Engineer's Recommended "Things for BAs, PMs, SMs, and POs to Know About Software Development" PinPopular
MSBassSinger24-Feb-21 9:19
professionalMSBassSinger24-Feb-21 9:19 
I don't expect everyone, or even a majority, of readers to agree. These are things I wish every Business Analyst (BA), Product Manager (PM), Scrum Master (SM), and Product Owner (PO) could know and take to heart.

1 - Developers are not assembling widgets on an assembly line. Adding more developers, especially after the start of a project, does not speed things up. In fact, it usually slows things down and delays delivery.
2 - Developers, and especially software engineers/architects, are professionals, not blue collar workers. Treat them like professionals, and expect them to act like professionals.
3 - Team leads for a project should be a senior software engineer with people skills, not a BA, PM, SM, or PO. And certainly not QA.
4 - Look at each project like a bus. Lots of different skills are going in the same direction, to the same destination, but there is only ONE bus driver - the Team Lead.
5 - Limit yourself to describing, in specificity, what you want (requirements), not how to do it. Leave the technology choices to the developers and engineers.
6 - Make time for thorough and detailed planning up front (epics, features, user stories, tasks, etc.), with most of those documents fleshed out by the Team Lead and whomever he or she chooses. Then be agile enough to revise as needed during the project.
7 - If coding has started, and the user stories are still ambiguous, then stop wasting developer resources ($$$) and finish the planning.
8 - Keep meetings to a minimum. Ideally, on Monday or Friday, meet with the leads and developers to look at what was done the past week, what is still being worked on, and what is needed to be worked the coming week. Then leave the developers alone and let them go "heads down" coding. That delivers a better result faster.
9 - A well-managed development team converses peer-to-peer when necessary, without need for a meeting. If a problem arises that developers within a team cannot solve, they will contact the team lead, and if the scrum master's help is needed to get outside resources, it can be handled then.
10 - Deep-six the daily scrum "stand ups". They are not needed, and only slow down work.
11 - If you cannot get rid of the daily "stand ups", at least understand what they are. The phrase "stand up" does not refer to actually standing up, like a bunch of little school children. It means to stand up your work before the team for examination and discussion.
12 - Don't go to developers directly without coordinating with the team lead first. Developers on a team need to be coding, not spending time so you can get some data bits for a report. In most cases, the team lead will get what you need.
13 - When a developer is interrupted for meetings or questions not directly dealing with getting code done, it takes anywhere from 15 minutes to 2 hours for the developer to get all the moving parts back in their mind so they can pick up where they left off. Software development is a complex work that takes a lot of intellectual horsepower.
14 - When deciding "we need a meeting" that interrupts developers, calculate the total cost in labor, and ask yourself if the cost is worth what you get out of it. Consider a team of 8 developers and one team lead, at an average labor cost (salary, benefits, etc.) of $100/hr. Your 1 hour meeting just cost $900 and delayed the project by at least 2 hours.
15 - An experienced team lead with business experience and able to describe the technical in non-technical terms can easily reduce the cost of a development team by replacing most, if not all, of what a BA, PM, SM, and PO does. And get it done better and sooner due to lack of overhead. If is far easier for a senior software engineer to learn the business side than for a BA, PM, SM, or PO to learn the software development side.
16 - Agile, Scrum, Kanban, agile frameworks, etc. are not recipes to be followed. They contain principles to be considered and used in the SDLC if and how they provide value. Just read the original Agile Manifesto and see how far today's agile has strayed from it.
17 - Look for generalists, not specialists, on the development team. Hiring specialists (those who work in the specific toolsets being used today) works for now, but not as technology changes. Hiring generalists (those who know software engineering but can adapt and learn whatever toolsets are in use today) gives you people who can efficiently adapt as technology changes.
18 - If you want to learn one new thing, learn what value engineering is.

These opinions are solely my own, and not necessarily those of any current or past employer.
GeneralRe: At least 1 Software Engineer's Recommended "Things for BAs, PMs, SMs, and POs to Know About Software Development" Pin
raddevus24-Feb-21 9:31
mvaraddevus24-Feb-21 9:31 
GeneralRe: At least 1 Software Engineer's Recommended "Things for BAs, PMs, SMs, and POs to Know About Software Development" Pin
MSBassSinger24-Feb-21 9:47
professionalMSBassSinger24-Feb-21 9:47 
GeneralRe: At least 1 Software Engineer's Recommended "Things for BAs, PMs, SMs, and POs to Know About Software Development" Pin
Gerry Schmitz24-Feb-21 9:55
mveGerry Schmitz24-Feb-21 9:55 
GeneralRe: At least 1 Software Engineer's Recommended "Things for BAs, PMs, SMs, and POs to Know About Software Development" Pin
MSBassSinger24-Feb-21 9:59
professionalMSBassSinger24-Feb-21 9:59 
GeneralRe: At least 1 Software Engineer's Recommended "Things for BAs, PMs, SMs, and POs to Know About Software Development" Pin
Gerry Schmitz24-Feb-21 11:54
mveGerry Schmitz24-Feb-21 11:54 
GeneralRe: At least 1 Software Engineer's Recommended "Things for BAs, PMs, SMs, and POs to Know About Software Development" Pin
MSBassSinger24-Feb-21 12:01
professionalMSBassSinger24-Feb-21 12:01 
GeneralRe: At least 1 Software Engineer's Recommended "Things for BAs, PMs, SMs, and POs to Know About Software Development" Pin
Gerry Schmitz24-Feb-21 12:40
mveGerry Schmitz24-Feb-21 12:40 
JokeRe: At least 1 Software Engineer's Recommended "Things for BAs, PMs, SMs, and POs to Know About Software Development" Pin
Nelek24-Feb-21 11:23
protectorNelek24-Feb-21 11:23 
GeneralRe: At least 1 Software Engineer's Recommended "Things for BAs, PMs, SMs, and POs to Know About Software Development" Pin
Gerry Schmitz24-Feb-21 12:00
mveGerry Schmitz24-Feb-21 12:00 
GeneralRe: At least 1 Software Engineer's Recommended "Things for BAs, PMs, SMs, and POs to Know About Software Development" Pin
20212a24-Feb-21 10:13
Member20212a24-Feb-21 10:13 
GeneralRe: At least 1 Software Engineer's Recommended "Things for BAs, PMs, SMs, and POs to Know About Software Development" Pin
MSBassSinger24-Feb-21 10:37
professionalMSBassSinger24-Feb-21 10:37 
GeneralRe: At least 1 Software Engineer's Recommended "Things for BAs, PMs, SMs, and POs to Know About Software Development" Pin
20212a24-Feb-21 10:49
Member20212a24-Feb-21 10:49 
GeneralRe: At least 1 Software Engineer's Recommended "Things for BAs, PMs, SMs, and POs to Know About Software Development" Pin
Amarnath S24-Feb-21 20:46
professionalAmarnath S24-Feb-21 20:46 
GeneralRe: At least 1 Software Engineer's Recommended "Things for BAs, PMs, SMs, and POs to Know About Software Development" Pin
MSBassSinger25-Feb-21 6:31
professionalMSBassSinger25-Feb-21 6:31 
GeneralRe: At least 1 Software Engineer's Recommended "Things for BAs, PMs, SMs, and POs to Know About Software Development" Pin
5teveH24-Feb-21 21:09
Member5teveH24-Feb-21 21:09 
GeneralRe: At least 1 Software Engineer's Recommended "Things for BAs, PMs, SMs, and POs to Know About Software Development" Pin
MSBassSinger25-Feb-21 6:34
professionalMSBassSinger25-Feb-21 6:34 
GeneralRe: At least 1 Software Engineer's Recommended "Things for BAs, PMs, SMs, and POs to Know About Software Development" Pin
Slacker00724-Feb-21 23:57
professionalSlacker00724-Feb-21 23:57 

General General    News News    Suggestion Suggestion    Question Question    Bug Bug    Answer Answer    Joke Joke    Praise Praise    Rant Rant    Admin Admin   

Use Ctrl+Left/Right to switch messages, Ctrl+Up/Down to switch threads, Ctrl+Shift+Left/Right to switch pages.