Project Management Url's - Kapil Sharma

Project Management Url's:

https://www.youtube.com/watch?v=JZKsk17a6oA&list=PLBB840DC740D9A813

http://www.tomsitpro.com/articles/project-management-certifications,2-670-2.html

Scrum Team Members - Kapil Sharma

SCRUM TEAM: 

A breif overview of scrum team members: 
1.) Product Owner (PO)
2.) Developement Team (DT)
3.) Scrum Master (SM)

Software Development Models( Scrum Vs Waterfall) - Kapil Sharma

Software Development Models: Scrum Vs Waterfall

As the software industry growing, it also leads many new technologies and software design architectures to evolving along with that.

As software designer you may came cross software development models. Mainly Waterfall model is the first choice of the software designers. But these days many software designers prefer Scrum based software development life cycle.

Waterfall Model:

The software development work goes in phase manner.

1.) Requirements

2.) Design

3.) Development

4.) Testing

5.) Maintenance

Suppose a client wants software to do stock trading and the time of building this software takes 12 months. The client shares his requirements in Jan. (first month) and by Dec. (last month) he/she able to see how the software works out.

There was no chance / choice of software requirements to change or any preview of the software product. So there was a complete blackout of more than 10 months for client side.

Whereas Scrum the new kid in the town believes that software development is a creative art where a big software product cut into small shippable product and client can change the requirements and view the shippable software in weeks based time frame rather than waiting to get a full finished software product.

Now, in scrum all this depends upon the PBI (Product Backlog Items) these are user stories or you can small chunks of bigger software requirements. These can be written by a scrum team consists of a ‘Product owner’ a ‘Scrum Master’ and ‘Development team’. All can write these user stories on client software requirements where as the P.O (product owner) he/she has the final authority to put these PBI in the sprints or iterations (these are time-bound week based software development cycle), in scrum a sprint can be 1-4 week maximum.

Scrum Sprint:

1.) Sprint 1, X items

2.) Sprint 2, X + Y items

3.) Sprint 3, X + Y + Z items

So, after ending of each sprint the scrum team show the client a workable software item. And this help client to check the software is building in the way he/she wants. If client thinks new or changes required, he suggest and these new C.R (change request) can be added in the next sprint.

So, in nutshell the scrum software design model basically cut short the margin of error of wrong software development and its leaps ahead of older development models.

What is Scrum Framework - Kapil Sharma

What is Scrum Framework?

Scrum is a methodology developed under Agile framework. The main people behind this methodology are 'Ken and Jeff'. They are the seasoned software developers. 

For example, think like 'Agile' is an umbrella and 'Scrum' is one edge of that framework.

Generally scrum methodology used in software development through out the globe.
The name scrum from a sport known as rugby : )

A scrum team having these following player or members:

1.) P.O: Product Owner
2.) SM: Scrum Master
3.) Team: Developers + QA 

SOW: Scope of work (Class 1003)

Scope of Work: 

The first thing in 'Project Management' any project manager face is the term 'SOW-Scope of Work'.

So, what exactly is the scope or scope of work?

Scope Of Work: Is expected level of work. As a team what we are delivering to the client and also what we are not committed for tasks. 

So, the 'Scope Of Work' document consists of these points: 
1) Project Title / Name.
2) Contact Information. 
3) Version Number and Dates.
4) Overview Of Project.
5) Clear Scope Of Work.
6) ETA-Time Frame Details.
7) Project Budget.
8) Client Approvals / Sign Off details. 

WBS: Work Breakdown Structure. (Class 1002)

WBS: Work Breakdown Structure:

First comes the 'SOW' project scope of work.

Than there is more in-depth tasks and further more in more in details tasks, so that every minute details capture, so that all gaps of tasks are covered. 

Each person or department knows what there are assigned off rather than keep on guessing the ongoing tasks.