Capstone

All conflict should be resolved privately. True:False

False

It is possible to calculate the critical path for a project knowing only the tasks, their dependencies and their *effort* estimates. True:False

False

There can be only one critical path in the schedule. True:False

False

User and customer are synonyms. They refer to the same person or role. True:False

False

Is Destination == to requirements? True:False

False Destination != requirements.

A team is better off without conflict. True:False

False Effective teams include members with diverse thinking styles, approaches, experience and knowledge. You want differences of opinion. It will increase a team's energy level and provide greater creativity through myriad viewpoints. The ideas that do survive are stronger as members are challenged to elaborate on their ideas so that others better understand them.

In a Chief Programmer CPT ( Lead Programmer ) team what does the Librarian do?

Librarian: Although an important role in the 1970's when the chief programmer team concept was first introduced, the role of of librarian is an anachronism today. During the 1970's the librarian was responsible for managing the artifacts of the software development process including punch cards, source code listings, test results, and documentation. Today many of the functions of the librarian have been superseded by powerful interactive work stations and automated configuration management systems.

The Software Requirements Specification (SRS) shouldn't specify design but it is OK for the SRS to restrict or limit certain design options. True: False

True Yes, this is the purpose of constraints.

In the context of a software project, the term "going dark" refers to the situation where a developer stops participating on a project. He or she stops going to meetings and stops writing code. True:False

False False. Going dark is where a developer continues to write code but doesn't check it in or make it available for review.

Is a project success is more than delivering desired features at an acceptable level of quality according to an agreed upon schedule and budget? True:False

True Long-term success is meeting schedule, budget, feature and quality objectives without sacrificing your people.

Which type of prototype are you more likely to create if your goal is to test the technology stack used for your product?

Vertical prototype

What is vertical prototyping?

Vertical prototypes gives full functionality for a few features.

Software requirements often unfold in progressive levels of detail. Identify 3 different levels of requirement specification from the abstract to the specific

Vision, features, use cases

In which of the following life cycle models are you more likely to find predictive planning? - Waterfall - Spiral - Evolutionary Prototyping - Code and fix

Waterfall

A Use case includes the ______ but not the _____

What but not the How

What is a functional requirement?

What is the software suppose to do? What functions are expected from the software?

In the elements of a project charter what purpose?

What problem or opportunity does the project address?

Does working alone increase your risk of failure? Yes:No

Yes

Is it possible to trust and respect someone you aren't friends with? Is it possible to trust and respect someone you don't like?

Yes, Yes

Is it acceptable for the development team or requirements analyst to suggest modifying the requirements to reuse existing components. Yes:No

Yes, small differences in functionality may be worth the reduced cost of reusing existing components. The development team shouldn't dictate requirements but they can help the client understand the options and their costs.

A Use case represents a ___ of the system.

model

Project Initiation clarifies ______

project objectives

Use cases are a good form of the system that is ___ and ___ for a end user

readable, understandable

What are some characteristics of a strong team?

varying viewpoints, experiences, skills and opinions.

What is the ricks and obstacles to success elements of a project charter?

what are the potential problems (technical and non-technical) that may occur

What is the scope element of a project charter?

what is and is not included in the project

In the Norming stage of team development what are some of its characteristics?

"During the Norming stage of team development, team members begin to resolve the discrepancy they felt between their individual expectations and the reality of the team's experience." Team members "accept the team, the team ground rules or "norms," their roles in the team, and the individuality of fellow members." Team members find "ways to raise and discuss differences of opinion effectively." "If the team is successful in setting more flexible and inclusive norms and expectations, members should experience an increased sense of comfort in expressing their "real" ideas and feelings."

In the Performing stage of team development what are some of its characteristics?

"The team is now an effective cohesive unit." Productivity is high; need for supervision is low. Members feel satisfaction in the team's progress. "Team members are able to prevent or solve problems in the team's process or in the team's progress" Changing circumstances may cause a team to revert back to an earlier stage. For example, if leadership changes the team may revert to the forming stage.

Which type of requirement is more likely to be discrete, that is, completely present or completely absent? - Functional Requirement - Constraint - Both of the above - Non-Functional Requirement

- Both of the above

What is a constraint

limitations on possible solutions

simple intuitive means what?

means for capturing system requirements

Having clear objectives helps to ensure _____

project success

In Project Initiation the Managing Expectations pertains to_____

- Agreement on goals - Project success criteria

A project is worth pursuing if it is____?

- Needed - Feasible - Optimum

What are the 3 types of teams?

Chief Programmer CPT ( Lead Programmer ) Egoless Programming Teams Hierarchical Team

What is horizontal prototyping?

Horizontal prototypes keep the features but eliminates the depth of the prototype.

