• Corpus ID: 12210759

Borland Software Craftsmanship: A New Look at Process, Quality and Productivity

@inproceedings{Coplien1994BorlandSC,
  title={Borland Software Craftsmanship: A New Look at Process, Quality and Productivity},
  author={James O. Coplien},
  year={1994}
}
The Borland Quattro Pro® for Windows (QPW) development is one of the most remarkable organizations, processes, and development cultures we have encountered in the AT&T Bell Laboratories Pasteur process research project. The project assimilated requirements, completed design and implementation of 1 million lines of code, and completed testing in 31 months. Coding was done by no more than eight people at a time, which means that individual coding productivity was higher than 1000 lines of code… 

Figures from this paper

Implementing SCRUM using Business Process Management and Pattern Analysis Methodologies

This comprehensive case study demonstrates how organizational behavior and process management techniques can be integrated with knowledge management approaches to deploy agile development and shows how combining SCRUM and EKD provides organizations with a comprehensive framework for managing and improving software and system development.

Organizational Transformation with Scrum: How a Venture Capital Group Gets Twice as Much Done with Half the Work

OpenView is the first high-performance non-software Scrums that has documented twice as much value produced in fewer working hours and provides a working manual on how to do Scrum outside of software development.

Organizational Transformation with Scrum: How a Venture Capital Group Gets Twice as Much Done with Half the Work

OpenView is the first high-performance non-software Scrums that has documented twice as much value produced in fewer working hours and provides a working manual on how to do Scrum outside of software development.

Synergy of Organizational Patterns and Aspect-Oriented Programming

  • Peter BertaV. Vranic
  • Computer Science
    2019 IEEE 15th International Scientific Conference on Informatics
  • 2019
This work analyzed organizational patterns of agile software development from the perspective of aspect-oriented programming, whose aim is to improve the separation of concerns in code, which, in turn, allows for better separation of tasks performed by people.

Scrum Abandonment in Distributed Teams: A Revelatory Case

It is proposed that task/team familiarity, group cohesion and transactive memory may be combined to understand the relationship between geotemporal distribution, process and performance.

Fully Distributed Scrum: Linear Scalability of Production between San Francisco and India

The ability to achieve hyperproductivity with distributed, outsourced teams was shown to be a repeatable process and a fully distributed model is now the recommended standard when organizations have disciplined Scrum teams with full implementation of XP engineering practices inside the Scrum.

The industrialisation of software production - a knowledge management perspective

ion may serve to make it easier to create the components that will form the solution as a whole, but abstraction will not address the emergent property of software as described above – this can only

SCRUM Development Process

SCRUM is an enhancement of the commonly used iterative/incremental object-oriented development cycle that defines the systems development process as a loose set of activities that combines known, workable tools and techniques with the best that a development team can devise to build systems.

Comparing PMBOK and Agile Project Management software development processes

The result is that, agile project management methodologies cannot be considered complete, from the traditional project management point of view, since a number of processes either are missing or not described explicitly.

Teams That Finish Early Accelerate Faster: A Pattern Language for High Performing Scrum Teams

It became apparent that a combination of nine Patterns in conjunction with the Scrum framework could help teams achieve Hyper-Productivity, more than a 400% increase in velocity over a team's initial velocity.

References

SHOWING 1-10 OF 13 REFERENCES

Introduction to Software Process Improvement.

The Software Engineering Institute's (SEI) software process maturity model is described, how this model can be used to guide software organizations in process improvement, and the various assessment and evaluation methods that use this model.

Does every inspection need a meeting?

This work proposes two alternative fault collection methods, either of which would eliminate the inspection meetings altogether: collect faults by deposition (small face-to-face meetings of two or three persons), or collect faults using verbal or written media (telephone, electronic mail, or notes).

A role-based empirical process modeling environment

  • Brendan G. CainJ. Coplien
  • Computer Science
    [1993] Proceedings of the Second International Conference on the Software Process-Continuous Software Process Improvement
  • 1993
The authors' initial research in large, mature telecommunications development processes concluded that such models do not capture abstractions that remain stable over time, so they turned their attention to empirical role-based models.

Managing the flow of technology

Quattro Pro For Windows At Work

Quattro Pro for Windows.'' PC Magazine

  • Quattro Pro for Windows.'' PC Magazine
  • 1992

‘ ‘ On the Road to Software Automation

    Borland turns the Windows page: Quattro Pro for Windows.’

    • PC Sources,
    • 1993

    Borland turns the Windows page: Quattro Pro for Windows

    • PC Sources
    • 1993

    Quattro Pro for Windows Version 1.0.’

    • InfoWorld, vol. 14 no. 41,
    • 1992