A Project Manager
-
I tried to express this issue way back (right after JABOT) (check skype log, search for scrum kanban etc…), not a freaking soul would listen.
Theese kinda things is what pisses me off.
Not a single fuck was given that day i tried to get this hammered through, now all of a sudden it is now done, and we have put our “PR” guy to do the job? When and by who was this decision made.
Im sure we have someone not that occupied and that might have more management experience to get onboard on this?
Previously experience shows that Chris and Devs not necessary get along…
Btw this is nothing personal against Chris, the only reason he ends up in the crosshair every time we discuss something is cause he seems to allways be the failover guy
when stuff needs doing. Which then again makes it halfass cause you can only juggle so many balls.
-
I seem to be doing this a lot recently, but I partially agree with svennand. I support this idea, and Chris’s version of the concept sounds much more community friendly, but I have ongoing concerns about the way in which decisions are made and the way things come to fruition. It’s important that people can have ideas and people can run with it but plans and decisions should be discussed rather than decided privately and implemented (albeit it softly).
For any community to work, everyone needs to be singing from the same songsheet/rulebook/procedure. I think it’s important that these procedures get decided early. I propose we nail down the decision making process and document it first. Document the flow of how ideas go from concept to reality. Next, you’d need to work out which projects fall under the PM jurisdiction, in theory this would be any project decided and agreed upon by the team via the process agreed upon above and none that haven’t been through the process. Giving clear demarcation between official/approved ideas and just standard ideas which haven’t been scrutinised thoroughly.
:)
-
Wow OK this is getting pretty heavy. I agree some kind of long term strategy and direction is needed. But be careful not to overdo the processes and rules. A primary agile principal is self organising teams with the authorisation to make decisions as required.
This is not a job for most people so where people have interests and ideas that’s most likely the best thing to actually work on. If people are interested in it it will get done more quickly and more time will be spent on it.
However saying that we do need so me kind of starting point to make sure a project is properly resourced and key features are prioritised. Again agile practices can allow us to get the %80 most important features done while only doing 20% of the work. (As the last few more complex features can be less important and likely more time consuming)
Short sprints releasing functionality at regular intervals. But this has to be from the guys actually working on the stuff. This may require a product owner rather than a project manager.
A representative that knows what they require of the end product and can make decisions rather than someone managing our time. Were not children.I’d be happy to help out as this is what i do for a day job. (Developer not product owner)
-
I’m not advocating that teams are weighed down with policy and compliance, that’s the last thing a team needs. Quite the opposite, I’m suggesting that get the details agreed upfront so the teams can get on with their job. If I use this thread as an example, between ML and Chris, the concept there is a clear difference of opinion, this muddies the waters, is the project manager we are looking for a tough love corporate psycho or a team building, motivational and organisational genius?
And just for svennand,
“If a man does not know what port he is steering for, no wind is favourable to himâ€
;)
-
I’ll do it.
If one or two others want to help me that’s would be kewl. I can dedicate at least an hour a day. Sometimes maybe more.
-
I’m not advocating that teams are weighed down with policy and compliance, that’s the last thing a team needs. Quite the opposite, I’m suggesting that get the details agreed upfront so the teams can get on with their job. If I use this thread as an example, between ML and Chris, the concept there is a clear difference of opinion, this muddies the waters, is the project manager we are looking for a tough love corporate psycho or a team building, motivational and organisational genius?
And just for svennand,
;)
Your right and I agree on the type or project manager that would be best would be the second.
But what I’m suggesting is that we just have a rough guess at the start of the project about what to work on first and what features may be required.
The reason for this is that at the start of the project we know less than at any other time. This is where traditional waterfall prince2 projects fall over.
All a team really needs at the start of a project is
-
A decision that the project is deemed to be worth while and the team can be dedicated to it.
-
Someone who has a vision for what is going to be created. Not necessarily all the specifics but the power to make decisions on what is required as the project rolls forward.
Im not trying to be awkward or spoil this thread (too late? lol) im just maybe voting against a traditional “Project Manager” and voting for a Product Owner as the difference is huge.
EDIT: Although this does not mean that there needs to be a consensus made before hand on if the project is worthwhile and how should/can work on it.
EDIT2: I think Calem would be great he has good people skills. All that would be required additionally would be an understanding of the particular specifics/vision of the project.
-
-
Wow OK this is getting pretty heavy. I agree some kind of long term strategy and direction is needed. But be careful not to overdo the processes and rules. A primary agile principal is self organising teams with the authorisation to make decisions as required.
This is not a job for most people so where people have interests and ideas that’s most likely the best thing to actually work on. If people are interested in it it will get done more quickly and more time will be spent on it.
However saying that we do need so me kind of starting point to make sure a project is properly resourced and key features are prioritised. Again agile practices can allow us to get the %80 most important features done while only doing 20% of the work. (As the last few more complex features can be less important and likely more time consuming)
Short sprints releasing functionality at regular intervals. But this has to be from the guys actually working on the stuff. This may require a product owner rather than a project manager.
A representative that knows what they require of the end product and can make decisions rather than someone managing our time. Were not children.I’d be happy to help out as this is what i do for a day job. (Developer not product owner)
Im not suggesting that it should be an papermill skyhigh for everything people wants to have done.
Im simple stating that getting an small “system” together to make it an more direct attack approach/structure both in time spent on each task, AND keeping it at an schedual would be pretty good and not to mention productive, this will also catch failing projects etc if someone gets bored or have their head under water. Then someone can scoop in an take over. This is much easier if you have an project segmented in sprints (scrum) if one branch failes/stops it doesnt slow down the whole production
Theres allready a bunch of awesome worktechnics invented out there (scrum,kanban and some others), check em out on youtube.
-
“If a man does not know what port he is steering for, no wind is favourable to himâ€
FIXED!
-
I agree at work we work in an agile way with sprints / retrospectives etc etc a little like scrum but less strict maybe more like kanban.
But I think your right we need some kind of overseeing board? what can prioritise different projects and help where needed.
-
I’ve gotten really use to Trello all ready, If someone is working on a project, I’ll need them here - https://trello.com/b/cfUhrHjM/team-todo
-
I can keep track of everything myself, but it would help everyone in the project if they were able to cross things off lists and move jobs around etc.
All the planning and major communication will be done as it’s always been, through the forum and skype, but project organisation should be done through Trello.
People can jump onto trello first thing in the morning, pick a project and away they go without needing to stall for any reasons.
-
Im more interessted in knowing exactly what resources Feathercoin has atm.
What skillset do people have, how much can they contribute?
An burndown chart might be as professional as possible, it still doesnt help if theres no teams behind it actually putting in the hours with it.
Just look at the feathercoin market for example, that on took FOREVER, and one of the main reasons for this is that bush had to do it all himself.
Quite an large task for one man, and by the end of it he was probably so feed up he felt feathercoin scratching his tonsils
-
I’m in favour of a board in control of multi Sig wallets voted in by the community (with veto powers to Bush if needs be). I’d even pay annually to be a part of the community.
-
svennand, can I add you to the list of resources (the team list been worked on). What can we use you for.
Kris, did you want to change your title… I’ve put you down as Merchant Development but if you can code maybe we put you down as General Development?
This team page is the first step in what I will try do. Give me a shot, and I’ll get a run down of everyone on the team, and ill put something together which will help with workload balance etc.
-
I’m in favour of a board in control of multi Sig wallets voted in by the community (with veto powers to Bush if needs be). I’d even pay annually to be a part of the community.
Definetly something I want setup… It’s been talked about as a bounty pool etc. I’ve seen it been talked about enough that ill add it to the to do list and we can start organising that.
-
Thanks. Am I correct in saying that the multi-sig technology is already there, it’s just a case of organising it? If we get this right we may be able to attract more developers with the bounties and it should add a layer of trust.
-
I’m not sure but I want to organise MultiSig if it’s not all ready in ftc, and also, we could do with 2FA in the wallet.
-
I’d welcome greater wallet security too. :)
-
I’ll have a chat with Bush and see if we can get this in next.
-
“If a man does not know what port he is steering for, no wind is favourable to himâ€
FIXED!
YES!