What should you do when your compromising?

If collaboration does work, compromise may be appropriate. With compromise, everyone gives up something and everyone gains something. This is sometimes called a lose-lose strategy because everyone gives up something.

What does conflict bring?

It brings creativity and helps avoid groupthink

Which type of requirement is more likely to be present to a degree?

Non-Functional Requirements

Problems first start to appear during what stage of team development?

Storming

What does a Writer or Editor do?

The writer is responsible for authoring or editing system documentation including user guides, system help text, release notes, etc.

The actor of a use case may be a user or external software system. True:False

True

What is the success criteria element of a project charter?

what constitutes project success?

The release plan is likely to change over the course of the project. True:False

True

The slack time for all of the tasks on the critical path is zero. True:False

True

Why do Use cases represent a model of the system?

Because they present an abstract view of the system from a specific viewpoint. The viewpoint is that of the end user.

What should you do when your collaborating?

First look for a solution that meets everyone's goals—a win-win solution.

Who can grant authority to proceed with a project?

Formal authority to pursue a project is granted from a person or entity external to the project who is high enough in the organization to authorize the expenditure of resources towards the project.

What are the 4 stages of team development?

Forming Storming Norming Performing

With a homogeneous group,

Group think is likely to increase and conflict is likely to decrease

Following an Agile methodology makes it ___________ for a team member to go dark.

Harder On an agile project a team member can't go dark beyond an iteration because teams show results at the end of each iteration.

What are the characteristics of a Functional team?

Healthy relationships/interactions Efficient and effective Energizing Feeling of unity, trust and shared purpose

How can you reduce social loafing?

Increase identifiability. People are more motivated when their individual ideas and output are identifiable (assignable to them). Decreasing team size is one way to increase identifiability. Set challenging, meaningful and individual goals. Reward team members for performance. If goals aren't challenging, not all members have to work at 100%. If goals aren't individual, there is a tendency to assume someone else will do some or all of the work. Allow group members the freedom to choose their roles and/or tasks.

Is the Ringelmann Effect more or less of an issue as team size increases.

More

Should you Compromise before you Collaborate? Yes:No

No Collaborate first then compromise

Project Initiation clarifies?

The project objectives

What does a User Interface Designer do?

The user interface (UI) designer works with the product manager and requirements analyst to define an appropriate user interface. The user interface designer is responsible for the detailed implementation of the UI and ensuring a consistent style is used throughout the system.

In the elements of a project charter what stakeholders?

Who are the people with an interest in the outcome of the project? What are their needs and expectations. (Key stakeholders include: project sponsor, project manager, customer, and users.)

Project initiation is concerned with what?

With defining the destination

Does a project have to be managed?

Yes

Writting a Use case is a what?

simple intuitive

Use case modeling is a very ______ concept with ________

simple, surprising value

Techniques for dealing with risk include risk avoidance, risk reduction or mitigation, risk transfer or sharing and risk retention or acceptance. Which of the following is an example of risk transfer? - A team creates a UI prototype in order to avoid the risk of delivering a system with an unacceptable UI. - A consulting company decides not to write medical device apps for fear of litigation. - Despite the high probability of not finishing on time, the team decided the pursue the project anyway because of the huge financial payoff if they were to finish on time. - A business owner wants to use Linux but is concerned about potential intellectual property lawsuits from companies claiming ownership of technologies on which Linux is based. Because of this, the business owner decides to use company A's brand of Unix because company A is willing to offer indemnification for its Unix users.

- A business owner wants to use Linux but is concerned about potential intellectual property lawsuits from companies claiming ownership of technologies on which Linux is based. Because of this, the business owner decides to use company A's brand of Unix because company A is willing to offer indemnification for its Unix users. The term "risk sharing" is sometimes preferred over "risk transfer" because in most cases the risk is never fully transfered. For example, if the indemnifying company goes out of business, you still could be liable for infringement.

Which of the following is not normally found in a requirements document? Check all that apply. Only one may apply. - Written use cases and/or a use case model - Communication Plan - Budget - Mandated Constraints - Non-Functional Requirements - Schedule

- Budget - Communication Plan - Schedule

In the Functional part Project Organizational Structures what are some of the advantages?

- Close physical proximity of specialists promotes sharing of expertise and knowledge within a discipline. This improves individual as well as institutional capability. - Promotes continuous process improvement, specifically the control and evolution of standards and methods. - Offers staff a stable work environment with improved career opportunities for specialists. - Specialized skills can be leveraged across multiple projects. This results in economies of scale and more efficient use of critical resources.

