11 Mar

Scrum is an iterative and incremental agile software development framework for managing software projects and product or application development.

 Scrum has three fundamental roles: Product Owner, ScrumMaster, and team member.

  • Product Owner: In Scrum, the Product Owner is responsible for communicating the vision of the product to the development team. He or she must also represent the customer’s interests through requirements and prioritization. Because the Product Owner has the most authority of the three roles, it’s also the role with the most responsibility. In other words, the Product Owner is the single individual who must face the music when a project goes awry.The tension between authority and responsibility means that it’s hard for Product Owners to strike the right balance of involvement. Product Owners must be available to answer questions from the team.
  • ScrumMaster: The ScrumMaster acts as a facilitator for the Product Owner and the team. The ScrumMaster does not manage the team. Instead, he or she works to remove any impediments that are obstructing the team from achieving its sprint goals. In short, this role helps the team remain creative and productive, while making sure its successes are visible to the Product Owner.
  • Team Member: In the Scrum methodology, the team is responsible for completing work. Ideally, teams consist of seven cross-functional members, plus or minus two individuals. For software projects, a typical team includes a mix of software engineers, architects, programmers, analysts, QA experts, testers and designers. Each sprint, the team is responsible for determining how it will accomplish the work to be completed. This grants teams a great deal of autonomy, but, similar to the Product Owner’s situation, that freedom is accompanied by a responsibility to meet the goals of the sprint.






Supply Chain Management

11 Mar

This is a key aspect of new product development today. The supply chain has shifted greatly toward a more technological approach with new advances in hand held devises such as PDAs for deliveries as well as orders within a supply chain. The ordering of goods can be done quickly and efficiently on-line, whether it be by an everyday consumer or even a big delivery by a multinational company. Also, all paperwork from the orders does not need to be on paper; it can simply be held safely on a disk and stored efficiently. The most important this about the supply chain is that it is timely and efficient. This has begun with the removal of paper from the system but has still a long way to go. And so, advances continue to be made toward this with a supply chain.


Here we can see the general overview of the supply chain process. Efficient Supply Chain managment systems will be needed here to make this system work as quickly as possible whicle getting the job done correctly. Advances have been made by companies such as Inditex and IBM to make their SCM extremely organised. 

Link to IBM supply chain solution.


Here we can see just how many links their may be in order to make a supply chain work.

Final Blog!!

11 Mar

Summary of Traditional Software Development:

Waterfall Model

V Model

Spiral Model

Systems Development Life Cycle.
What is the difference between Agile and Traditional Software Development Methodology?
Although Agile method is based on iterative development as some of the traditional approaches, Agile and Traditional methodologies have key differences. Traditional approaches use planning as their control mechanism, while Agile models use the feedback from the users as the main control mechanism. Agile can be called a people-centric approach than traditional methods. Agile model delivers a working version of the product very early compared to traditional methodologies so that the customer can realize some of the benefits early on. Testing cycle time of Agile is relatively short compared to traditional methods, because testing is done parallel to development. Most traditional models are very rigid and relatively less flexible than the Agile model. Because of all these advantages, Agile is preferred over the traditional methodologies at the moment.

I hope by reading my blogs i have helped you more clearly understand The traditional methods of software development. Although it is not preferred when compared to Agile methods it is still extremely important. Best of luck in the exams.

Now that we are almost finished….what does the future hold for systems analysts?

10 Mar

With the rapid developments in technology it is forcing businesses to adapt to the changing nature of commerce. With more emphasis on E-commerce the need for flexible and innovation systems analysts is only going to increase significantly. According to the U.S. Bureau of Labor Statistics, Employment Projections program,

“Employment of computer systems analysts is expected to grow 22 percent from 2010 to 2020, faster than the average of all occupations.”

This shows how much business will change over the next number of decades as technology continues to advance! There will be a need for better training of new systems analysts and even better RE-TRAINING of existing SA’s in order for businesses to remain competitive.

Growth in wireless and mobile networks will create a need for new systems that work well with these networks.

