Account Navigation

Account Navigation

Currency - All prices are in AUD

Currency - All prices are in AUD
 Loading... Please wait...
The Art of Service Standard Requirements Self Assessments

Agile Software Development Toolkit: best-practice templates, step-by-step work plans and maturity diagnostics

$249.00

Agile Software Development Toolkit: best-practice templates, step-by-step work plans and maturity diagnostics

$249.00

Availability:
Downloadable Resources, Instant Access

Product Description

Save time, empower your teams and effectively upgrade your processes with access to this practical Agile Software Development Toolkit and guide. Address common challenges with best-practice templates, step-by-step work plans and maturity diagnostics for any Agile Software Development related project.

Download the Toolkit and in Three Steps you will be guided from idea to implementation results.

The Toolkit contains the following practical and powerful enablers with new and updated Agile Software Development specific requirements:


STEP 1: Get your bearings

Start with...

  • The latest quick edition of the Agile Software Development Self Assessment book in PDF containing 49 requirements to perform a quickscan, get an overview and share with stakeholders.

Organized in a data driven improvement cycle RDMAICS (Recognize, Define, Measure, Analyze, Improve, Control and Sustain), check the…

  • Example pre-filled Self-Assessment Excel Dashboard to get familiar with results generation

Then find your goals...


STEP 2: Set concrete goals, tasks, dates and numbers you can track

Featuring 746 new and updated case-based questions, organized into seven core areas of process design, this Self-Assessment will help you identify areas in which Agile Software Development improvements can be made.

Examples; 10 of the 746 standard requirements:

  1. When you are identifying the potential technical strategy(s) you have several process factors that you should address. As with initial scoping how much detail you go into when documenting the architecture, the views that you create, and your approach to modeling are important considerations. Furthermore, will you be considering one or more candidate architectures and what is your overall delivery strategy?

  2. As corporate ventures usually go to new business areas and work with new technologies, they are most likely unable to utilise existing commercial or parent corporations in-house development methods. Could Agile Manifesto and agile methods be a good starting point for the corporate venture to start their development effort towards their own, efficient agile in-house software development method?

  3. Management buy-in is a concern. Many program managers are worried that upper-level management would ask for progress reports and productivity metrics that would be hard to gather in an Agile work environment. Management ignorance of Agile methodologies is also a worry. Will Agile advantages be able to overcome the well-known existing problems in software development?

  4. Many teams will find that informal modeling sessions around whiteboards will be sufficient, although sometimes more formal modeling sessions, such as Joint Application Design (JAD) strategies or stakeholder interviews will work best. How will non- functional requirements pertaining to availability, security, performance, and many other factors be addressed?

  5. Much of the agile advice is oriented towards small teams of up to ten people, who are either co-located or near located, who have ready access to their primary stakeholders, and who are working on software that can be easily organized into a series of small releases. What about large teams?

  6. The sprint backlog is the list of work the team must address during the next sprint. The list is derived by selecting stories/features from the top of the product backlog until the team feels they have enough work to fill the sprint. Is this done by the team asking, Can we also do this?

  7. The fundamentals of agile software development, agile project management, and evolutionary development have been proven and demonstrated to be highly successful. Are these now preferred in our organization?

  8. Could Agile Manifesto and agile methods be a good starting point for the corporate venture to start their development effort towards their own, efficient agile in-house software development method?

  9. How do you take a methodology, like agile development, that basically evolved in small groups and then scale it up so that it works on projects with hundreds of developers and thousands of users?

  10. Imagine a scenario where you engage a software group to build a critical software system. Do you think you could provide every last detail the developers need to know right off the bat?


Complete the self assessment, on your own or with a team in a workshop setting. Use the workbook together with the self assessment requirements spreadsheet:

  • The workbook is the latest in-depth complete edition of the Agile Software Development book in PDF containing 746 requirements, which criteria correspond to the criteria in...

Your Agile Software Development self-assessment dashboard which gives you your dynamically prioritized projects-ready tool and shows your organization exactly what to do next:

  • The Self-Assessment Excel Dashboard; with the Agile Software Development Self-Assessment and Scorecard you will develop a clear picture of which Agile Software Development areas need attention, which requirements you should focus on and who will be responsible for them:

    • Shows your organization instant insight in areas for improvement: Auto generates reports, radar chart for maturity assessment, insights per process and participant and bespoke, ready to use, RACI Matrix
    • Gives you a professional Dashboard to guide and perform a thorough Agile Software Development Self-Assessment
    • Is secure: Ensures offline data protection of your Self-Assessment results
    • Dynamically prioritized projects-ready RACI Matrix shows your organization exactly what to do next:

 

STEP 3: Implement, Track, follow up and revise strategy

The outcomes of STEP 2, the self assessment, are the inputs for STEP 3; Start and manage Agile Software Development projects with the 62 implementation resources:

  • 62 step-by-step Agile Software Development Project Management Form Templates covering over 6000 Agile Software Development project requirements and success criteria:

