In: Computer Science
Please find the best methodology for each of the three software development personalities below and explain why you chose that one en each case.
“Show don’t tell” describes his modus operandi best. He is an enigma: not outright friendly or forthcoming, but he works surprisingly well on a team.
His motto? Don’t have doubts; just resolve the problem quickly and efficiently. This no-nonsense attitude makes him an absolute joy to work with.
He is outspoken and the unofficial project manager. He is the consummate ring-master, able to please both clients (the ferocious lions) and team members (the elephants that could easily trample him if they wanted).
works behind the scenes, receiving lower pay for what amounts to the same work
The half-cup speedster takes on multiple projects at once. He works much faster than most, but his amazing quantity is tarnished by its quality: his speed results from cutting corners and hacking core.
Unfortunately, much like the handwriting of physicians, his code is practically indecipherable. Should someone need to fix a problem that surfaces later, they will surely encounter difficulties. You can’t fix what you can’t read or understand.
Methodologies:
Methodology |
Focus |
Waterfall |
The linear and sequential approach to development |
Agile |
Continuous improvement and delivering better quality |
Critical path method |
Maximizing project activities and finding the shortest path (timeline) to task and project success |
Critical chain project management |
Optimizing resources usage |
Six Sigma |
Eliminating waste and improving processes and profitability |
Scrum |
Delivering higher quality |
Lean Six Sigma |
Customer-focused |
Kanban |
Customer-focused, fostering ongoing collaboration and continuous learning |
Scrumban |
Reducing waste, shorten lead time, turnaround time, and deliver higher quality products and services |
Lean development |
Reducing waste while maximizing output and increasing stakeholder value |
Crystal |
Improving project results by focusing efforts on the people-side of projects |
Dynamic systems development method |
Aligning projects with companywide strategic goals |
Adaptive software development |
Helping teams become more agile when dealing with change |
1.)
The ninja is a man of few words and keeps to himself. While similar to the hardcore geek, he has more in his life than code and work.
He is an enigma: not outright friendly or forthcoming, but he works surprisingly well on a team. Everyone notices his tireless nature but can’t figure out how he does everything so well and so quickly. There is much evidence of his work but little evidence that he did it. “Show don’t tell” describes his modus operandi best.
Never outwardly frazzled (try as you might to throw him off), he resolves problems quickly and efficiently, regardless of time or place. The ninja’s stealth sends chills down your spine, and he leaves you wondering how he managed to accomplish his feat.
A lone ranger, he gets the job done regardless of his status on the team or his relationship with other members. His motto? Don’t have doubts; just resolve the problem quickly and efficiently. This no-nonsense attitude makes him an absolute joy to work with.
So,Scrumban methodoly fits best for ninja personality as it also focus on :Reducing waste, shorten lead time, turnaround time, and deliver higher quality products and services
2.)
The clever ambassador is the face of the team. He is outspoken and the unofficial project manager. His knowledge of software development, project workflows and code theory is adequate, but he does very little of the actual programming or work.
He is quick to pick up leads and great at communicating with clients. He is the consummate ring-master, able to please both clients (the ferocious lions) and team members (the elephants that could easily trample him if they wanted).
In his supervisory role, the clever ambassador ensures that every project meets the requirements and satisfies the client. He is the go-between, representing the development team for the client and balancing client satisfaction with practicality.
Having to walk this tight rope, he often feels that he should be better compensated, despite never doing any heavy lifting (i.e. coding). He is the model who sits pretty in front of the camera selling the product, while the rest of the team (make-up artists, hair stylists, etc.) works behind the scenes, receiving lower payment for what amounts to the same work.
So,Kanban methodoly fits best for The clever ambassador personality as it also focus on:
Customer-focused, fostering ongoing collaboration and continuous learning
3.)
The half-cup speedster takes on multiple projects at once. He works much faster than most, but his amazing quantity is tarnished by its quality: his speed results from cutting corners and hacking core.
He feels that optimizing and checking code takes too long. His code is messy because he does not follow best practices and never makes use of object-oriented programming (OOP).
Amazingly, despite his code looking like a minefield, the product works just as intended. Cutting corners is generally not good practice, but in an impossible crunch, the half-cup speedster might be the person for the job.
Unfortunately, much like the handwriting of physicians, his code is practically indecipherable. Should someone need to fix a problem that surfaces later, they will surely encounter difficulties. You can’t fix what you can’t read or understand.
So,Critical path method methodoly fits best for The half-cup speedster personality as it also focus on:
Maximizing project activities and finding the shortest path (timeline) to task and project success