Showing results for "The Mark" in Programming

Salary surveys worldwide regularly place software architect in the top ten best jobs, yet no real guide exists to help developers become architects. Until now. This updated edition provides a comprehensive overview of software architecture's many aspects, with five new chapters covering the latest insights from the field. Aspiring and existing architects alike will examine architectural characteristics, architectural patterns, component determination, diagramming architecture, governance, data, generative AI, team topologies, and many other topics.

As mobile and web technologies continue to evolve rapidly, there is added pressure to develop and implement software projects in weeks instead of months. Agile Project Management for Dummies can make that happen. This is the first book to provide a simple, step-by-step guide to Agile project management approaches, tools, and techniques.

Agile Project Management for Dummies introduces you to the planning and execution approaches that can help you complete projects more quickly, with higher quality and using fewer resources. For companies in any industry—not just software development—agile project management reduces waste and increases transparency, while addressing customers' ever-changing requirements. You'll learn all the important terms, tools, and concepts, so you can infuse agility into your projects right away. Create a product roadmap and prepare for product launches with ease, thanks to this Dummies guide.

We are living in the computer age, in a world increasingly designed and engineered by computer programmers and software designers, by people who call themselves hackers. Who are these people, what motivates them, and why should you care? Consider these facts: Everything around us is turning into computers. Your typewriter is gone, replaced by a computer. Your phone has turned into a computer. So has your camera. Soon your TV will. Your car was not only designed on computers, but has more processing power in it than a room-sized mainframe did in 1970.

You are a Scrum Master and you are joining an existing team. There is a problem, though. The Product Owner is unhappy. There is a high priority item on the Product Backlog that the developers are refusing to add to their Sprint. They say that Scrum gives them the right to choose the work they do, and they claim the so called "high priority" item is not very important at all.

You are on a Scrum Team with a problem. You need some changes to the data base behind the application you are creating, but the tables are controlled by another team, they are busy with their own priorities and do not want to help. What should you do? This case and the others in the series come from the real-world experiences of a group of Scrum professionals who meet regularly to discuss the Scrum Framework and how to apply it to actual situations they have encountered.

You are an Agile Coach and you are being called in to fix a bad problem. Your client has entered into a fixed price contract with their client, but it looks like the project is going sour. Half of the time and money have been spent but only about 30 percent of the milestones have been reached. Management wants you to "do Agile" and fix the problem. What should you do? This case and the others in the series come from the real-world experiences of a group of Scrum professionals who meet regularly to discuss the Scrum Framework and how to apply it to actual situations they have encountered.