Additional job growth is expected in healthcare fields. A large increase is expected in electronic medical records, e-prescribing, and other forms of healthcare IT, and analysts will be needed to design computer systems to accommodate the increase.

I hope you all enjoyed my blogs! To be honest I wasnt very sure about the idea initially but i must admit i thoroughly enjoyed the research aspect of it as well as the publishing side of it.


Agile Unified Process (AUP)

10 Mar

Agile Unified Process is a simplified version of the Rational Unified Process (RUP).  It describes a simple, easy to understand approach to developing business application software using agile techniques and concepts yet still remaining true to the RUP.

The serial nature of Agile UP is captured in its four phases :

  1. Inception.
  2. Elaboration.
  3. Construction.
  4. Transition.

Disciplines are performed in an iterative manner, defining the activities which development team members perform to build, validate, and deliver working software which meets the needs of their stakeholders. The disciplines are:

  • Model.  The goal of this discipline is to understand the business of the organization, the problem domain being addressed by the project, and to identify a viable solution to address the problem domain.
  • Implementation.  The goal of this discipline is to transform your model(s) into executable code and to perform a basic level of testing, in particular unit testing.
  • Test.  The goal of this discipline is to perform an objective evaluation to ensure quality. This includes finding defects, validating that the system works as designed, and verifying that the requirements are met.
  • Deployment.  The goal of this discipline is to plan for the delivery of the system and to execute the plan to make the system available to end users.
  • Configuration Management.  The goal of this discipline is to manage access to your project artifacts. This includes not only tracking artifact versions over time but also controlling and managing changes to them.
  • Project Management.  The goal of this discipline is to direct the activities that takes place on the project. This includes managing risks, directing people (assigning tasks, tracking progress, etc.), and coordinating with people and systems outside the scope of the project to be sure that it is delivered on time and within budget.
  • Environment. The goal of this discipline is to support the rest of the effort by ensuring that the proper process, guidance (standards and guidelines), and tools (hardware, software, etc.) are available for the team as needed.

The Agile UP is based on the following principles:

  1. Your staff knows what they’re doing.
  2. Simplicity.
  3. Agility.
  4. Focus on high-value activities.
  5. Tool independence.
  6. You’ll want to tailor this product to meet your own needs.

Information Systems Aiding Innovation

10 Mar

Cross Functional Expertise

It is very important that there is a cross functional information system within a business for NPD (new product development). The importance of this, stems from the need for a strong communication system within business. There should always be a link between the various departments off a company in order for them to discuss different aspects of the new product.

For example ;

The financial department should always have access to the product management and process management departments and within them, they should hhave access to sales and marketing as well as supply chain management. This is very important as without that connection budgets can be badly broken and products could fail.

This has become more of a growing issue with more and more finance required in order to get a new product on its feet and selling well.

Supply Chain Management

With NPD some say the most important thing is how timely your production is and how efficiently the process is done. This is why an effective supply chain is vital. Orders need to be specific and close attention must always be kept towards delivery times and production deadlines. Without this your whole production line could fail and you may end up over paying employees or other areas of your supply chain may suffer.Image

Internal and External Knowledge of Markets

A marketing information system (MIS) is intended to bring together different types of data related to a certain product or service and evaluate it to get to know various aspects of your chosen market. This has become a very important part of NPD as it can give companies strategic advantage on their product, the prices they should sell at, place where they could sell and how they should promote their product. Information systems play a vital role here as all areas of the marketing department need to be kept up to date on the research findings.


Trends in I.S: Transaction Processing Systems

10 Mar

As promised, for my last blog, I will be focusing on Transaction Processing Systems (TPS). A TPS is a very valuable asset to business because it deals with processing routine transactions efficiently and accurately. It involves collecting, modifying and retrieving all transaction data used in business transactions.

TPS consist of invoicing systems, payroll systems and stock control systems. They support operational level employees in a business. TPS is known for its high performance standards, consistency and reliability. It is also known as transaction processing or real-time processing.

The following image is a simplified explanation of TPS:


This was my last ever blog on trends in I.S so I hope you enjoy reading this blog and that you also appreciated my previous blogs! 🙂

Thanks again!

%d bloggers like this: