Agile Project Management with Scrum (Microsoft Professional) - Ken Schwaber

Agile Project Management with Scrum (Microsoft Professional)

Latest member in my scrum book collection. I have read this many times in the library and I bought it for myself because this is not just a book but a treasure by 'Founders of Agile'. See below the product description.

Try it out, you will not loose your money.

Product Description

Apply the principles of Scrum, one of the most popular agile programming methods, to software project management—and focus your team on delivering real business value. Author Ken Schwaber, a leader in the agile process movement and a co-creator of Scrum, brings his vast expertise to helping you guide the product and software development process more effectively and efficiently. Help eliminate the ambiguity into which so many software projects are borne, where vision and planning documents are essentially thrown over the wall to developers. This high-level reference describes how to use Scrum to manage complex technology projects in detail, combining expert insights with examples and case studies based on Scrum. Emphasizing practice over theory, this book explores every aspect of using Scrum, focusing on driving projects for maximum return on investment.

About the Author

Ken Schwaber is the co-creator of Scrum. He is one of the leaders of the agile process revolution, as a signatory of the Agile Manifesto and founder and director of the Agile Alliance. He has been in the software development industry for more than 30 years and teaches and speaks at many conferences, including OOPSLA & Software Development.

Read More details from amazon.

Functional Point Analysis (Mind Map) - Part 3

Multi-scale Quantum Models for Biocatalysis: Modern Techniques and Applications (Challenges and Advances in Computational Chemistry and Physics)

Multi-scale Quantum Models for Biocatalysis: Modern Techniques and Applications (Challenges and Advances in Computational Chemistry and Physics)

Functional Point Analysis (Mind Map) - Part 2

Software Estimation: Demystifying the Black Art (Best Practices (Microsoft))


Software Measurement and Estimation: A Practical Approach (Quantitative Software Engineering Series)

Information System Project Management - Examples of Risks

Staff Risks

• key staff will not be available when needed
• key skills will not be available when needed
• staff will be lost during the project

Equipment Risks

• required equipment will not be delivered on time
• access to hardware will be restricted
• equipment will fail

Client Risks

• client resources will not be made available when required
• client staff will not reach decisions in a timely manner
• deliverable will not be reviewed according to schedule
• knowledgeable client staff will be replaced by those less qualified

Scope Risks

• requirements for additional efforts will surface
• changes of scope will be deemed to be included in the project
• scope changes will be introduced without the knowledge of the project manager

Technology Risk

• technology will have technical or performance limitations that endanger project
• technology components will not be easily integrated
• technology is new and poorly understood.

Delivery Risk

• system response time will not be adequate
• system capacity requirements will exceed available capacity
• the system will fail to meet functional requirements

Physical Risk

• the office will be damaged by fire, flood or other catastrophe
• a computer virus will infect the development systems
• a team member will steal confidential material and make it available to competitors of the client

Source:

Information Systems Project Management: How to Deliver Function and Value in Information Technology Projects

Functional Point Analysis (Mind Map) - Part 1

 

The IT Measurement Compendium: Estimating and Benchmarking Success with Functional Size Measurement


Functional Data Analysis with R and MATLAB (Use R)

How to determine a realistic schedule for a project?

prerequisites before task scheduling 

• Requirements gathered to the level just enough for estimating
• Determine Risks, Constrains
• Availability of resources
• Make sure the estimates are done by your team and work package is estimaetd by the person who is going to do the real work.

Steps to follow: 

1. Create a work breakdown structure (WBS). I prefer to use either Featurewise categorization or use Product life cycle categorization. (Dont try to simulate PMI process model in the WBS)
2. Create a Ghant Chart or use MSProject
3. Estimate Work-packages.
4. Sequence the activities (Network Diagram) or User the MsProject Ghant chart itself.
5. Run through Forward Pass , Backward pass: You can use either float formula to compute float. Late Finish - Early Finish = 14 - 9 :::  5, or Late Start - Early Start'" 8 - 3 = 5.
6. Determine Float, Total Float
7. Resource Allocation
8. Level Resources

 IT Project Estimation: A Practical Guide to the Costing of Software