Milestone 3
Persona Profile01 - Jack Smith
Software developing engineer at Google Inc
Technological
Jack has a two-year old Dell computer, which he takes with him wherever he goes. He takes it to attend meetings, to give reports and even when he provide trainings to new employees in his team. Also, there is a three-year old desk computer at home, which he shares with his family. He always spends all of his conscious time on a computer, which is typically 18 hours per day. He uses the computer to exchange email with colleagues and friends, write codes and reports, read news and play games. The programming tools he prefers are Visual C++ and Eclipse for the language of Java. He welcomes diverse software, which can provide him with information about current user preferences and software developing trends.Personal Description
Jack is 30 years old and he works 45 ~50 hours a week on projects in his company. He usually spends most of his time on programming and communicating with other team members about the methods of answering certain features of some software they’re developing.Each day Jack keeps an eye on the new technologies appear in the market and he has a lot of friends who work in diverse software companies throughout U.S. They know each other’s job and company features, and often they talk about their recent project focuses as well as the merits and shortages of some current software. They like new ideas and are excited when hear concepts fresh to them. Jack considers himself and people around him are those most clever in the world and they’re fond well-designed technologies, which can match their efficiency and intelligence.
Jack values simplicity. He likes to draw his ideas when communicating with other team members since it’s more intuitionistic and efficient to convey what jump into his mind. Although most of his time is spent on programming, the biggest challenge may still be providing an efficient idea of managing different modules and make them easy to fix and flexibly adaptive. When there is divergence about the arrangement of data flow across modules during a meeting, he feels that whiteboard are inefficient since you can only erase or add new pictures instead of just “moving” symbols already on the whiteboard.
When it comes to the projects he manages, in each stage of developing, he takes time to clarify the intended purpose and the overall demands of the project to the whole team. But during each stage there may appear new demands to answer additional feathers or accomplish in another way, to cope with fluctuations throughout a project Jack has to make a thorough record of the whole process, which includes collecting information from each meeting and embed key solutions into a specific project management file.
Thus, from showing the blueprint of how different modules work consistently together to each module’s function and applied methods, Jack has to coordinate all the team members and be informed of their working status through each morning’s meeting.
And often the case, software bugs may influence the process originally arranged, under such situation the team has to figure out the problem together. But, sometimes it is hard to solve the problem because there are a lot of possibilities and the whole team may discuss for a long time without achieving a consensus. In the circumstance, Jack has to record each possibility his team suggests and rule out one by one according to their analysis. For those unanswered question, people may have idea or distinct opinion after the meeting, they will find way to discuss with Jack or email Jack; then, Jack reports such feedback to the whole team in the next meeting.
Besides, to fix communications between modules may be hard and the interfaces between modules may not that match since they are assigned to different team members. Jack used to
To keep energetic, Jack encourages other team members to talk about using new technologies to accomplish some features, they give bold assumptions and complement plans for the disadvantage of current solutions. And those brainstorm part in a meeting is greatly valued by Jack since each idea mentioned is unique and intelligent. Jack used to quote some meeting episodes to teach new employees in his department.
Role
Jack spends a lot of his time on programming and working out specific modules of a project to answer the clients’ expectations. He is very experienced in the industry and especially care about catching up new trends in the market, thus he always suggests new ideas at each meeting. He is one of the most important idea contributors to the department.Since he has been working in the Department for 5 years, he is responsible for the organization of some projects which he has more knowledge of than other colleagues in his team. When there are new employees and interns allotted in his department, he acts like a mentor to provide suggestions to the inferior. He teaches them about the working flow here and each one’s general responsibility. He gives them instructions on how to use new tools and methods to accomplish software features required, and discuss with them about tentative ideas.
Whenever it comes to programming, you cannot get rid of debugging. So in the worst case Jack may spend as much time of programming as solving bug problems with the whole team. Under the cases when some former released software needs to be maintained, Jack has to reverse those programming to fix its functions.
Tasks
- Provide efficient accomplishment of software developing with high quality.
- Coordinate with people around a project he manages and train new employees.
Goals
- Make sure the accomplishment of certain features using the best methods.
- Make sure the different modules match ideally.
- To make a bug free program which can fully answer its requirements.
- Make sure the whole program goes smoothly, including coordinating among team members about their responsibilities, communications and information flow through out a project.
Scenarios
Scenario I - Can You Make Whiteboards Portable and Electronic without losing what is great about them?
At 9:00am, Jack goes into the meeting room. He talks to his team about their new secret project, feeling confident and excited. Jack has an idea in his mind already and would like to get the understanding and comments of his peers. Jack makes a new MeetingBytes meeting, creates a new whiteboard and waits for all of his peers to plug in to the software to present his ideas. First, he makes several sequences of drawings on the MeetingBytes electronic whiteboard like screen, which can be shared among each attendant’s laptop. He feels so satisfied because he has created many custom Google shapes easily and can use them with existing common shapes. This is better than a regular whiteboard where sometimes only the drawer knows that things are. Also, by communicating this way he doesn’t need to move to the side of the whiteboard after he finishes drawing because everyone can see the same whiteboard clearly on their laptops. The whiteboard functionality is so advanced that he can move his drawings around to different locations easily and change the size, color, and shapes as much as he wants. Anyone can comment or make a copy of the board to doodle on their own without impacting the drawing that Jack has made. accordingly and change the size, color, and comments as long as necessary. You don’t even need to worry about the spelling mistakes, which occur often using a regular whiteboard. The program is ideal for Jack and his team since they all enjoy typing on their laptops and sketching on the whiteboard. Jack is even able to save different components of the whiteboard as separate files since it appears as though this project could go in multiple directions. His team prefers MeetingBytes to the regular whiteboard because the process feels more like prototyping to them. They can all access the whiteboard files from the MeetingBytes server after the meeting is over as well.
Scenario II - Can you help me refer to points in the meeting I attended that I know are useful, but don’t remember word for word?
Later on at 11:30 am, Jack decides to discuss some ideas with his team. He knows that his colleague, Aaron said something about GoogleDocs at the meeting earlier. He doesn’t quite remember what was said, but he knows that it would be useful for the current conversation. Luckily, the 9:00am meeting was captured using MeetingBytes. He opens up the MeetingBytes software and navigates to the MeetingDatabase Index. He selects all of the meetings in the meeting folder GoogleSecretProject and searches for the word GoogleDocs. He is glad that he captured the meeting using MeetingBytes because he easily pulls up the record of the meeting at the time stamped with YouTube.
Check out other personas:
Tina Rogers | Matthew McGraw | David Wang
