And you are here why?

So you’re building a product. I assume you’ve got everything under control? You know what you’re building, what stages it needs to be delivered in, when they are due, and so on, right? Most importantly, you have all of the things that you are doing —  and need to do!  — documented, right? Well, for those of you whose To-Do list is some variation of the above, herewith an actual list (•) of all the things that you should have covered. Take this as a starting point — at the very least you should have   some   idea around each of the following. You can flesh it out as you go on, with the amount of fleshing depending completely on your circumstances. Without further ado. • Scope : The   Business   and   Technical   requirements, probably some set of epics, user stories, and whatnot. This includes requirements for everything below. • Schedule : Prioritizing everything.   Everything . This ranges from the   Big (Ideas, Epics, …) to the ...

/via http://geek-and-poke.com/ Think about the way you “do code” at work”. You probably have a process, right? Something like “ grab a ticket from JIRA, create a branch, write code, squash commits, … ”, right? Now, think about the way others on your team code. Broadly speaking, they probably all follow the same system, except when they don’t. And now that you’re  really  thinking about it, you’ve probably got a couple of peeves around how, well, pretty much everybody else is (not) following process. I mean • Alice is great, except she sometimes forgets to squash commits • Bob is great too, except you have to keep reminding him to lint his code • Carol, wow, she’s stellar! Except…she never bumps the version number on checkin and so on. The thing is, pretty much all of them probably have exactly the same opinions about each other,  and you!  I mean, while  you  may think it’s ok to not comment your code in the really obvious cases, maybe Ali...