Examples; 10 of the check box criteria:

  1. Variance Analysis: Does the scheduling system identify in a timely manner the status of work?

  2. Procurement Audit: Were any additional works or deliveries admissible, without recourse to a new procurement procedure?

  3. Change Management Plan: Is there a support model for this application and are the details available for distribution?

  4. Requirements Management Plan: Who is responsible for monitoring and tracking the Agile Software Development project requirements?

  5. Communications Management Plan: Are the stakeholders getting the information others need, are others consulted, are concerns addressed?

  6. Procurement Management Plan: Is the Agile Software Development project Sponsor clearly communicating the Business Case or rationale for why this Agile Software Development project is needed?

  7. Activity Attributes: How difficult will it be to do specific activities on this Agile Software Development project?

  8. Scope Management Plan: Is the organization structure for both tracking & controlling the budget well defined and assigned to a specific individual?

  9. WBS Dictionary: Are indirect costs accumulated for comparison with the corresponding budgets?

  10. Activity Duration Estimates: Are resource rates available to calculate Agile Software Development project costs?

 
Step-by-step and complete Agile Software Development Project Management Forms and Templates including check box criteria and templates.

1.0 Initiating Process Group:

  • 1.1 Agile Software Development project Charter
  • 1.2 Stakeholder Register
  • 1.3 Stakeholder Analysis Matrix


2.0 Planning Process Group:

  • 2.1 Agile Software Development project Management Plan
  • 2.2 Scope Management Plan
  • 2.3 Requirements Management Plan
  • 2.4 Requirements Documentation
  • 2.5 Requirements Traceability Matrix
  • 2.6 Agile Software Development project Scope Statement
  • 2.7 Assumption and Constraint Log
  • 2.8 Work Breakdown Structure
  • 2.9 WBS Dictionary
  • 2.10 Schedule Management Plan
  • 2.11 Activity List
  • 2.12 Activity Attributes
  • 2.13 Milestone List
  • 2.14 Network Diagram
  • 2.15 Activity Resource Requirements
  • 2.16 Resource Breakdown Structure
  • 2.17 Activity Duration Estimates
  • 2.18 Duration Estimating Worksheet
  • 2.19 Agile Software Development project Schedule
  • 2.20 Cost Management Plan
  • 2.21 Activity Cost Estimates
  • 2.22 Cost Estimating Worksheet
  • 2.23 Cost Baseline
  • 2.24 Quality Management Plan
  • 2.25 Quality Metrics
  • 2.26 Process Improvement Plan
  • 2.27 Responsibility Assignment Matrix
  • 2.28 Roles and Responsibilities
  • 2.29 Human Resource Management Plan
  • 2.30 Communications Management Plan
  • 2.31 Risk Management Plan
  • 2.32 Risk Register
  • 2.33 Probability and Impact Assessment
  • 2.34 Probability and Impact Matrix
  • 2.35 Risk Data Sheet
  • 2.36 Procurement Management Plan
  • 2.37 Source Selection Criteria
  • 2.38 Stakeholder Management Plan
  • 2.39 Change Management Plan


3.0 Executing Process Group:

  • 3.1 Team Member Status Report
  • 3.2 Change Request
  • 3.3 Change Log
  • 3.4 Decision Log
  • 3.5 Quality Audit
  • 3.6 Team Directory
  • 3.7 Team Operating Agreement
  • 3.8 Team Performance Assessment
  • 3.9 Team Member Performance Assessment
  • 3.10 Issue Log


4.0 Monitoring and Controlling Process Group:

  • 4.1 Agile Software Development project Performance Report
  • 4.2 Variance Analysis
  • 4.3 Earned Value Status
  • 4.4 Risk Audit
  • 4.5 Contractor Status Report
  • 4.6 Formal Acceptance


5.0 Closing Process Group:

  • 5.1 Procurement Audit
  • 5.2 Contract Close-Out
  • 5.3 Agile Software Development project or Phase Close-Out
  • 5.4 Lessons Learned

 

Results

With this Three Step process you will have all the tools you need for any Agile Software Development project with this in-depth Agile Software Development Toolkit.

In using the Toolkit you will be better able to:

  • Diagnose Agile Software Development projects, initiatives, organizations, businesses and processes using accepted diagnostic standards and practices
  • Implement evidence-based best practice strategies aligned with overall goals
  • Integrate recent advances in Agile Software Development and put process design strategies into practice according to best practice guidelines

Defining, designing, creating, and implementing a process to solve a business challenge or meet a business objective is the most valuable role; In EVERY company, organization and department.

Unless you are talking a one-time, single-use project within a business, there should be a process. Whether that process is managed and implemented by humans, AI, or a combination of the two, it needs to be designed by someone with a complex enough perspective to ask the right questions. Someone capable of asking the right questions and step back and say, 'What are we really trying to accomplish here? And is there a different way to look at it?'

This Toolkit empowers people to do just that - whether their title is entrepreneur, manager, consultant, (Vice-)President, CxO etc... - they are the people who rule the future. They are the person who asks the right questions to make Agile Software Development investments work better.

This Agile Software Development All-Inclusive Toolkit enables You to be that person.

 

Includes lifetime updates

Every self assessment comes with Lifetime Updates and Lifetime Free Updated Books. Lifetime Updates is an industry-first feature which allows you to receive verified self assessment updates, ensuring you always have the most accurate information at your fingertips.

Product Reviews

Find Similar Products by Category