Techniques for dealing with risk include risk avoidance, risk reduction or mitigation, risk transfer or sharing and risk retention or acceptance. Which of the following is an example of risk retention? - A team creates a UI prototype in order to avoid the risk of delivering a system with an unacceptable UI. - A consulting company decides not to write medical device apps for fear of litigation. - Despite the high probability of not finishing on time, the team decided the pursue the project anyway because of the huge financial payoff if they were to finish on time. - A business owner wants to use Linux but is concerned about potential intellectual property lawsuits from companies claiming ownership of technologies on which Linux is based. Because of this, the business owner decides to use company A's brand of Unix because company A is willing to offer indemnification for its Unix users.

- Despite the high probability of not finishing on time, the team decided the pursue the project anyway because of the huge financial payoff if they were to finish on time. The team is accepting the risk of not finishing on time.

What are the benefits of capturing requirements with use cases?

- Excellent ROI - Simple and intuitive method of recording functional requirements. - Readable by end users but also detailed enough for programmers to implement and testers to write test cases. - Systematic and semi-formal representation helps ensure requirements are complete and well understood.

What does a Use Case exclude?

- Excludes User Interface Detail - Excludes Implementation Concerns

Other advantages of use cases are?

- Expressing requirements in term of goal-oriented user interaction avoids gold plating or adding features that aren't likely to be used. - Can be used to drive the development process. (Iteration planning, validate architecture,

What are the 3 types of Project Organizational Structures?

- Functional - Project - Matrix

In the Project part Project Organizational Structures what are some of the disadvantage?

- Inefficient use of critical resources (human and material). - Increased cost because of duplication of effort. - Difficult to have all required resources assigned to the project. When the resources are assigned it creates the other problem of making efficient use of them. - Increased anxiety for project members towards the end of a project as they contemplate their future. - Inhibits the development and transfer of expertise from one project to the next.

In the Matrix part Project Organizational Structures what are some of the disadvantage?

- It is a two-boss system. When the project manager contracts for services from a functional unit, the staff in the functional unit working on the project will have two bosses. This is a source of conflict when project goals interfere with the goals of the function unit. For example, on time delivery may conflict with the goal of continuing education and staying current with technology. - It requires additional overhead for creating work packages. The work performed by functional units must be fully specified in work packages and tracked. This creates an additional external interface that has to be tracked and managed. - Divided authority and responsibility between project managers and function managers creates a potential for conflict.

Which of the following behaviors by a technical staff member would be considered unethical if carried out during a software requirements gathering meeting? Check all that apply. Only one may apply. - Overestimating the cost of implementing a feature because it would not be fun or interesting to implement - Overestimating the cost of implementing a feature because budget and schedule target dates are unrealistic and it would even things out - Giving a ballpark estimate (clearly designated as such) for the cost of implementing a feature without knowing precisely what the costs and risks are. - Mentioning the option of changing the file format of exported data to make it harder for the data to be used with competing products

- Overestimating the cost of implementing a feature because it would not be fun or interesting to implement - Overestimating the cost of implementing a feature because budget and schedule target dates are unrealistic and it would even things out "mentioning the option of changing the file format of exported data to make it harder for the data to be used with competing products" is a judgement call. It depends on what framework you are working from. The IEEE Software Engineering Code of Ethics and Professional Practice states that: 1. Software engineers shall act consistently with the public interest. 2. Software engineers shall act in a manner that is in the best interests of their client and employer consistent with the public interest. You could argue that changing the format would not be in the public interest because it would reduce interoperability. However, you aren't really harming the public because they have the choice to not user your product.

In Project Initiation the Authorizing the Project pertains to_____

- Project justification - Assigning authority

In the Project part Project Organizational Structures what are some of the advantages?

- Project manager has complete authority and control over the project and project resources. This provides a single source for decisions and project control. - Project personnel identify with the project which results in improved motivation and morale during the active phase of the project. - Interfaces between organizational units are minimized because most work is performed within a single group.

Listing in order of the highest to lowest. In what order does the Project Manager have the most authority and the Organization has the most structure?

- Projected - Matrix - Functional

What are the elements of a project charter?

- Purpose - Stakeholders - Goal and Objectives - Features - scope - assumptions - success criteria - risks and obstacles to success

What are some benefits of working in a team?

- Shorter schedules. When a team works well together it is able to accomplish more than its individual members can working independently. - Complementary skills. No one individual may have the skills and expertise necessary to complete the work.

In Project Initiation the Preliminary Planing pertains to_____

- The Goals and objectives - Scope

Which of the following statements is a constraint of the type you would expect to find in a software requirements specification? - The database must be open source - The project must be completed by 2/12/20xx - The user interface must be intuitive and easy to use. It must pass the usability test outlined in the next section. - The system must keep a record of every transaction that changes the database

- The database must be open source The statement "The project must be completed by 2/12/20xx" is a constraint on the project. It is more appropriate for the project charter and/or project plan.

