Software Project MafiaIntro
Life in a software company is never dull, nor straightforward. And while common interests (not to mention job descriptions) should force people to work together towards a common goal, a web of lies, gossips and hidden agendas almost always makes that goal harder to reach.
You have been employed by "SVW Company"
, famous for large-scale software projects, with a rather small portfolio of products. This is a good opportunity for career development: a company where experience can be gained very fast.
But can you succeed in reaching your personal development goals in this environment? Or at least survive?FactionsGoodies - May or may not have some BTSC. WinCon: Eliminate those who stand in the way of the (public) goal completion.Baddies - Have BTSC and a group Night Kill. WinCon: Bend the wills of others and gain a comfortable majority to ensure smooth operation of their hidden agendas.List of rolesHead of Unit
- Promoted from within the software development team, he has gained the respect of those working in his unit. He knows how to resist pressure from above and is wise enough to see when things must not be sacrificed for pressure reasons only. Still likes to micro-manage whenever an opportunity arises.Product Manager
- Has been with the company for a long time and considers the product as his own baby. This often leads to bias against new implementation projects or market-driven modifications of development plans. But when push comes to shove, he will be around making any extra effort needed to ensure the end result fits.Implementation Project Manager
- Pure manager with little technical background, does not understand software complexity nor cares about it. Will do whatever needed in order to achieve short-term goals and nice Profit & Loss reports.Presales Writing Specialist
- Some technical background, advanced writing skills and a lot of experience in twisting the truth when needed. He is good on winning contracts, but often without a clue on how the others will actually achieve the features that were described in the offer. Which earns him a great deal of "sympathy" from the implementation team.Marketing Specialist
- Supposed to be a pair of the presales writer, can't stand his arrogance. Struggles to absorb all that tech information to make his marketing moves and speech target the right spots. Befriended a couple from the development team which provide him info and insights over long fruitful coffee breaks.Development Project Manager
- Extensive technical background and a keen mind driving the company's R&D. Essential for long-term goals. A control freak, really goes hay-wire when he feels the odds are stacked against him, seeing conspiracies everywhere.Business Analyst
- Struggles to match user needs incorrectly reported by the presales team with features incorrectly reported by the development team. New addition to the team, he feels almost useless at times, since the Product Manager already knows or guesstimates things based on previous experience, and people seem to override him almost all the time. He counters this by trying to be actively involved (lending a hand) in testing and developing the product features. Software Architect
- Part-time employee, great mind, little to no cooperation skills. He works his magic after the initial analysis, laying the software architecture to be used. But he is never around when questions arise and when compromises are reached (late at night or before deadlines).Senior Software Developer
- Excellent programming skills coupled with a lot of passion. However, he feels overwhelmed by the ammount of product features and design changes. And by that pesky junior asking questions all the time, tends to put him on hold from time to time.Junior Software Developer
- Keen mind, but far too little programming experience to make a difference. Will settle for what others tell him to do, which severely impacted his learning curve. Floats like a leaf in the wind.Graphic Designer
- Has a mind of his own, still considering beauty over simplicity or usability, which gets him into trouble most of the time. Whenever he gets his point across and reaches a compromise with the rest of team, a (usable) work of art is born.Software Tester
- Made almost obsolete by new automated testing technologies, must continuously struggle to meet his quota. Which leads to a lot of false positive and a general hostility towards him. Usability Tester
- He is usually called whenever things are already set in stone and proceeds to criticize everything starting from the User Interface and going back to incomplete analysis or incomplete testing. Lack of social skills does not help him earn any points.Rules
*Role names are public but all abilities are secret.
*There are only 2 factions, but alignment to factions is secret.
*The night post will show all actions played upon player names, without mentioning the roles that acted.
*Lynched players will have their role shown, but not their faction
*Feel free to interpret Role Descriptions and Night/Day posts as containing hints, but be warned that this may not be the case (no hints or even red herrings).
*Genders are all male for story purposes (to simply things for me - I'm still having troubles with writing genders in a foreign language). So, please don't consider those as discrimination.
*Outing or claiming an ability results in immediate loss of that ability (Note: saying "I know X is a goodie" does not out the ability and is allowed. Saying "I can spy a person" or "I spied X last night" means outing that ability and is not allowed)
*Outing or claiming a faction is (obviously) allowed
*Outing or claiming a role is (obviously) allowed and (obviously) discouraged by the mere existence of secret RID Killers (or worse).
*Ties result in all tied players being lynched. Any day.
*The order of actions (see OOA
is public: RID Kill >> Save > Redirect > Block > Kill >> Spy. Only RID kills are blocking, kills don't stop the target's action. Any roles that do not appear in that OOA have the same order as spies.