At its core, agile is an iterative project management methodology. Agile works by breaking projects down into short duration milestones of user functionality, prioritizing them, and then continuously delivering iterations, usually, in short two week cycles.
….Many people refer to time as a resource. A resource is something ready for use, or something that can be drawn upon for aid. that fits his definition. Begin to accept time as your most important resource. Time is a tool that can be drawn upon to help you accomplish results, an aid that can take care of a need, an assistant in solving problems. However, time is not like other resources, because you can’t buy it, sell it, rent it, steal it, borrow it, store it, save it, multiply it, manufacture it, or change it. All you can do is spend [ use] it.
As a resource, time poses another paradox: If you don’t use it, it disappears anyway. Thus, the quality of your [time] resource depends on how well you use it. The knowledge that you are wasting this very personal resource when you do not spend it properly should be enough to keep you on track, resolving to spend your time better.
Your attitude toward time is also affected by the fact that time is free – you do not have to buy it. You receive 24 hours simply by waking up each morning. Many people do not place much value on things that cost nothing or on things obtained with little effort. If you buy” your time, you’d probably spend it much differently had to than you do now.
Not only is time free; it is equitable. Everyone receives exactly same amount each day. But this is a deceptive equality, since people always manage to get more out of their 24 hours than s. Still, time is one of the truly democratic aspects of our lives…..
–Merrill e. Douglass/Donna N. Douglass, 1980,” Manage Your Time, Manage Your Work, Manage Yourself”; ISBN: 0-81447632-5
While I’m no longer a formal Project Manager, from time to time I still have the need to create a project Plan or to help someone else to organize a project plan. Usually. I find that it is easier to get to a more holistic plan faster, if I have a pattern of essential tasks and milestone to work with. So, I usually go to a template which I have assembled across time use as an accelerator and/or job aide. The attached project plan templates are for a common data warehouse project pattern, but by no means is intended to be the end all of project plans; it is just a starter kick, sort of speak.
There are several reasons why projects plan patterns may vary, other than the experience and knowledge of project planner, among them are:
The environment migration pattern in use
The application stack of the of the environment
The tools use to manage the project plan (MS Project, JIRA, OpenProj, etc.)
The size and complexity of the project team
Here is project plan mockup around Infosphere Datastage, but should be adaptable to any other ETL application.
Rapid Application Development (RAD) is a type of incremental software development methodology, which emphasizes rapid prototyping and iterative delivery, rather than planning. In RAD model the components or major functions are developed in parallel as if they were small relatively independent projects, until integration.
RAD projects are iterative and incremental
RAD projects follow the SDLC iterative and incremental model:
During which more than one iteration of the software development cycle may be in progress at the same time
In RAD model the functional application modules are developed in parallel, as prototypes, and are integrated to complete the product for faster product delivery.
RAD teams are small and comprised of developers, domain experts, customer representatives and other information technology resources working progressively on their component and/or prototype.
Over the years I have seen a lot of patterns for Information integration testing process and these patterns will not be an exhaustive list of patterns a consultant will encounter over the course of a career.
However, the two most common patterns in the testing process are:
The Three Test Phase Pattern
In the three test phase pattern, normally, the environment and testing activities of SIT and SWIT are combined.
The Four Test Phase Pattern
In the four test phase pattern, normally, the environment and testing activities of SIT and SWIT are performed separately and, frequently, will have separate environments in the migration path.
Testing of individual software components or modules. Typically done by the programmer and not by testers, as it requires detailed knowledge of the internal program design and code. may require developing test driver modules or test harnesses.
System Integration Testing (SIT):
Integration testing – Testing of integrated modules to verify combined functionality after integration. Modules are typically code modules, individual applications, client and server applications on a network, etc. This type of testing is especially relevant to client/server and distributed systems. Testing performed to expose defects in the interfaces and in the interactions between integrated components or systems. See also component integration testing, system integration testing.
Software Integration Test (SWIT)
Similar to system testing, involves testing of a complete application environment, including scheduling, in a situation that mimics real-world use, such as interacting with a database, using network communications, or interacting with other hardware, applications, or systems if appropriate.
User Acceptance Testing (UAT):
Normally, this type of testing is done to verify if the system meets the customer specified requirements. Users or customers do this testing to determine whether to accept the application. Formal testing with respect to user needs, requirements, and business processes conducted to determine whether or not a system satisfies the acceptance criteria and to enable the user, customers or other authorized entity to determine whether or not to accept the system.