In the Functional part Project Organizational Structures what are some of the disadvantages?

- There is no central point of authority and control for the project. Project coordination is distributed. - The loyalty of staff is with their functional unit rather than the project. - When there are multiple projects there may be competition for resources and arguments over priorities.

What does a Use Case include?

- User (Actor in Use Case Parlance) - Goal - Interaction

What are the main sources of the Ringelmann effect? Check all that apply. Choices: - loss of motivation when team members feel the task is impossible - loss of motivation when team members feel their contributions aren't indentifiable - loss of productivity due to inability to coordinate the work of multiple individuals - loss of productivity due to increased socialization among group members

- loss of motivation when team members feel their contributions aren't indentifiable - loss of productivity due to inability to coordinate the work of multiple individuals

What is the Process for writing a Use Case?

1) Identify actors 2) Identify the goals associated with each actor. Make each goal a use case. 3) Prioritize use cases 4) Elaborate use cases 5) Create a structured use case model (UML Diagram)

Four analysts attend a design review meeting lasting 2 hours. One analyst didn't make any meaningful contributes during the review. What was the duration of the meeting? How much effort was expended during the meeting? (Assume the standard definition of the term effort used when planning a project.)

2 hours; 8 hours It doesn't even matter if the analyst not making any comments did or didn't prepare. He or she participated which represents 2 hours of effort. You can expend effort without getting results.

Techniques for dealing with risk include risk avoidance, risk reduction or mitigation, risk transfer or sharing and risk retention or acceptance. Which of the following is an example of risk avoidance? - A team creates a UI prototype in order to avoid the risk of delivering a system with an unacceptable UI. - A consulting company decides not to write medical device apps for fear of litigation. - Despite the high probability of not finishing on time, the team decided the pursue the project anyway because of the huge financial payoff if they were to finish on time. - A business owner wants to use Linux but is concerned about potential intellectual property lawsuits from companies claiming ownership of technologies on which Linux is based. Because of this, the business owner decides to use company A's brand of Unix because company A is willing to offer indemnification for its Unix users.

A consulting company decides not to write medical device apps for fear of litigation. Risk avoidance includes not performing some activity to avoid the risk altogether.

Which of the following best illustrates the practice of resource leveling: - A family on vacation monitors their spending closely so as not to run out of money before the scheduled end of the trip. - A family planning a vacation makes an initial schedule of activities. Upon review they decide to move around a few of the planned activities in the schedule in order to better balance the number and duration of activities planned for each day. - A family going on vacation decide at the start to give each family member an equal amount of spending money. - A family planning a vacation set goals and objectives for their vacation at the start and then allocate their time and money according to the priorities of their established goals and objectives.

A family planning a vacation makes an initial schedule of activities. Upon review they decide to move around a few of the planned activities in the schedule in order to better balance the number and duration of activities planned for each day.

What is a milestone>?

A milestone is a significant accomplishment during the life of a project

Milestones plus their expected achievement dates form _____

A preliminary schedule

What is Groupthink?

A psychological phenomenon that occurs within a group of people, in which the desire for harmony or conformity leads to a loss of individual creativity, uniqueness and independent thinking. Group members try to minimize conflict and reach a consensus decision without critical evaluation of alternative ideas or viewpoints.

Techniques for dealing with risk include risk avoidance, risk reduction or mitigation, risk transfer or sharing and risk retention or acceptance. Which of the following is an example of risk reduction? - A team creates a UI prototype in order to avoid the risk of delivering a system with an unacceptable UI. - A consulting company decides not to write medical device apps for fear of litigation. - Despite the high probability of not finishing on time, the team decided the pursue the project anyway because of the huge financial payoff if they were to finish on time. - A business owner wants to use Linux but is concerned about potential intellectual property lawsuits from companies claiming ownership of technologies on which Linux is based. Because of this, the business owner decides to use company A's brand of Unix because company A is willing to offer indemnification for its Unix users.

A team creates a UI prototype in order to avoid the risk of delivering a system with an unacceptable UI. Risk reduction can take the form of reducing the probability and/or impact of the risk.

What id the definition of a team?

A team is two or more individuals working together with a shared commitment to a common purpose in an environment of mutual accountability.

Which of the following statements are true? Check all that apply. Only one may apply. - A use case can have at most one actor. - A use case with multiple scenarios must have multiple actors. - A use case with multiple actors must have multiple scenarios. - A use case can have multiple scenarios and multiple actors. - Each scenario of a use case will have a different actor.

A use case can have multiple scenarios and multiple actors.

What is a Use Case?

A use case is a narrative description of a goal-oriented interaction between the system under development and an external agent

Exploratory projects with high uncertainty are best suited to what type of planning?

Adaptive

You can plan and schedule work at different levels of detail. What are the advantages of planning detailed tasks rather then broad objectives? Choices: - More control over the project (more tasks means more opportunities for feedback and course corrections that can be made sooner) - Better estimates of overall effort - More likely to meet deadlines because schedule slips are identified sooner - all of the above - 2 out of the first three above

All of the above

What is a non-funcational requirement?

All other requirements including qualitative aspects of the software. I.e. usability, performance, reliability, portability, etc.

Give an example of a situation where formal communication is more appropriate than informal communication.

An example informal communication channel that should be discouraged is having marketing (or any stakeholder for that matter) informally ask developers to add certain features. Changes to requirements should go through formal change control procedures.

In a Chief Programmer CPT ( Lead Programmer ) team what does the Auxiliary Programmer do?

Auxiliary Programmer: Auxiliary programmers may be added to the project when the volume of code is more than what the chief programmer and backup programmer can manage within the allotted time. Auxiliary programmers may also be added to perform specialized coding. For example, if the project is to write a compiler, auxiliary programmers may be added to write code optimizing routines. The chief programmer directs and integrates the results of auxiliary programmers. This reduces communication and coordination and helps ensure the conceptual integrity of the final product.

In a Chief Programmer CPT ( Lead Programmer ) team what does the Backup Programmer do?

Backup Programmer: The backup programmer is the alter ego of the chief programmer. He or she is a senior-level engineer, but probably has less experience than the chief programmer. The backup programmer is there to provide a second opinion on items requiring professional judgment and to fill-in for the chief programmer as needed. The backup programmer not only assists the chief programmer, but also learns from him or her. Software development is often characterized as part science and engineering, part art, and part craft. To the extent that software development is a craft, the organizational structure should support some type of apprenticeship training. The relationship between chief programmer and backup programmer is an excellent example of how apprenticeship training can be instituted.

In the Matrix part Project Organizational Structures what are some of the advantages?

Because the matrix structure combines elements of the functional and project structures it retains most of their advantages: - There is a project champion--someone with authority and responsibility for the project as a whole. - Critical resources can be shared between projects resulting in improved economy of scale. - Provides for continuity and stability between projects. - Provides for improved technical expertise and standards.

A throw away prototype can be used to:

Better understand requirements Resolve technical risks Explore design alternatives

Why is it necessary to identify the dependencies between project tasks? Choices: - To calculate the critical path through the schedule - To create schedules. Task dependencies limit the times when tasks can be scheduled. - Both of the above.

Both of the above.

Larry and Mindy are assigned separate but equally difficult tasks (for example, both are asked to write a module that turns out to be 100 lines of code). Mindy completes her task by working 6 hours over 2 days. Larry completes his task by working 8 hours over 2 days. What can you say about this situation? - Both tasks took the same effort. - Both tasks took the same duration - Larry and Mindy are equally productive - 2 and 3 - 1 and 2

Both tasks took the same duration Answering this question correctly depends on sorting out three separate concepts: effort, duration and productivity. Productivity is output per unit of input. Mindy's productivity is 1/6 of a module per hour. Larry's productivity is 1/8 of a module per hour. Effort estimates assume a certain productivity. The actual effort is the total amount of time spent working on the task. Two people working on separate but equally difficult tasks can spend unequal amounts of effort.

What is going dark?

It is a term used to describe developers that go off on their own for long periods of time to perfect some work before springing their masterpiece on an admiring public.

In a Chief Programmer CPT ( Lead Programmer ) what is the organizational structure for the group?

Chief Programmer Administrator ----------- Backup Programmer Tester ---- Technical Writer ---- Other Programmers

In a Chief Programmer CPT ( Lead Programmer ) team what does the chief programmer do?

Chief Programmer: For maximum conceptual integrity the chief programmer has broad and deep responsibilities. The chief programmer makes most of the technical and project-related decisions. He or she is responsible for requirements, system specification, the complete system design, implementation of critical modules, and the first draft of system documentation. The chief programmer is supported by a small group of functional specialists. Subtasks are assigned to these specialists and the chief programmer integrates their results. The CP relies on good tools and a skilled support staff in order to manage the workload.

Which type of problem solving should you attempt first?

Collaboration problem solving

What are the two main reason the Ringelmann Effect takes place?

Communication and coordination problems (discussed in CS449), and Loss of motivation aka "Social Loafing"

There are two companies that provide satellite launch services. Company A has had 12 catastrophic failures in the last 100 launches and company B has had only 10 catastrophic failures in the last 100 launches. One advantage with company A is that it can carry larger less expensive satellites. If the cost of a satellite to be carried by company A is $200 million and the cost of a satellite for company B is $250 million, which launch carries the least risk?

Company A because the risk exposure with company A is smaller than it is with company B The risk exposure for a launch with company A is $24 million, for company B it is $25 million.

What is a constraint requirement?

Constraints are limits place on design and implementation options.

Which of the following are you least likely to find in a project charter? - Goals and objectives - Rough schedule and budget estimates - Project success criteria - Detailed requirements - Constraints and assumptions - Major risks and obstacles to success

Detailed requirements

What is Project Planning?

Devises a course of action for accomplishing the goals and objectives decided on during project initiation

Project Planning is concerned with what?

Devising the optimal path to the destination

What are some responses you could do if a conflict arises?

Do nothing Private conversation between affected members Impersonal mention during group meeting. Discuss general concerns (no names) at group meeting In-group confrontation. Airing of grievances (professionally of course) during group meeting Dismiss members from team. Last resort.

What are the assumptions elements of a project charter?

Does project success depend on certain conditions outside of the control of the immediate project team? (Something you "wish" to be true, can't be an assumption.)

Resource leveling is the practice of staffing with individuals at a similar skill level to make scheduling easier. (If individuals are at the same skill level they can be moved from one task to another without re estimating the time needed to complete the task.) True:False

False Staffing a project with individuals at the same skill level might make resource leveling easier, but resource leveling is not a staffing issue. Resource leveling is a process for leveling out the hills and valleys in a schedule (i.e. moving tasks around in the schedule and reassigning tasks so that work effort is evenly distributed among days and equitably among individuals) Note, resource leveling may also be needed to resolve conflicts for resources.

In the elements of a project charter what features?

Features are the main client-valued functions of a product.

Consider the risk of personal injury or material loss when traveling by car. Which of the following best illustrates a contingency plan for this risk. - Purchase a car with antilock brakes - Wear a motorcycle helmet when you drive - Walk or ride a bike instead - Find a good hospital and auto body repair shop

Find a good hospital and auto body repair shop Only D is a contingency plan. The others are techniques for reducing risk. The first reduces the probability of an unsatisfactory outcome. The second reduces the magnitude of the loss associated with an unsatisfactory outcome. The third arguably does a little of both. Only D is a contingency plan. A contingency plan is a plan of action to be taken should the risk actually becomes a problem.

In a Egoless Programming Team what kind of team does it form?

Forms a democratic programming team.

In a Hierarchical Team Structure what kind of team does it form?

Forms a democratic programming team.

What does a Build Coordinator do?

Frequent builds and testing are software engineering best practices. Regular builds and testing ensures that errors are found early and the overall quality of the system remains high. The build coordinator is responsible for integrating the work of developers, building a driver and running integration tests. Builds are performed according to a regular schedule, usually daily or weekly.

What are the types of Requirements?

Functional Non-Functional Constraints

If I assigned a team grade based on the collective work of the team and did away with individual point allocations (everyone gets the same grade), would social loafing likely go up, down or stay the same.

Go up

In the elements of a project charter what goals and objectives?

Goals and objectives define expected project outcomes. Objectives should be specific and measurable. Goals can be more grand and inspirational. Preliminary schedule and budget estimates.

What are the 4 leadership styles the goes with the 4 stages team development?

Integrative Drirective Coaching

When Obtaining Formal Authority to Proceed with a project what does the needed category cover?

It addresses a legitimate business problem or opportunity.

Project initiation does what for a project?

It announces and legitimizes the project by formally assigning authority to the project manager.

What is Project Initiation?

It determines destination. Defines and gets agreement on project's goals and objectives

What is a deliverable?

It is a tangible result.

How do you avoid group think?

Make it a practice to have individuals brainstorm a list of alternatives in private before discussing any course of action in public in detail.

What is the relationship between throwaway and non-throwaway prototypes and vertical and horizontal prototypes?

No relationship. All 4 combinations valid: throwaway-horizontal; throwaway-vertical; non-throwaway-horizontal; non-throwaway-vertical

Consider a risk management plan with two risks: Risk A has a 50% chance of becoming a problem and the consequences would be moderate. Risk B has a 30% chance of becoming a problem and the consequences would also be moderate. You spend proportionally more time and money mitigating the impact of risk A verses risk B but it turns out that risk B is the one that actually becomes a problem. Did you do anything wrong? If on a future project the exact same two risks reappear with the same probabilities of becoming a problem and the same expected loss, should you do anything different? Yes:No

No, you did nothing wrong. Probabilities are probabilities not certainties. There is no indication that the original estimates were wrong. Note, the question says "the exact same two risks reappear with the same probabilities of becoming a problem and the same expected loss". You might do something different if the risk exposure shifted to say that B is more risky, but that's not the scenario given.

Is the following an acceptable ground rule for a team? "No critical/harsh behavior towards other members."

No. It's too vague. What is considered harsh will vary among team members. You haven't really set any ground rules.

What are the characteristics of a Dysfunctional team?

Poor communication and social conflict Inefficient and less effective Draining Members primarily look out for their own self-interests

A project with well-understood and stable requirements is best suited to what type of planning?

Predictive

What are the primary functions of project Initiation?

Preliminary Planing Managing Expectations Authorizing the Project

What are the two components of risk exposure?

Probability of a risk turning into a problem and the potential impact or loss associated with the problem

What does a Programmer/Developer do?

Programmers are responsible for detailed design, development, and unit testing of software. Because programmers have intimate knowledge of implementation options and opportunities for reuse, they may also be asked to estimate feasibility or cost of implementing different features.

In a Chief Programmer CPT ( Lead Programmer ) team what does the Project Administrator do?

Project Administrator: The chief programmer should have the last word on all project decisions but may not have time for day-to-day project management responsibilities. For larger projects it may be necessary to add a part-time or even full time project administrator who can take responsibility for budgets, scheduling tasks and managing the day-to-day administrative details of the project. This is one role that might be hard for the larger organization to accept. Many organizations are not accustom to having administrator roles subordinate to technical ones.

In a Hierarchical Team Structure what does the structure look like?

Project_ Leader Senior Programmer Junior Programmer

What does a Database Designer/Developer do?

Projects that have a separate database will most likely need a database designer role. The database designer is responsible for planning, designing, developing and maintaining the database.

What are the foundations of healthy interaction between teammates?

Respect Trust Humility

Holding someone who isn't responsible accountable is ?

Scapegoating

The four constraints of a project are: time, cost, scope and quality. What are the corresponding elements of a project plan used to plan and manage these 4 constraints?

Schedule, budget, product backlog and change control procedures, quality plan

What is Loss of motivation also known as?

Social Loafing

What are some of the characteristics of social loafing?

Social loafing = people exerting less effort to achieve a goal when they work in a group than when they work alone. Group members tend to rely on others in the group to furnish the required effort to complete the task. Research shows that group members may be unaware they are not working at their full potential.

Assuming a team goes through all four stages of team development, which stage has the lowest productivity or performance?

Storming

Which of the following is not one of the common fields you would expect to find in a use case? Check all that apply. Only one may apply. - Title - Story Points - Actor(s) - Owner - Main Success Scenario - Extensions (i.e. alternate scenarios)

Story Points Owner

In the Forming stage of team development what are some of its characteristics?

Team members get to know one another. Everyone is polite. Conflict and controversy is avoided. There is a sense of excitement, anticipation and optimism. Specific activities: Define goals and objectives Clarify roles and responsibilities Decide how decisions will be made and work done Establish ways of working together (rules for collaboration) Develop conventions and procedures for communication Each member wants to know, and is entitled to know: "How do I fit in?" and "What will be expected of me?"

In the Storming stage of team development what are some of its characteristics?

Teams get a reality check during the storming stage of team development. This happens when the team begins to realize the task is different and more difficult than they imagined. Individuals on the team may become frustrated and aggravated with the team's progress and the way the work is being performed. If problems aren't resolved, members may withdraw—physically by leaving the team or emotionally by not caring any more. Expect conflict during the storming stage of team development. (Conflict resolution techniques will be discussed shortly).

In a Chief Programmer CPT ( Lead Programmer ) team what does the Technical Writer do?

Technical Writer: The chief programmer writes the first draft of most documentation because he or she is most familiar with the product. The technical writer is responsible for polishing it and filing in the missing details such as table of contents, references, appendices, etc.

In a Chief Programmer CPT ( Lead Programmer ) team what does the Tester do?

Tester: It's generally accepted that programmers shouldn't system test their own code. The chief programmer and auxiliary programmers will most likely write some unit test cases but a tester is needed to write and maintain a complete set of test cases. The tester may also be responsible for running test cases and planning the different testing phases (unit, integration, system, acceptance).

What does a Testers do?

Testers are responsible for planning activities such as writing test plans and devising testing procedures and the detailed work of designing, writing, and executing test cases. They may also be responsible for evaluating test coverage.

What does a Architect do?

The architect is responsible for creating and documenting the high level system design or architecture.

What is financial information?

The preliminary budget estimates for personnel and equipment.

What does a Product Manager do?

The product manager is responsible for the definition and evolution of the product concept.

When Obtaining Formal Authority to Proceed with a project what does the Optimum category cover?

The project is the best use of available resources.

What does a project manager do?

The project manager is responsible for planning, organizing, staffing, directing, controlling and managing risks. The main deliverable of the project manager is a project plan which includes a schedule, budget, and risk management plan.

What does a Quality Assurance Analyst do?

The quality assurance function is different from testing. The quality assurance analyst assures management and other project stakeholders that software products have their planned levels of quality. The quality assurance analyst makes sure the development team has access to agreed upon standards and procedures for software development and that the produces they produce conform to these standards.

A desirable characteristic of a requirements document is that it be traceable. Requirements may have forward and backward traceability. Backward traceability (from the perspective of the requirement) means that it is possible to trace a specific requirement back to its source (where it originated from). Forward traceability means it's possible to trace a requirement to a design element, code and/or test case. True:False

True Traceability refers to the ability to trace features between work products (forward and backward) in the software life cycle.

What does a Requirements/Business Analyst do?

The requirements analyst leads and coordinates the effort to establish project requirements. The product manager ultimately decides what goes into the product, but the requirements analyst does the work of eliciting and documenting the requirements.

What, if anything, is wrong with using a statement like the following in a requirements document in order to document a usability requirement: "The user interface should be easy to use"?

The statement isn't testable. Statements in the requirements document should be measurable and testable. "easy to use" should be defined. An alternative is "95% of users that fit the profile of the average user defined in section x.y can complete all possible transactions without prior training and without consulting the product documentation."

What is an example of a non-funcational requirement?

The system shall be responsive. No query should take longer than 3 seconds

What is an example of a functional requirement?

The system shall keep a record of all the transactions that modify the database

What is an example of a constraint requirement?

The system shall use and open source database

What is the Ringelmann Effect

The tendency for individual members of a group to become increasingly less productive as the size of their group increases.

When Obtaining Formal Authority to Proceed with a project what does the Feasible category cover?

There a high probability that the performing organization can complete the project successfully

Why are Use cases valuable?

They keep system development focused on the needs of the end user

Which of the following best describes the purpose of the project charter? Choices: - To define the expected project outcome - To define the path to the expected project outcome - To define the software product requirements - To define project staffing

To define the expected project outcome

In a Chief Programmer CPT ( Lead Programmer ) team what does the Toolsmith do?

Toolsmith: Small teams rely on good tools to maximize productivity. The toolsmith is responsible for assessing tool needs and then either acquiring or creating the tools to meet those needs. Creating custom tools can be seductive. A good toolsmith can accurately assess the value of potential tools and has the discipline to pursue only those tools that will improve the overall productivity of the team.

In general, the contents of a release plan comes from ______ analysis of the work and the contents of an iteration plan comes from ________ analysis of the work.

Top-down, Bottom-up

A milestone is a significant event during a project used to measure progress. A milestone is usually scheduled, but it doesn't have to be. True:False

True

Are Smaller teams preferable and more productive over larger teams? True:False

True

Except under extraordinary circumstances, an iteration plan is fixed for the duration of the iteration. True:False

True

Give an example of one of the most likely problems you will encounter if you wait until after the forming stage to establish team ground rules? [This is a discussion question for class. Be prepared to answer it in class.]

True

Is conflict a normal part of working in teams? True:False

True

It is possible to calculate the critical path for a project knowing only the tasks, their dependencies and their duration estimates. True:False

True

Risk management is a technique or discipline for dealing with uncertainty. Without uncertainty there is no need for risk management. True:False

True

Risk management is the practice of identifying risks, analyzing them, taking actions to avoid the risks identified, mitigating the probability and/or impact of the risk becoming a problem, creating contingency plans for dealing with risks that become problems and monitoring the changing nature of risks as the project evolves. True:False

True

The system being modeled in one UML use case diagram may play the role of actor in another use case diagram? In other words, it's perfectly reasonable for the software system at the center of one use case diagram to be an actor in another use case diagram. True:False

True Actors are usually individuals but actors can also be other software systems.

Assume the following statement comes from a software requirements specification: "The system shall be easy to learn. 90% of the users as defined in section x.y shall be able to complete use cases 1-3 within 10 minutes without consulting the written documentation." This statement is best characterized as what?

a non-functional requirement

All the actors and use cases of a system make up _______

a use case model

Project Initiation does what for clients?

manages client expectations which helps to avoid disagreements and misunderstandings towards the end of a project.

What is the definition of requirements?

internal and external capabilities and characteristics of the system necessary to satisfy the explicit and implicit needs of the customer and/or user.

Consider the following statement in a requirements document: (1) The system shall be secure. (2) Users should be authenticated with a user ID and password. After three consecutive invalid password attempts, the user account should be locked for 5 minutes. What is (1)? What is (2)?

non-functional requirement, functional requirement

Nearly all software is created in the context of a ______

project

A Use case model defines _______

the boundaries of the system

The project definition or concept is shaped by ?

the stakeholders interest