Bua 235 teamwork


Published on

Published in: Business, Technology
1 Like
  • Be the first to comment

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Bua 235 teamwork

  1. 1. BUA 235: Team Project And Chap 10’s Information Systems Development- SDLC
  2. 2. AOL: Teamwork • Goal 4: Teamwork • Students will understand the fundamental concepts of teamwork, and demonstrate the ability to work in teams.
  3. 3. Corresponding Objectives: • Students will identify the elements in building effective teams; students will articulate the team goal and their individual contributions to the team goal and students will describe the significant roles and contributions of team members
  4. 4. Why teamwork? • Because of synergy in groups is remarkable • We are assessing group effectiveness in order to place individual personalities in perspective, value differences that arise, and meld diverse approaches into effective teamwork
  5. 5. Effective Teams • The most effective teams are the ones where everyone understands their unique jobs and then (of course) does them
  6. 6. What is measured when determining Effective teamwork? • Do all members know what specific goals the team is trying to accomplish? • Do team members agree on that the specific goals identified? • What activities does the team choose to undertake or assign in order to achieve its goals? – Did any particular activity work particularly well in getting goals met?
  7. 7. Team effectiveness continued • Did each team member have a specific –even unique---responsibility(s) that helped the team achieve its goal? • Is the work stimulating and worth your time? • Does your team have the resources to achieve its goals? • Resources include; – Organization – Leadership – Communication – Talents /skills – time
  8. 8. Your Team Project • The team project consists of developing an inventory information system using MS Access 2007. Specific deliverables of the team project will include; • A list of three to five business requirements that state how the information system should work • An Entity Relationship (ER) Model that graphically represents specific information system entities. These entities include; tables, relationship types, fields, and field data types • The completed information system itself. This information system will include; tables, forms, queries, macros, relationships, various reports, and a main menu for accessing information system resources.
  9. 9. To start the project • Teams will be setup first. Next week • Information Systems Cases will be assigned to each team: Next week • Team leaders will have to choose a electronic platform, Google Docs, Wiggio, etc… to manage communication, workflow, and Content management • Deliverables: • Business Requirements and ER Diagram Report • The Information system itself built using MS Access 2007 /2010 • DUE: Report and Info system due on 12/2/2010 • Team Presentations: Dec 7-9
  10. 10. What is Systems Development? • Systems development, or systems analysis and design • Process of creating and maintaining information systems
  11. 11. System development not just for Techies! • Establishing the system’s goals, setting up the project, and determining requirements require business knowledge and management skill. • Tasks such as building computer networks and writing computer programs require technical skills. • Developing the other components requires nontechnical, human relations skills.
  12. 12. Non-technical, human relations skills required! • Creating data models requires the ability to interview users and understand their view of the business activities. • Designing procedures, especially those involving group action, requires business knowledge and an understanding of group dynamics. • Developing job descriptions, staffing, and training all require human resource and related expertise. • Coordinated teamwork of both specialists and non-specialists with business knowledge.
  13. 13. IS systems never “off the shelf” • Information systems involve people and procedures, therefore procedures must be constructed or adapted to fit business and people, regardless of how computer programs are obtained. • You will have a key role in information systems development. • Ensuring that effective procedures exist for using the information system • Ensuring that personnel are properly trained and are able to use the IS effectively • Single most important criterion for information systems success is for users to take ownership of their systems.
  14. 14. Difficulties Associated with Systems development • Systems development is difficult and risky. • Many projects are never finished. • Some finish 200 to 300 percent over budget. • Others finish within budget and schedule, but never satisfactorily accomplish their goals.
  15. 15. Requirements Determination • What features do you want? • Do you really need them? • What kind of controls do you want? • What functions should it have? • What data do you have? • What information do you want provided? • Must create environment where difficult questions are asked and answered
  16. 16. Challenges associated with Virtual Teams • Remember chap 2? • Content management requires a means to manage multiple users that are contributing and changing documents, schedules, task lists, assignments, and so on…. • Factors that will effect collaboration include; • unique dimensions of virtuality include; • geographic dispersion, • electronic dependence, • cultural diversity, and • dynamic structure.
  17. 17. Changes in Requirements • Development aims at moving target • Bigger the system and longer the project, the more requirements change When requirements change, what should the development team do? • Stop work and rebuild system in accordance with new requirements? If they do that, system will develop in fits and starts and might never be completed. • Or, should the team finish the system, knowing that it will be unsatisfactory the day it is implemented and will therefore need immediate maintenance?
  18. 18. Scheduling and Budgeting Problems • How long to build it? • How long to create data model? • How long to build database applications? • How long to do testing? • How long to develop and document procedures? • How long for training? • How much will it cost for labor? • What are the costs and benefits? • What’s the rate of return on investment?
  19. 19. Changing Technologies and Diseconomies of Scale • Technology is constantly changing! • Do you change mid-way through a systems development project should something newer come along? Diseconomies of Scale • As development teams get larger, the average contribution per worker decreases • As a result, more meetings and coordination is required…= more time!
  20. 20. Brooks’ Law  Adding more people to a project makes the project later.”  When new staff are brought into a late project, they must be trained by productive members who lose productivity while they’re training new members. • Some tasks simply can’t be speeded up.
  21. 21. Systems Development Lifecycle -SDLC 1. Systems definition • Management’s statement of objective and goals for new system 2. Requirements analysis • Identify features and functions 3. Component design (hardware, software, network) • Based on approved user requirements 4. Implementation • Purchase, build, test, and convert to new system 5. System maintenance (fix or enhance) • Repair, add new features, maintain
  22. 22. How Is System Definition Accomplished?
  23. 23. How Is System Definition Accomplished? • Team of users and IT professionals assigned to assess feasibility • Small business may hire consultant to work with managers and key employees 1. (a.) Define system goals for new system  Facilitate competitive strategy  Improve decision making  MRV • Create quality relationships with quality customers • Use those relationships to generate revenue
  24. 24. How Is System Definition Accomplished? 1.(b.) Define scope for new system  Defined by customers, users involved, business processes impacted, physical location, functional area  Clear definition of scope simplifies • Requirements determination • Coordination and other work
  25. 25. Assess Feasibility Dimensions of feasibility • Cost feasibility  Approximated, “back-of-the-envelope” analysis  Purpose: eliminate infeasible ideas early  Consider cost of previous projects, operational and labor costs • Schedule feasibility  Ball park estimate • Technical feasibility  Is it technically likely to meet needs? • Organizational feasibility  Fit with customs, culture, charter, legal requirements of organization
  26. 26. Form a Project Team • Typical personnel on a development team are: • Manager (or mangers for larger projects) • System analysts • Programmers • Software testers • Users. • Depending on nature of project, team may also include hardware and communications specialists, database designers and administrators, and other IT specialists.